Skip to Content
DevelopersOverview

Developers

RGL8R’s public API is production-first and organized around three canonical workflows. Every integration follows the same pattern: authenticate with an operator-issued integration key, pick a workflow, and run it end-to-end with curl, Postman, or an example script.

Core flow

  1. Your RGL8R operator issues an integration key (assisted onboarding; the secret is revealed once).
  2. Exchange the key for a short-lived bearer token via POST /api/auth/token/integration.
  3. Pick one of the three canonical workflows (below) and call the tenant endpoints with Authorization: Bearer <token>.
  4. Poll async jobs or feed sessions until they reach a terminal state.
  5. Fetch results, record workflow metadata downstream.

Three canonical workflows

  1. SIMA screening (smallest) — enqueue a batch against your tenant catalog, poll, fetch outcomes. See the SIMA section in public-api-contract-v1.
  2. TRADE feed — upload a CSV/Excel, normalize, classify-preview, review, apply to catalog. See TRADE feed contract.
  3. SHIP audit — upload carrier invoices, list findings, dispute, bundle into a claim submission. See SHIP finding contract and SHIP claim submission contract.

Build with TRADE API

If you are integrating classification, landed cost, or catalog feeds into your own system, start here:

  1. 5-Minute API Quickstart — get a token and make your first call.
  2. TRADE Feed Contract — upload, normalize, classify, and apply catalog data.
  3. Agent Integration Kit — connect AI agents and automation tools.
  4. Integrations Overview — n8n, Zapier, and CLI quickstarts.

Start with these docs

What developers usually need first

Auth and access

  • Use integration keys for API clients and automation.
  • Use Clerk-authenticated sessions for app settings, billing, and module controls.
  • Keep integration-key scope narrow and rotate keys when operators change.

Product APIs

  • SHIP supports upload, findings review, and claim workflows.
  • TRADE supports classification, catalog upload, SIMA screening, landed-cost calculations, and obligation checks.
  • Billing and usage visibility are available from tenant-scoped billing endpoints.

Operational assumptions

  • Daily caps and lower rate limits apply to Sandbox tenants.
  • Professional and Enterprise tiers are designed for sustained production use.
  • API clients should treat rate limits, async jobs, and partial review workflows as normal operating conditions.

Next steps

Regulatory Intelligence5-Minute API Quickstart