API
Using a REST architectural style, the Web service API exposes much of the PageSeeder functionality to external applications so that everything that can be done through the user interface can also be programmatically.
All available Web services are documented, including whether they support XML or JSON or both, and in which version of PageSeeder they were introduced. To simplify the handling on the client-side, we’ve standardised the output and errors.
The API elements section provides a complete list of elements used in the output of services from <alias> to <workflow>.
A lot of progress has been made migrating the PageSeeder APIs to XML or JSON-based services or the Bridge, for Java developers. While this new environment is the result of a lot of hard work, we understand how quickly that effort can be undone by inaccurate or out-of-date documentation.
If you notice any issues with the API documentation, you can email your comments to this address . Thank you for taking the time to learn more about PageSeeder.