The Glomo API is designed using REST principles, featuring clear, resource-based URLs. It processes form-encoded request bodies, returns responses in JSON format, and utilizes standard HTTP methods, response codes, and authentication.
Test mode is available for the Glomo API, allowing you to run requests without affecting live data. The type of API key used will determine if the request is in test or live mode.
Note that bulk updates are not supported, so each request handles only one object at a time.
The complete API contract is published as a single, self-contained OpenAPI 3.1 document:
| Format | URL |
|---|---|
| YAML | /openapi.yaml |
| JSON | /openapi.json |
Both are the same document — 61 paths, 81 operations, 68 schemas — with every $ref resolved inline, so one request gets you the whole contract with nothing left to follow. They are served as application/yaml and application/json with Access-Control-Allow-Origin: *, so a browser-based tool can fetch them cross-origin.
Use them to generate a client, seed an HTTP collection, or hand the API to a coding agent. The URLs are stable; they are regenerated from source on every change and guarded in CI against drift.