Overview
This document outlines the Zenskar-compatible DateTime formats, common errors, and troubleshooting steps to ensure smooth data ingestion.
DateTime formats compatible with Zenskar
Zenskar APIs expects the timestamp
field to be in DateTime64
or DateTime36
format without timezone offsets. The expected structure is:
YYYY-MM-DD HH:MM:SS
For example, timestamp": "2024-12-18 01:00:00
.
Common error
When sending usage data, using an incorrect DateTime format (for example, timestamp": "2024-12-18T01:00:00.000000000+0100
) may result in the following error:
Invalid type for key: timestamp. Expected Date32/DateTime64, got string
The example timestamp contains a timezone offset (e.g., +0100
), which is not supported.
"timestamp": "2024-12-18 01:00:00",
Troubleshooting
- Remove any timezone offset from the timestamp.
- Ensure the timestamp is formatted as
YYYY-MM-DD HH:MM:SS
. - Confirm that your API request body is correctly structured and does not contain additional metadata.
- If the issue persists, reach out to Zenskar support with the error message for further assistance.
Additional Notes
- If your backend (for example, in Golang) generates timestamps automatically, ensure that it strips off timezone information before sending data to Zenskar.
- Future updates may include support for timezones, but as of now, they must be manually adjusted before sending requests.