Envelope Fields
| Field | Type | Description |
|---|---|---|
timestamp | string | ISO 8601 timestamp of response generation |
success | boolean | true if the request succeeded, false on error |
message | string | Human-readable status message |
errorCode | string | Machine-readable error code — empty string "" on success |
type | string | Data type name of the object in data — empty string "" on error |
data | object | null | The response payload — null on error |
Success Response
Error Response
Data Types
Thetype field tells you what shape the data object has:
| Type Value | Returned By | Description |
|---|---|---|
ChartResult | /v2/charts, /v2/charts/coordinates | Full chart with all properties (type, profile, channels, centers, strategy, authority, incarnation cross, activations, and more) |
ChartSimpleResult | /v2/charts/simple | Simplified chart (type, profile, gates, channels, centers) |
Parsing Guidelines
- Check
successfirst — determines whetherdatais populated ornull - Use
errorCodefor logic — never parsemessagefor error handling. Messages are human-readable and may change without notice. datais always a single object — v2 chart endpoints return one chart per request, never an array
v1 Response Format
v1 endpoints return the chart data directly as a flat JSON object — no envelope. Field names use
snake_case (e.g., channels_short, incarnation_cross). See the migration guide for differences.
