Skip to main content

General concepts

This page contains concepts that you should be familiar with when working with the Emogg APIs.

Dates​

Requests​

All date and time query parameters and fields allow strings in ISO 8601 format or numeric unix milliseconds timestamp:

  • YYYY-MM-DDTHH:mm:ss.sssZ (UTC)
  • YYYY-MM-DDTHH:mm:ss.sss+HH:MM (for specifying a timezone)
  • 0000000000000 (UTC)

If none timezone or UTC is specified, the last is assumed. Examples for representing the 1st of April 2024 at 13.30 UTC time:

  • 2024-04-01T13:30:00.000Z
  • 2024-04-01T15:30:00.000+02:00
  • 1711971000000

Responses​

All date and time fields included in any API response will follow the ISO 8601 in the UTC format: YYYY-MM-DDTHH:mm:ss.sssZ.

Example: 2024-04-01T13:30:00.000Z.

Data format​

The Emogg APIs (both REST and WS) uses JSON as data encoding format for communication. In the case of the REST API all of the requests bodies and responses will use this format, and in the case of the WS API all the messages sent and received will also be encoded as JSON.