SDK methods and routes
These methods and paths are taken from the repository's TypeScript SDK implementation. They describe client calls, not a claim that every endpoint is publicly enabled in every environment.
| SDK operation | Hosted API path |
|---|---|
createParticipant() | POST /v1/participants |
getParticipant(id) | GET /v1/participants/:id |
createRelationship(input) | POST /v1/relationships |
getRelationship(id) | GET /v1/relationships/:id |
getContext(id) | GET /v1/relationships/:id/context |
getHistory(id) | GET /v1/relationships/:id/history |
addContribution(id,input) | POST /v1/relationships/:id/contributions |
exchange(input) | POST /api/apex/exchange |
compose(input) | POST /api/apex/composition (prepare / commit / cancel) |
uploadImageArtifact(input) | POST /api/apex/artifacts/image |
validateMigration(input), stageMigration(input) | POST /api/apex/migrations |
commitMigration(input) | PATCH /api/apex/migrations |
getMigration(id) | GET /api/apex/migrations |
listVerification(), getVerification(id) | GET /v1/verification |
Requests use a bearer API key, tenant scope (organization, project, environment) and the RSC-APEX-Version header (SDK default 2026-09-21). Exchange and composition require idempotency keys. Server authorization, relationship ownership and credit enforcement remain authoritative.