Summary
Elevale publishes an OpenAPI 3.1 specification summarizing endpoints, parameters, and schemas.
Who this is for
Developers and integrators building automations with Elevale API personal access tokens.
Elevale publishes an OpenAPI 3.1 specification summarizing endpoints, parameters, and schemas.
Specification URL
https://elevale.app/openapi.yaml
Relative path on your deployment: /openapi.yaml
The Platform Wiki guides (this folder) are the narrative documentation with examples and security detail. OpenAPI is a concise machine-readable summary-keep both in sync when the API changes.
Common field formats
dueDate (tasks) - string, format date, YYYY-MM-DD. Do not send YYYY-MM-DDTHH:mm:ssZ or milliseconds.
createdAt / updatedAt - string, format date-time, ISO 8601 UTC.
status (tasks) - todo | in_progress | completed
priority (tasks) - low | medium | high | urgent
Task nesting - up to 7 levels; up to 1,000 subtasks per parent. See Tasks API.
Document map
Introduction to the Elevale API - overview and base URL
Reading data (GET API) - query params, filters, and read examples
Personal access tokens (PATs) - authentication setup
Scopes and permissions - authorization model
Requests, responses, and errors - envelopes and rate limits
Tasks, KPIs, OKRs, Wiki, Strategic brief, BD logs, Chat - per-resource guides