These can be alternate representations, e.g. collections and processes) a set of links can be added. The API is designed in a way that to most entities (e.g. Single actions MUST be single endpoints with a single HTTP verb (POST is RECOMMENDED) and no other endpoints beneath it. Resource identifiers MUST be named with a noun in plural form except for single actions that can not be modelled with the regular HTTP verbs. Therefore, endpoints are centered around resources. Naming of endpoints follow the REST principles. Therefore, changing a property on a deeper level of the full JSON object always requires to send the whole JSON object defined by the first-level property. Unless otherwise stated, PATCH requests are only defined to work on direct (first-level) children of the full JSON object. If there is a need to transfer big chunks of data for a GET requests to the back-end, POST requests MAY be used as a replacement as they support to send data via request body. GET, POST, PUT, PATCH, DELETE) whenever technically possible. ![]() Public APIs MUST be available via HTTPS only.Įndpoints are made use meaningful HTTP verbs (e.g. This uses HTTP REST Level 2 for communication between client and back-end server. get Download results for a completed batch job.post Process and download data synchronously.post Validate a user-defined process (graph).get Full metadata for a user-defined process. ![]() ![]() get Full metadata for a specific dataset.get Information about the authenticated user.get Supported secondary web service protocols.get OGC specifications this API conforms to.
0 Comments
Leave a Reply. |