Skip to main content

Timezone Offsets

Here is how we handle timezone offsets in API v1 calls:

  • We use the following standard date format: ISO_8601_FORMAT_DATE_TIME = "YYYY-MM-DD'T'hh:mm:ss±hh:mm".
  • We either save the date as it is or extract the offset value if it contains an offset.
  • Unlike in API v2, in API v1 we don’t validate the timezone.

Example Each Mambu tenant has one timezone. Let’s take for example tenants in the East European time zone (UTC+02:00).

Date and time of requestWhat is saved in the database
2021-03-09T13:37:502021-03-09 13:37:50
2021-03-09T13:37:50+02:002021-03-09 11:37:50
note
  • When posting a transaction in the present, the current offset should be used, according to the tenant’s time zone.
  • When posting a backdated transaction, the offset which was correct for that date and time should be used, according to the tenant’s time zone.
  • When posting a transaction in the future, the future offset should be used, according to the tenant’s time zone.
  • If your country uses Daylight Saving Time, posting transactions that occur during 'lost' hours, for example between 02:00:00 a.m. CEST and 2:59:59 a.m. CEST, will be allowed as the timestamp will not be validated, however, this can create timestamps that don’t actually exist, which may lead to unexpected errors if exporting or synchronising data to other systems which do validate timezones and time offsets. We also generally recommend not processing API calls during the minutes leading up to and after the switchover as small differences in clock synchronisation across various systems and services may lead to unexpected errors.
    • Last updated on