Orange Logic (Cortex) Specs

README — provenance

DAM Wiki extracted these files on 2026-09-30 from the public Orange Logic developer portal (developer.orangelogic.com, hosted on ReadMe). Orange Logic does not publish a single downloadable OpenAPI document: each endpoint page of the API reference embeds its own small OpenAPI 3.1 definition (one operation per file) in an "OpenAPI definition" code block of the page's Markdown rendition (<page URL>.md). Each file below is the JSON text of that code block, stored byte-for-byte (only a trailing newline normalised). DAM Wiki re-extracts them when the developer changelog (https://developer.orangelogic.com/changelog) announces API changes.

Extraction pattern: download https://developer.orangelogic.com/reference/{slug}.md, take the fenced ```json block that follows the # OpenAPI definition heading. The page list comes from https://developer.orangelogic.com/llms.txt (184 pages on 2026-09-30, 44 of them embed a definition).

Notes

• Every definition declares servers: https://{OrangeLogicURL}/… (the customer's own instance host, i.e. https://{tenant}.orangelogic.com or a custom domain) and an OAuth 2.0 clientCredentials security scheme whose tokenUrl is a ReadMe placeholder (https://example.com/oauth2/token), not the real token endpoint. The real endpoints are documented in prose (see ../api.md).
• Many documented endpoints are not covered by any embedded definition: DataTable CRUD calls (/API/DataTable/v2.1|v2.2/{Object.Type.Subtype}:{Read|Create|Update|CreateOrUpdate|Delete|ListFields} beyond the three samples), webhook subscription update/delete/get/list/test/topics, Get Client Credentials, /api/Monitoring/v1.0/RunChecks, /api/QualityControl/v2.0/Ping, legacy multi-part upload calls (/API/UT_UPLOADTRANSACTION/…, /API/CortexUploader_BO/…), IIIF and the MCP server. They are documented only in prose (or only in each tenant's Swagger UI).
• Each customer instance exposes a full Swagger UI at https://{tenant}/swagger and a JSON spec at https://{tenant}/swagger/application/swagger.json, but only for logged-in users with the "Can access Swagger" Security Function (the vendor's own instance answers 403 without a session, observed 2026-09-30). That tenant-level spec is therefore Behind login and not stored here.
• The ReadMe project also exposes 19 "API registry" files (https://dash.readme.com/api/v1/api-registry/{uuid}, UUIDs listed in the portal's page data). On 2026-09-30 17 of them were empty shells (0 operations), get-links.json and webhooks.json duplicated the embedded definitions, and orangelogic-api-application.json (OpenAPI 3.0.1, 13 operations) describes an internal, beta cluster-management API (/webapi/application/cluster/…) that is not referenced anywhere in the published docs. None of them is stored here.
• No official Postman collection is published (the docs recommend importing the tenant Swagger JSON into Postman).
• Quick inventory: python -c "import json,glob;[print(f,list(json.load(open(f,encoding='utf-8'))['paths'])) for f in glob.glob('*.json')]"