HighQube API
Use the prices and quotes your team sees in HighQube from your own systems: your website, TMS, CRM or spreadsheets. The API works with your organization's own data. A rate search prices your carrier contracts, and the quotes are the ones your team sent.
Quickstart
Make your first rate search in five minutes.
API keys
Create a key, choose what it can do, and keep it safe.
Price a shipment
Ocean rates, the surcharges behind them, LCL and trucking.
API reference
Every endpoint, with examples you can run in the browser.
What you can do
| Area | What it gives you |
|---|---|
| Rate search | All-in prices per container from your carrier contracts, for one lane or many: ocean freight plus the surcharges in effect today. |
| Surcharges | The breakdown behind any rate: each surcharge, what it applies to, and what is filed to start later. |
| LCL | Prices for less-than-container-load shipments. |
| Trucking (drayage) | Prices for moving a container between a port or rail ramp and a door address. |
| Quotes | Turn a rate search into a quote to your customer, then list, open and download your quotes. |
| Locations | Look up the UN/LOCODE port codes and IATA airport codes the other endpoints take. |
How it works
- One address, plain JSON. Every request is HTTPS. Every response is JSON in the same envelope:
success,data, anderrorswhen something went wrong. The one exception is quote downloads, which are Excel files. - Company keys. Keys belong to your organization, not to a person, so an integration keeps working when someone leaves. See API keys.
- Permissions per key. Give each key only what it needs: read rates, read quotes, or create quotes.
- Built for retries. Reads are always safe to send again. Creating a quote is too, with an idempotency key.
This site is a preview. Everything here works against the sandbox, https://api-dev.highqube.ai, which has test data and takes test keys (hq_test_…). Test keys are created at dev.highqube.ai. The production address comes with launch.
