Request format
Ez a tartalom még nem érhető el a jelenlegi nyelven.
Use this page for conventions shared by the operation reference. Each operation page remains authoritative for its required parameters and response fields.
Base URL and headers
Section titled “Base URL and headers”The API base URL is https://api.cleverev.net. Send these headers with requests:
| Header | Value | Purpose |
|---|---|---|
Authorization | Bearer <API_KEY> | Authenticates the API key. |
organization-id | Organization identifier | Selects the tenant used for authorization and data access. |
compatibility-date | YYYY-MM-DD later than 2025-11-01 | Required compatibility header. |
Accept | application/json | Recommended when requesting JSON responses. |
For JSON request bodies, send Content-Type: application/json. The location image upload operation uses multipart/form-data; let your HTTP client set the multipart boundary rather than setting a bare content type yourself.
Timestamps
Section titled “Timestamps”Send and expect date-time values in ISO 8601 UTC form, for example 2026-10-25T08:30:00.000Z. The compatibility header is date-only (2026-10-25), not a timestamp.
Response handling
Section titled “Response handling”Use the HTTP status and the response schema shown for that operation. Resource-array names, count fields, and error bodies can differ; don’t assume one envelope fits every endpoint.