Loading…
The Connexx REST API covers shipment creation, rate comparison, label generation, tracking, carrier management, and customs. Authentication is bearer-token, the API is documented in OpenAPI 3.1, and median response time is under 200ms. Below: the full reference, the live status page, the changelog, webhooks, rate limits, and SDK examples.
Quick start
A POST to /v1/shipments runs live rate comparison across every connected carrier, returns the selected carrier, the label URL, and the tracking number.
curl -X POST https://api.itdglobal.com/v1/shipments \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": { "postcode": "M1 1AA", "country": "GB" },
"to": { "postcode": "EH1 1YZ", "country": "GB" },
"parcel": { "weight_kg": 2.5, "length_cm": 30, "width_cm": 20, "height_cm": 10 },
"service_preference": "cheapest"
}'Everything you need to integrate, in one place.
API documentation
The full reference for every Connexx endpoint. Create shipments, compare rates across every connected carrier, generate labels, track parcels, and manage carrier accounts. OpenAPI 3.1 spec, request/response examples, and a try-it-now console.
Open the API referenceStatus page
Live status across the API, the dashboard, carrier integrations, and webhooks. Incident history, scheduled maintenance, and component-level uptime over the last 90 days.
View status pageChangelog
Every API change, dated, with the version it applies to and the migration path where breaking. Backwards-compatible additions, deprecations with notice periods, and bug fixes that affect API behaviour.
Read the changelogWebhooks
Subscribe to shipment lifecycle events: created, label_generated, manifested, in_transit, delivered, exception, returned. Payloads are JSON, signed with HMAC-SHA256. Retries follow exponential backoff up to 24 hours.
Webhook referenceSDKs and API clients
Working code examples in Node.js, Python, PHP, and Ruby for the most common workflows: create a shipment, fetch rates, generate a label, subscribe to a webhook. Copy, adapt, and ship.
View API client examplesRate limits and authentication
Bearer-token authentication with separate keys for staging and production. Default rate limit is 100 requests per second per account, burst up to 200. Higher tiers available on Enterprise. Key rotation supported without downtime.
Authentication guideConnexx is a REST API for multi-carrier shipping. The API covers shipment creation, live rate comparison across every connected carrier, label generation, tracking, webhook subscriptions, carrier account management, and customs documentation. The API uses bearer-token authentication, returns JSON, and is documented in OpenAPI 3.1. Median response time is under 200ms.
API keys are issued from the Connexx dashboard under Settings, then API Keys. Each account has separate keys for staging and production. Keys can be rotated without downtime by issuing a new key, updating your client, and revoking the old key. Existing customers get keys immediately. New customers get keys at the end of onboarding.
The default rate limit is 100 requests per second per account, with a burst of up to 200 for short-lived spikes. Webhook delivery is not subject to the rate limit. Enterprise customers can request higher limits via /help/submit-request. The current limit and remaining quota are returned in every response under X-RateLimit-Limit and X-RateLimit-Remaining.
Yes. Webhooks fire on shipment lifecycle events: created, label_generated, manifested, in_transit, delivered, exception, and returned. Payloads are JSON, signed with HMAC-SHA256 using a per-endpoint secret. Failed deliveries retry with exponential backoff for up to 24 hours.
Working code examples are available in Node.js, Python, PHP, and Ruby covering the most common workflows. Any language with an HTTP client can integrate using the OpenAPI 3.1 spec, which is published at docs.itdglobal.com/openapi. Official SDKs are on the roadmap.
The OpenAPI 3.1 specification is published at docs.itdglobal.com/openapi.yaml. The spec covers every endpoint, request schema, response schema, error type, and authentication method. Generate a client in any language with a code generator like openapi-generator or Stainless. The spec is versioned with the API.
Yes. Every account has a separate staging environment with its own API base URL and its own API key. Staging uses simulated carrier responses, generates non-production labels, and never charges for shipments. The data model is identical to production. Use staging for integration development before promoting to production.