The easiest way to integrate with the Spring API
Add the Spring API to your e-commerce backend, WMS, or 3PL stack through one Sendcloud integration. Ship cross-border via Spring's 30+ last-mile partner network alongside 170+ other couriers.
The easiest way to integrate with the Spring API
Add the Spring API to your e-commerce backend, WMS, or 3PL stack through one Sendcloud integration. Ship cross-border via Spring's 30+ last-mile partner network alongside 170+ other couriers.
The easiest way to integrate with the Spring API
Add the Spring API to your e-commerce backend, WMS, or 3PL stack through one Sendcloud integration. Ship cross-border via Spring's 30+ last-mile partner network alongside 170+ other couriers.
Easy to use and thoroughly documented
Tested on millions of shipments
Available on all plans
Why integrate Spring via the Sendcloud API?
Small parcel cross-border via 30+ partners
Spring Global is a cross-border mail and parcel courier owned by PostNL. Sendcloud handles courier selection, label format, and tracking consolidation for each destination.
Unified tracking across all Spring partners
Spring selects the last-mile partner per destination for the best transit-cost balance. Sendcloud normalises tracking events from each partner into a single response, so your logic stays consistent across destinations.
Integrate with 170+ couriers at once
Stop maintaining and integrating different couriers and use one API for all.
GDPR Compliance
We comply with the GDPR rules to protect data and privacy in Europe.
API uptime of 99.99%
Reliable shipping software built on AWS and with leading market technologies.
ISO 27001 Certified
The world’s most rigorous standards for information security.
The complete shipping API for any system
Shipping API
Get rates, create shipments, download labels, configure webhooks and so much more.
Checkout API
Retrieve the list of active couriers, query service points by GPS location, and check their availability.
Tracking API
Track parcels in real time, retrieve delivery time stamps, and consolidate statuses in an easy-to-read format.
Returns API
Build your own returns portal, find the nearest service point, create return shipments, and download return labels.
Webhooks API
Get parcel status, return, and integration updates pushed to your endpoint the moment they happen.
"Sendcloud allows us to connect to a lot of different couriers seamlessly."
Oscar Ziegler
Founder and CEO
-
Hive
API integration examples
Service Point Picker
See how to integrate the Service Point Picker into a custom application.
Where do you start?
Questions & answers
Why integrate the Spring API via Sendcloud rather than directly?
Direct Spring integration means handling Spring's API key authentication and managing 30+ partner-courier service codes (Spring x EVRi, Spring x DPD DE, Spring x Bartolini, Spring x PostNL Parcel Benelux, etc.) where each maps to a different last-mile courier.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Spring alongside every other courier in your account. A direct Spring contract is required either way; Sendcloud rates aren’t offered for Spring.
What happens when Spring updates or breaks their API?
Spring periodically updates the partner-courier services available on its network and the routing rules between Spring and last-mile couriers. Direct integrators have to refresh credentials when authentication updates and adjust to new or deprecated service codes.
When you ship Spring through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Spring's documentation and adjusts the courier connector internally. The same endpoints work whether your shipment routes through Spring x EVRi, Spring x DPD DE, or Spring x PostNL Parcel Benelux.
Can I use my own Spring contract?
Yes, and you have to. Spring requires a direct contract; Sendcloud rates aren't offered. Contact Spring directly to acquire one.
In Sendcloud, go to Shipping > Couriers > My Contracts, click Add your own contract, find Spring, and click Add Contract. Enter the API key from your Spring account manager. A Lite, Growth, or Premium plan is required.
The partner-courier services available depend on what's enabled in your Spring contract; contact your Spring account manager to expand the list.
Which Spring products are supported through the API?
Spring's full partner-courier network is available through the integration. Examples include:
Spring x EVRi Standard,Spring x EVRi Next Day, with signature and collect variantsSpring x DPD DESpring x Bartolini Home DeliverySpring x Colis Prive(Sign and No Sign)Spring x Italian Post CronoandCrono ExpressSpring x PostNL Parcel BeneluxandParcel EUSpring ExpressandSpring Express Clear(incoterm DDP)
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your Spring contract.
Which Spring-specific features does the API expose?
Spring-specific cross-border features exposed through the integration:
Partner-courier routing across 30+ services through one Spring contract: each service is preconfigured to route through the right last-mile courier (EVRi, DPD, PostNL, La Poste, Bring, Bartolini, etc.)
Cross-border consolidation: Spring handles the linehaul and partner handover, you ship one method per region
Incoterm DDP options on selected international methods (e.g.
Spring Express Clear,Spring Mini Clear) for Delivered Duty Paid shipmentsSame Sendcloud endpoints as every other courier in your account, no Spring-specific routing code needed
How do I track Spring parcels?
Spring tracking events flow through Sendcloud's webhook system regardless of which partner courier handles the last mile. Whether the parcel routes through EVRi, DPD, PostNL, or Bartolini, the event taxonomy stays consistent.
All events normalise to Sendcloud's status taxonomy through GET https://panel.sendcloud.sc/api/v2/tracking/{tracking_number}, with the chronological history under statuses and each event mapped to parent_status. Subscribe to the parcel-status-changed webhook for push updates. Reference: Tracking parcels.
How do I create Spring return labels?
Spring return availability varies by partner-courier service. For example, Spring x EVRi Standard - Collect provides a collection-based return flow. The Sendcloud shipping-methods endpoint shows which Spring return methods are enabled on your contract.
All return labels are created through Sendcloud's standalone v3 Returns API (synchronous or asynchronous; async is recommended for higher throughput). No outgoing parcel lookup or JWT tokens are required. Reference: Returns API overview.
How does Sendcloud's multi-carrier API compare to connecting couriers individually?
The Sendcloud REST API gives you access to 170+ couriers, including Spring, through one credential set, one schema, one webhook stream, and one error model. Connecting couriers individually means handling separate authentication, payload formats, and tracking systems for each, and redoing the work every time a courier ships breaking changes upstream.
With Sendcloud, you ship Spring alongside DHL, UPS, FedEx, and PostNL, or any other courier in your account using the same code. Route shipments between couriers based on rules (weight, destination, service level, cost) without writing courier-specific routing logic. Fall back to alternative couriers automatically if Spring's upstream system has issues.
Adding a new courier later means adding it to your Sendcloud account, not building a new integration.
Questions & answers
Why integrate the Spring API via Sendcloud rather than directly?
Direct Spring integration means handling Spring's API key authentication and managing 30+ partner-courier service codes (Spring x EVRi, Spring x DPD DE, Spring x Bartolini, Spring x PostNL Parcel Benelux, etc.) where each maps to a different last-mile courier.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Spring alongside every other courier in your account. A direct Spring contract is required either way; Sendcloud rates aren’t offered for Spring.
What happens when Spring updates or breaks their API?
Spring periodically updates the partner-courier services available on its network and the routing rules between Spring and last-mile couriers. Direct integrators have to refresh credentials when authentication updates and adjust to new or deprecated service codes.
When you ship Spring through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Spring's documentation and adjusts the courier connector internally. The same endpoints work whether your shipment routes through Spring x EVRi, Spring x DPD DE, or Spring x PostNL Parcel Benelux.
Can I use my own Spring contract?
Yes, and you have to. Spring requires a direct contract; Sendcloud rates aren't offered. Contact Spring directly to acquire one.
In Sendcloud, go to Shipping > Couriers > My Contracts, click Add your own contract, find Spring, and click Add Contract. Enter the API key from your Spring account manager. A Lite, Growth, or Premium plan is required.
The partner-courier services available depend on what's enabled in your Spring contract; contact your Spring account manager to expand the list.
Which Spring products are supported through the API?
Spring's full partner-courier network is available through the integration. Examples include:
Spring x EVRi Standard,Spring x EVRi Next Day, with signature and collect variantsSpring x DPD DESpring x Bartolini Home DeliverySpring x Colis Prive(Sign and No Sign)Spring x Italian Post CronoandCrono ExpressSpring x PostNL Parcel BeneluxandParcel EUSpring ExpressandSpring Express Clear(incoterm DDP)
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your Spring contract.
Which Spring-specific features does the API expose?
Spring-specific cross-border features exposed through the integration:
Partner-courier routing across 30+ services through one Spring contract: each service is preconfigured to route through the right last-mile courier (EVRi, DPD, PostNL, La Poste, Bring, Bartolini, etc.)
Cross-border consolidation: Spring handles the linehaul and partner handover, you ship one method per region
Incoterm DDP options on selected international methods (e.g.
Spring Express Clear,Spring Mini Clear) for Delivered Duty Paid shipmentsSame Sendcloud endpoints as every other courier in your account, no Spring-specific routing code needed
How do I track Spring parcels?
Spring tracking events flow through Sendcloud's webhook system regardless of which partner courier handles the last mile. Whether the parcel routes through EVRi, DPD, PostNL, or Bartolini, the event taxonomy stays consistent.
All events normalise to Sendcloud's status taxonomy through GET https://panel.sendcloud.sc/api/v2/tracking/{tracking_number}, with the chronological history under statuses and each event mapped to parent_status. Subscribe to the parcel-status-changed webhook for push updates. Reference: Tracking parcels.
How do I create Spring return labels?
Spring return availability varies by partner-courier service. For example, Spring x EVRi Standard - Collect provides a collection-based return flow. The Sendcloud shipping-methods endpoint shows which Spring return methods are enabled on your contract.
All return labels are created through Sendcloud's standalone v3 Returns API (synchronous or asynchronous; async is recommended for higher throughput). No outgoing parcel lookup or JWT tokens are required. Reference: Returns API overview.
How does Sendcloud's multi-carrier API compare to connecting couriers individually?
The Sendcloud REST API gives you access to 170+ couriers, including Spring, through one credential set, one schema, one webhook stream, and one error model. Connecting couriers individually means handling separate authentication, payload formats, and tracking systems for each, and redoing the work every time a courier ships breaking changes upstream.
With Sendcloud, you ship Spring alongside DHL, UPS, FedEx, and PostNL, or any other courier in your account using the same code. Route shipments between couriers based on rules (weight, destination, service level, cost) without writing courier-specific routing logic. Fall back to alternative couriers automatically if Spring's upstream system has issues.
Adding a new courier later means adding it to your Sendcloud account, not building a new integration.
Questions & answers
Why integrate the Spring API via Sendcloud rather than directly?
Direct Spring integration means handling Spring's API key authentication and managing 30+ partner-courier service codes (Spring x EVRi, Spring x DPD DE, Spring x Bartolini, Spring x PostNL Parcel Benelux, etc.) where each maps to a different last-mile courier.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Spring alongside every other courier in your account. A direct Spring contract is required either way; Sendcloud rates aren’t offered for Spring.
What happens when Spring updates or breaks their API?
Spring periodically updates the partner-courier services available on its network and the routing rules between Spring and last-mile couriers. Direct integrators have to refresh credentials when authentication updates and adjust to new or deprecated service codes.
When you ship Spring through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Spring's documentation and adjusts the courier connector internally. The same endpoints work whether your shipment routes through Spring x EVRi, Spring x DPD DE, or Spring x PostNL Parcel Benelux.
Can I use my own Spring contract?
Yes, and you have to. Spring requires a direct contract; Sendcloud rates aren't offered. Contact Spring directly to acquire one.
In Sendcloud, go to Shipping > Couriers > My Contracts, click Add your own contract, find Spring, and click Add Contract. Enter the API key from your Spring account manager. A Lite, Growth, or Premium plan is required.
The partner-courier services available depend on what's enabled in your Spring contract; contact your Spring account manager to expand the list.
Which Spring products are supported through the API?
Spring's full partner-courier network is available through the integration. Examples include:
Spring x EVRi Standard,Spring x EVRi Next Day, with signature and collect variantsSpring x DPD DESpring x Bartolini Home DeliverySpring x Colis Prive(Sign and No Sign)Spring x Italian Post CronoandCrono ExpressSpring x PostNL Parcel BeneluxandParcel EUSpring ExpressandSpring Express Clear(incoterm DDP)
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your Spring contract.
Which Spring-specific features does the API expose?
Spring-specific cross-border features exposed through the integration:
Partner-courier routing across 30+ services through one Spring contract: each service is preconfigured to route through the right last-mile courier (EVRi, DPD, PostNL, La Poste, Bring, Bartolini, etc.)
Cross-border consolidation: Spring handles the linehaul and partner handover, you ship one method per region
Incoterm DDP options on selected international methods (e.g.
Spring Express Clear,Spring Mini Clear) for Delivered Duty Paid shipmentsSame Sendcloud endpoints as every other courier in your account, no Spring-specific routing code needed
How do I track Spring parcels?
Spring tracking events flow through Sendcloud's webhook system regardless of which partner courier handles the last mile. Whether the parcel routes through EVRi, DPD, PostNL, or Bartolini, the event taxonomy stays consistent.
All events normalise to Sendcloud's status taxonomy through GET https://panel.sendcloud.sc/api/v2/tracking/{tracking_number}, with the chronological history under statuses and each event mapped to parent_status. Subscribe to the parcel-status-changed webhook for push updates. Reference: Tracking parcels.
How do I create Spring return labels?
Spring return availability varies by partner-courier service. For example, Spring x EVRi Standard - Collect provides a collection-based return flow. The Sendcloud shipping-methods endpoint shows which Spring return methods are enabled on your contract.
All return labels are created through Sendcloud's standalone v3 Returns API (synchronous or asynchronous; async is recommended for higher throughput). No outgoing parcel lookup or JWT tokens are required. Reference: Returns API overview.
How does Sendcloud's multi-carrier API compare to connecting couriers individually?
The Sendcloud REST API gives you access to 170+ couriers, including Spring, through one credential set, one schema, one webhook stream, and one error model. Connecting couriers individually means handling separate authentication, payload formats, and tracking systems for each, and redoing the work every time a courier ships breaking changes upstream.
With Sendcloud, you ship Spring alongside DHL, UPS, FedEx, and PostNL, or any other courier in your account using the same code. Route shipments between couriers based on rules (weight, destination, service level, cost) without writing courier-specific routing logic. Fall back to alternative couriers automatically if Spring's upstream system has issues.
Adding a new courier later means adding it to your Sendcloud account, not building a new integration.
One API for all your shipping needs
No set-up fees
Same-day integration
Ship with Europe’s top couriers
Product
Solutions
Integrations
© 2026 Sendcloud. All rights reserved
Chamber of Commerce: 66572959
VAT number: NL856613897B01
Product
Integrations
Solutions
Resources
© 2026 Sendcloud. All rights reserved
Chamber of Commerce: 66572959
VAT number: NL856613897B01
Product
© 2026 Sendcloud. All rights reserved
Chamber of Commerce: 66572959
VAT number: NL856613897B01