DutyClaims Partner API
Quick ActionsAPI Host MirrorRaw OpenAPI
Getting Started

Integrate from the current contract, not tribal knowledge.

DutyClaims v1 is documented around the same contract that drives the API reference, downloads, and changelog. Start here, then move into auth and the live reference.

Recommended onboarding path

  1. Issue or rotate a managed credential and confirm whether your integration uses `Authorization: Bearer ...` or `X-API-Key`.
  2. Create a low-risk sandbox workflow first: client creation, claim submission, or notifications test traffic.
  3. Configure webhooks early so you can observe asynchronous status changes instead of polling everything forever.
  4. Download the generated starter artifacts only after confirming the commit metadata on the downloads page matches your target deployment.
Review AuthFetch Artifacts

Current contract scope

The live v1 contract currently covers 77 documented operations across 65 paths.

  • Authentication: 1 operations
  • Diligence: 5 operations
  • Partner Orgs: 8 operations
  • Clients & Authority: 11 operations
  • Entries & Scans: 7 operations
  • Claims: 9 operations
  • Financing: 8 operations
  • Litigation: 9 operations
  • Counterparty: 9 operations
  • Notifications: 3 operations
  • Reporting: 4 operations
  • Reference: 3 operations

Environment truth

Production

Production-ready surface

Clients, claims, financing, litigation, notifications, revenue, webhooks, and reference data are the truthful v1 production surface today.

Sandbox Only

Sandbox-only auth

OAuth client-credentials token issuance is available for sandbox partner integrations. Production access still centers on managed credentials.

Provider Blocked

Provider-gated automation

Diligence and counterparty automation stay explicitly provider-gated until paid external provider activation is complete. The docs keep that boundary visible.

First reads and writes

# 1. Read the live contract
curl https://api.dutyclaims.com/v1/docs/openapi

# 2. Create or inspect a client
curl -H "Authorization: Bearer dcp_live_replace_me" \
  https://api.dutyclaims.com/v1/clients

# 3. Register a webhook endpoint once event handling is ready
curl -X POST https://api.dutyclaims.com/v1/webhooks/endpoints \
  -H "Authorization: Bearer dcp_live_replace_me" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://partner.example.com/webhooks/dutyclaims","events":["claim.updated"]}'

Route ownership

  • Human guides: docs.dutyclaims.com
  • Interactive reference: docs.dutyclaims.com/api
  • Raw contract: api.dutyclaims.com/v1/docs/openapi
  • Versioned changelog JSON: api.dutyclaims.com/v1/docs/changelog