Resources
Organisations, opportunities, projects, credentials, evidence and catalogue items.
API REFERENCE
Design stable contracts before integrations multiply.
A reference architecture for resource naming, versioning, errors, pagination, idempotency and audit context.
API REFERENCE
Developer contract.
A reference architecture for resource naming, versioning, errors, pagination, idempotency and audit context.
Versioning
Explicit API version and backwards-compatibility policy.
Errors
Stable machine-readable error codes and correlation IDs.
Idempotency
Protect write operations from duplicate submission.
Pagination
Cursor-based approaches for large or changing datasets.
Audit context
Actor, organisation, request ID and decision context where appropriate.
NEXT STEP
Discuss an integration requirement.
Production integrations require scope, identity, data classification, rate and support requirements.