Get API access
How shippers and providers request a development or production API token to start integrating with Cargobase.
API tokens are not self-serve. Cargobase issues credentials that are scoped to your company and to one environment (Sandbox or Production). If you are new to the platform, start here before calling any endpoint.
Who can request a token
- Shippers integrating a TMS, ERP, or other systems that create requests, manage shipments, or pull invoices.
- Providers (carriers and logistics partners) that consume work, post tracking, or exchange operational data.
You should already be a Cargobase customer (or in onboarding). If you do not yet have a commercial relationship, email support@cargobase.com and ask about becoming a partner.
What to ask for
Email support@cargobase.com (or your Cargobase account / customer success contact) and include:
| Detail | Why it matters |
|---|---|
| Company name | Tokens are scoped to that company |
| Role | Shipper or Provider |
| Environment | Prefer Sandbox first; request Production only when you are ready for live traffic |
| Use case | Short note on what you will automate (e.g. create drafts, post tracking) |
| Technical contact | Who should receive the credential |
Your company administrator can also request tokens on your behalf if they already work with Cargobase support.
Sandbox first
- Request a Sandbox token and use
https://sandbox.cargobase.com. - Build and validate against the Shipper or Provider reference.
- When you are ready for live data, request a separate Production token and switch the base URL to
https://pluto.cargobase.com.
Sandbox and Production credentials are not interchangeable. See Environments.
After you receive a token
- Store it in a secrets manager—never commit it to source control.
- Send it on every request as described in Authentication:
Authorization: Token <your_access_token>
- In the interactive API reference, open Authentication, paste the token once, and try a simple read (for example listing addresses or shipments) to confirm access.
Rotating or replacing a token
If a token may have been exposed, or a teammate leaves, ask support to revoke the old credential and issue a new one for the same company and environment. Update your integration as soon as the new token arrives.
Still stuck?
- Not sure whether you need Shipper or Provider docs? Start with Getting started.
- Token works in one host but fails in another? Check Environments.
- Anything else: support@cargobase.com.