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
- Royal Mail Developer Documentation (Shipping API V3)
Royal Mail's REST shipping surface for UK origin shipments. Bearer-token auth issued through the Royal Mail Customer Portal.
Sources
Last reviewed: 2026-04-25