Developer Hub
Start here if you are building on the API and need the partner model, host split, and practical integration path before reading raw route docs.
OpenThis section is for engineers, solution architects, and technical partner teams. It explains how the external API model fits the human web-app model, which partner types exist, and where to start for auth, reference, downloads, and live contract work.
The DutyClaims partner API is in early alpha. Routes, request shapes, response contracts, and auth patterns are all subject to change without notice. Pin to the contract hash shown on this page and treat every endpoint as potentially deprecated until a stable release is announced.
Start here if you are building on the API and need the partner model, host split, and practical integration path before reading raw route docs.
OpenHow the hosted partner model works, why SaaS teams use it, and what DutyClaims handles behind the branded experience.
OpenCredentials, first requests, generated examples, and the safest order to integrate.
OpenCopy-paste TypeScript starters for canonical partner flows, diligence compatibility, broker aliases, and webhook verification.
OpenCanonical domains, sandbox versus production rules, release pinning, and environment scope.
OpenProduction managed credentials first, sandbox OAuth where explicitly supported, plus current header semantics.
OpenCurrent API families, representative routes, and the route order most partner teams implement first.
OpenEndpoint registration, signature verification, sandbox test events, and delivery debugging.
OpenProblem payload anatomy, request IDs, retry discipline, and problem-type troubleshooting paths.
OpenVulnerability reporting contact, security.txt locations, disclosure expectations, and good-faith testing boundaries.
OpenGo-live proof points for credentials, tracing, idempotency, webhooks, support handoff, and cutover discipline.
OpenMove legacy diligence and broker-compatibility traffic onto canonical `/v1/*` routes without losing operational visibility.
OpenThe live interactive reference stays on the API host so contract and route behavior remain aligned.
Openae140b8f3b926d06| Concept | What it answers | Examples |
|---|---|---|
| Portal role | Which human workspace should this signed-in user land in? | importer, broker, partner_admin, admin, attorney |
| Partner type | What kind of external API tenant is this organization? | broker, saas_partner, forwarder_or_tms, service_provider |
| Capability | What is that tenant allowed to do? | Diligence reads, submissions, financing, litigation enrollment, webhooks, authority shortcuts |
Managed credentials everywhere, plus sandbox-only OAuth client credentials for partner testing.
1 operations in the current contract
Open workflow notesSubmit portfolios, poll job status, and retrieve reports or datasets while provider-backed automation remains gated.
5 operations in the current contract
Open workflow notesPartner organizations, capabilities, webhook endpoints, and managed credentials.
8 operations in the current contract
Open workflow notesCanonical client records, authority state, delegations, invitations, and POA assertions.
11 operations in the current contract
Open workflow notesEntry ingest, batch normalization, and portfolio scan lifecycle endpoints.
7 operations in the current contract
Open workflow notesClaim scoring, claim creation, status reads, and claim document delivery.
9 operations in the current contract
Open workflow notesOffers, agreement sessions, and advance or disbursement state.
8 operations in the current contract
Open workflow notesEnrollment, readiness, package delivery, and docket status reads.
9 operations in the current contract
Open workflow notesCounterparty profiles, diligence cases, provider runs, monitoring enrollment, evidence, and partner-safe reports with truthful deployment-readiness guardrails.
13 operations in the current contract
Open workflow notesPartner-triggered notifications, delivery analytics, and client notification history.
3 operations in the current contract
Open workflow notesPartner dashboards, revenue ledgers, and export surfaces.
4 operations in the current contract
Open workflow notesOfficial HTS-backed search, countries, and health metadata.
3 operations in the current contract
Open workflow notesStart with the white-labeling guide if you want the business and operating model first. If you are already configuring branding, launch data, or the hosted customer journey as a partner operator, use the workspace guide next. The developer hub still covers the external API model, but the human setup console now lives in the SaaS partner guide.
Partner type
Best when the external organization is a customs broker or brokerage that needs importer relationship management, delegated authority flows, partner emails, commissions, and broker-specific operational paths.
Maps to both worlds: broker is a partner type for the API platform and also a top-level portal role for humans in the web app.
Partner type
Best when the external organization is a compliance platform, ABI-adjacent system, duty-analytics product, or embedded trade workflow that needs structured API access without broker-human workspace semantics.
Still not a portal role by itself. `saas_partner` classifies the external tenant, while human operators use the `partner_admin` workspace on the main host.
Partner type
Best when the external organization brings shipment context, logistics workflow, or transportation operations but does not fit the broker portal model.
No portal role. This is an external API tenant classification for shipment- and workflow-centric partners.
Partner type
Best when the external organization is a general service partner, specialist vendor, or channel-style integration that needs a tenant record and API or webhook capability but not a dedicated first-party portal workspace.
No portal role. This is the generic external-partner bucket when a tenant is neither a broker nor a clearly productized SaaS or logistics system.
/api/diligence/* or /broker/v1/* paths.