The customer-facing surface for the AgentSync Contracting platform: a purpose-built,
read-only API for producers, contracts, contract assignments, and the hierarchies those
assignments form. Every endpoint below is under the /v2 path prefix.
Every endpoint requires an OAuth2 client-credentials token and the scope shown on that
endpoint. See Authentication for how to
request credentials and retrieve a token,
API Base URLs for the sandbox and production
hosts, and Pagination for how page_token
and page_size behave across list endpoints.
Contracting and hierarchy endpoints are documented together because they share one set of
scopes: a token carrying contracting.contractassignments.read reaches both. They are also
entangled by design — a hierarchy node’s key is a contractAssignmentId. Use the sidebar
groups to navigate: hierarchy and upline-discovery endpoints are under Hierarchies.
Webhook events
AgentSync delivers outbound events to your configured endpoint when contracts, contract
assignments, and hierarchy placements change. Each event is an HTTP POST whose body carries a
unique id, a dot-notation type, and a type-specific data payload; respond 2xx to
acknowledge. The event types are declared under webhooks below.
Full payload documentation — every field of every event, delivery semantics, retry behaviour
and signature verification — lives at
Contracting API Webhooks.
- Server 1:https://api.sandbox.agentsync.io/contracting
Sandbox
- Server 2:https://api.agentsync.io/contracting
Production
oauth2 (oauth2)
OAuth2 client credentials. The tokenUrl below is the SANDBOX token endpoint; for production use https://auth.agentsync.io/oauth2/token. OpenAPI 3.1 permits only one token URL per flow, so both cannot be expressed here - see https://developer.agentsync.io/api-authentication for the full environment table, how to request credentials, and worked token-retrieval examples.