General notes
  • 15 May 2024
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

General notes

  • Dark
    Light
  • PDF

Article summary

All data is in unicode and encoding used is UTF-8.

API accepts and generates only application/json requests and responses. All requests must have correct content negotiation headers to receive responses in correct format.

Some operations might not have any response body, like DELETE operation.

All create and update requests use flattened definitions. All other requests use normal definitions.

Dates and times

Dates and times are always in ISO 8601 standard format.

Type

Format

Example

Date

YYYY-MM-DD

2019-05-02

Time

HH:MM:SS

15:32:01

Date/Time

YYYY-MM-DDTHH:MM:SS

2019-05-02T15:32:01

Geographical locations

Geographical locations are passed as EWKT (Enhance WellKnown Text).

Example of location:

{

"location": "SRID=3067;POINT Z (454939.9781610000063665 6702826.5743100000545382 0.0000000000000000)"

}


Was this article helpful?

What's Next