Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| kind | one of: unix_ms, iso8601 | yes |
Request body
This operation takes no request body.
Example request
A request body that works, as JSON.
{}
Response
The fields inside data of a successful response.
| Name | Type | Required | Description |
|---|---|---|---|
| id | string | yes | Generated timestamp ID |
| type | string | yes | Type of timestamp ID generated |
Example response
A real answer from the operation, as JSON. The fields in the table above are inside data.
{
"data": {
"id": "1793085582088",
"type": "timestamp_unix_ms"
},
"errors": null,
"meta": {
"request_id": "b3c4f23c-335d-4c80-88e7-39f0842d2010",
"timestamp": "2026-10-27T07:19:42.088050Z",
"version": "2026-03-26"
},
"pagination": null
}
Responses
| Status | When it happens |
|---|---|
| 200 | Successful Response |
| 400 | The body respects the operation schema, but the use case rejected it. Each problem is one ApiError entry |
| 413 | The request is larger than the request size limit of the API allows |
| 422 | The body does not respect the operation schema. Each problem is one ApiError entry with the code validation_error |
| 500 | Something failed inside the server and was not an input problem. The same envelope, errors may be empty |