Royal MailShipping APIukRESTActive

Royal Mail Shipping API V3 (REST, UK)

Royal Mail's REST shipping surface for UK origin shipments. Bearer-token authentication issued through the Royal Mail Customer Portal, separate from any Click & Drop UI session.

Royal Mail Shipping API V3 is the REST surface for shipments originating in the UK on Royal Mail's network. It covers shipment creation, label retrieval, manifest closing, and tracking-event lookup. Authentication is a static bearer API token issued through the Royal Mail Customer Portal — not OAuth. The token rides on every request in an `Authorization: Bearer <token>` header and must be treated as a long-lived secret. The most common first-time integration confusion is treating the API as a programmatic mirror of the Click & Drop web UI. They are related but not identical: Click & Drop sessions and Shipping API V3 tokens are separate credentials, and some operations available in Click & Drop (like complex multi-leg returns) require additional Royal Mail-side configuration before they are available through the API. Operationally, Shipping API V3 returns label artifacts as base64-encoded payloads embedded in the JSON response. Label-format negotiation (PDF, ZPL, EPL) happens via request parameters, and printer drift between sandbox-style proofs and production printers is a recurring incident category. Manifesting is explicit: shipments must be added to a manifest and the manifest closed before the carrier handover, and missed manifest closes are a frequent cause of unexpected shipment-status drift downstream.

Surface details

API name
Royal Mail Shipping API V3
Authentication
Bearer API token issued through Royal Mail Customer Portal
Production base URL
https://api.royalmail.net/shipping/v3
Sandbox notes
Royal Mail's sandbox availability varies by product and customer agreement. Confirm sandbox access in your Royal Mail customer portal; treat any rate or label generated outside production as non-authoritative.
OpenAPI / REST reference
https://developer.royalmail.net/

Frequently asked questions

Does Royal Mail Shipping API V3 use OAuth 2.0?

No. It uses a static bearer API token issued through the Royal Mail Customer Portal. Treat the token as a long-lived secret, store it server-side, and rotate it through the portal when staff changes.

Is a Click & Drop session the same as a Shipping API V3 token?

No. Click & Drop is the web UI and uses session credentials. Shipping API V3 uses a separate bearer token. They are not interchangeable.

Why are my labels missing after a successful create call?

The most common cause is a missed manifest close. Royal Mail requires shipments to be added to a manifest and the manifest closed before carrier handover; otherwise downstream tracking and billing can drift. Verify the manifest workflow in your integration.

Related concepts

Tooling and references

Sources

Last reviewed: 2026-04-25