The published catalogue defines the supported external operations. An internal route or an OpenAPI definition alone does not establish publication.
Prerequisites
Create an API key and obtain the target workspace UUID and type UUID from the application. Use the URL of your environment; production uses https://api.ontologie-growthsystemes.com.
curl --fail-with-body --silent --show-error \
"https://api.ontologie-growthsystemes.com/api/v1/object-types/TYPE_UUID/instances" \
-H "X-API-Key: df_REPLACE_WITH_YOUR_KEY" \
-H "x-workspace-id: WORKSPACE_UUID"
Replace the placeholders. Documentation pages use /docs/; server endpoints use /api/. Do not substitute a documentation path into an HTTP request.
Search APIs
Explore the 30 search operations: composition, business definitions, documents, instances and graph exploration. Each API includes its purpose, inputs, result and a usage example.
Test in API Manager
API Manager is available at /ontology/apis in the application. Select a published operation and open its test panel. It uses your user session and selected workspace; it does not simulate an external API key. Compare a known record with the interface and check pagination before calculating totals.
Support contract
- The catalogue is generated from the publication manifest and checked in CI.
- Check each operation’s required scopes and permissions before integrating.
- Check the exact method, path, parameters and access requirements before integrating.
- An empty list differs from an access error. Session success does not establish key permissions.
For diagnosis, keep the method, path, HTTP code and request identifier. Remove secrets from shared logs. Continue with the API quickstart.
