List of timezones
When sending date activities, it is required that you provide the timezone of the date so that it can be stored correctly. Ideally, you would use a consistent time zone across your entire account, but this is not required. Here is an example of an activity request with a date attribute:
shell
curl --location\ --request POST 'https://api.ap3api.com/v1/activities/create'\ --header 'X-Api-Key: YOUR-REAL-API-KEY-HERE'\ --header 'Content-Type: application/json'\ --data-raw '{ "activities":[ { "activity_id":"act:cm:visited-store", "fields": { "str::first": "Chris", "str::last": "Smith", "str::email": "chris.smith@example.com" }, "attributes": { "dtz:cm:visit-date": {"year":2022,"month":3,"day":4,"timezone":"Africa/Abidjan"} } } ] }'NOTE: Ortto customers who have their instance region set to Australia or Europe will need to use specific service endpoints relative to the region:
For example: https://api.eu.ap3api.com/v1/<entity/endpoint>
All other Ortto users will use the default service endpoint (https://api.ap3api.com/).
If you provide an invalid timezone, your request will fail like so:
json
{"request_id":"4a7db0c6-1644-4505-a903-c07450bd0ce7","code":500,"error":"Internal Server Error"}Valid timezones
The following list indicates all valid timezones available in Ortto: