Comment on page
Requests and filters
All requests to the Dashdoc API must be made over SSL (https, not http).
We recommend using JSON body format when performing API requests. In order to do a proper JSON-formatted request, make sure you provide
Content-Type: application/jsonin HTTP request headers. XML data is also supported, see Sending XML data.
Our API uses the HTTP verbs for each action:\
Our API uses a straight-forward URL naming convention.
Always specify the API version in your calls ;
/api/automatically redirects to the latest available version of the API.
- When one item is being asked and such method exists, the UID of the item must be appended to the URL, for example
- The API token must be provided as part of the http header for all requests using the
Example of curl authenticated request
curl -X GET -H "Authorization: Token 5a4d02fad3975c169e9f538d8e733ead4069703x" "https://www.dashdoc.eu/public-api/v2/"
You can pass in filters to indicate which data you would like to fetch when asking for a collection/list of objects. When provided, you can add comparison filters that are separated from the field a double underscore:
Most endpoints in our API support this.
For example, you may only want to fetch transports that were updated after a given date. We'll use the
__gteto do that. This can be done using the following syntax:
Filtering transports on updated date