The easiest way to integrate with the Geodis API
Add the Geodis API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship French domestic parcel and European freight alongside 170+ other carriers, with no separate Geodis agreement.
The easiest way to integrate with the Geodis API
Add the Geodis API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship French domestic parcel and European freight alongside 170+ other carriers, with no separate Geodis agreement.
The easiest way to integrate with the Geodis API
Add the Geodis API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship French domestic parcel and European freight alongside 170+ other carriers, with no separate Geodis agreement.
Free plan available
Works with your shop
Cancel anytime
Why integrate PostNL through the Sendcloud API?
Why integrate PostNL through the Sendcloud API?
Why integrate PostNL through the Sendcloud API?
Why integrate PostNL through the Sendcloud API?
France's B2B parcel and freight specialist
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Parcel and freight on one endpoint
PostNL's evening windows and 4,500+ service points are available via Sendcloud's REST API, with no separate PostNL API credentials required.
Integrate with 170+ carriers at once
Stop maintaining and integrating different carrier 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 top market technologies.
ISO 27001 Certified
The world’s most rigorous standards for information security.
Why integrate PostNL through the Sendcloud API?
France's B2B parcel and freight specialist
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Parcel and freight on one endpoint
PostNL's evening windows and 4,500+ service points are available via Sendcloud's REST API, with no separate PostNL API credentials required.
Integrate with 170+ carriers at once
Stop maintaining and integrating different carrier 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 top market technologies.
ISO 27001 Certified
The world’s most rigorous standards for information security.
Why integrate PostNL through the Sendcloud API?
France's B2B parcel and freight specialist
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Parcel and freight on one endpoint
PostNL's evening windows and 4,500+ service points are available via Sendcloud's REST API, with no separate PostNL API credentials required.
Integrate with 170+ carriers at once
Stop maintaining and integrating different carrier 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 top market technologies.
ISO 27001 Certified
The world’s most rigorous standards for information security.
The complete shipping API for any system
The complete shipping API for any system
The complete shipping API for any system
"Sendcloud allows us to connect to a lot of different carriers seamlessly."
Oscar Ziegler
Founder and CEO
-
Hive
"Sendcloud allows us to connect to a lot of different carriers seamlessly."
Oscar Ziegler
Founder and CEO
-
Hive
"Sendcloud allows us to connect to a lot of different carriers seamlessly."
Oscar Ziegler
Founder and CEO
-
Hive
API integration examples
API Integration
See a basic example of an API integration using Python.
Service Point Picker
See how to integrate the Service Point Picker into a custom application.
API integration examples
API Integration
See a basic example of an API integration using Python.
Service Point Picker
See how to integrate the Service Point Picker into a custom application.
API integration examples
API Integration
See a basic example of an API integration using Python.
Service Point Picker
See how to integrate the Service Point Picker into a custom application.
Instantly connect to 170+ couriers Get started now
Free plan available
Works with your shop
Cancel anytime
More than 2,600 five star reviews
Instantly connect to 170+ couriers Get started now
Free plan available
Works with your shop
Cancel anytime
More than 2,600 five star reviews
Where do you start?
Where do you start?
Where do you start?
Questions & answers
Why integrate the Geodis API through Sendcloud instead of directly?
Direct Geodis integration means managing separate API keys for shipments and tracking (the ZoomClient API), handling the Identifier, Depot Code (CodeSA), and Customer Account (CodeClient) on every shipment, and generating end-of-day Geodis manifests in your own code.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Geodis alongside every other carrier in your account. A direct Geodis contract is required either way; Sendcloud rates aren't offered for Geodis.
What happens when Geodis updates or breaks their API?
Geodis maintains separate API endpoints for shipments and tracking (ZoomClient). Direct integrators have to track changes across both, refresh credentials when authentication updates, and re-test payloads when rate codes or depot configurations change.
When you ship Geodis through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Geodis's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same regardless of upstream Geodis changes.
Can I use my own Geodis contract?
Yes, and you have to. Geodis requires a direct contract; Sendcloud rates aren't offered.
Contact Geodis directly for the contract. In Sendcloud, go to Shipping > Carriers > My Contracts, click Add your own contract, find Geodis, and click Add Contract. Enter the Identifier, API Key (Shipments), API Key (Tracking, also called ZoomClient), Depot Code (CodeSA), and Customer Account (CodeClient) from your Geodis account manager.
One depot code per Sendcloud account. If you have multiple Depot codes, you'll need separate Sendcloud accounts. A Lite, Growth, or Premium plan is required.
Which Geodis products are supported through the API?
Through Sendcloud, you can ship Geodis's domestic and European parcel and freight network. Specific shipping methods depend on your contract; the Sendcloud shipping-methods endpoint returns the up-to-date list.
Geodis is a major French logistics provider with parcel and freight services across France and into European destinations. Multicollo (multi-parcel) shipments are supported. Contact your Geodis account manager for the full destinations and service matrix.
Which Geodis-specific features does the API expose?
Geodis-specific features exposed through the integration:
Separate ZoomClient API key for tracking, distinct from the shipments API key
Multicollo (multi-parcel) shipments for grouped deliveries
End-of-day Geodis manifest generation directly in the Sendcloud platform
Depot Code (CodeSA) and Customer Account (CodeClient) routing per shipment
Geodis supports one Depot Code per Sendcloud account; for multiple depots, set up multiple Sendcloud accounts.
How do I track Geodis parcels?
Geodis tracking comes through the ZoomClient API, configured with the separate API Key (Tracking) at contract setup. The tracking key is distinct from the shipments API key. Once both are in place, events flow through Sendcloud's standard taxonomy.
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 Geodis return labels?
Geodis return method availability depends on your contract setup. Multicollo (multi-parcel) return shipments are supported when the contract enables them, useful for grouped reverse logistics. The Sendcloud shipping-methods endpoint returns the methods enabled for your account.
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 carriers individually?
The Sendcloud REST API gives you access to 170+ carriers, including Geodis, through one credential set, one schema, one webhook stream, and one error model. Connecting carriers individually means handling separate authentication, payload formats, and tracking systems for each, and redoing the work every time a carrier ships breaking changes upstream.
With Sendcloud, you ship Geodis alongside Colissimo, Chronopost, DPD, and DHL, or any other carrier in your account using the same code. Route shipments between carriers based on rules (weight, destination, service level, cost) without writing carrier-specific routing logic. Fall back to alternative carriers automatically if Geodis's upstream system has issues.
Adding a new carrier later means adding it to your Sendcloud account, not building a new integration.
Questions & answers
Why integrate the Geodis API through Sendcloud instead of directly?
Direct Geodis integration means managing separate API keys for shipments and tracking (the ZoomClient API), handling the Identifier, Depot Code (CodeSA), and Customer Account (CodeClient) on every shipment, and generating end-of-day Geodis manifests in your own code.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Geodis alongside every other carrier in your account. A direct Geodis contract is required either way; Sendcloud rates aren't offered for Geodis.
What happens when Geodis updates or breaks their API?
Geodis maintains separate API endpoints for shipments and tracking (ZoomClient). Direct integrators have to track changes across both, refresh credentials when authentication updates, and re-test payloads when rate codes or depot configurations change.
When you ship Geodis through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Geodis's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same regardless of upstream Geodis changes.
Can I use my own Geodis contract?
Yes, and you have to. Geodis requires a direct contract; Sendcloud rates aren't offered.
Contact Geodis directly for the contract. In Sendcloud, go to Shipping > Carriers > My Contracts, click Add your own contract, find Geodis, and click Add Contract. Enter the Identifier, API Key (Shipments), API Key (Tracking, also called ZoomClient), Depot Code (CodeSA), and Customer Account (CodeClient) from your Geodis account manager.
One depot code per Sendcloud account. If you have multiple Depot codes, you'll need separate Sendcloud accounts. A Lite, Growth, or Premium plan is required.
Which Geodis products are supported through the API?
Through Sendcloud, you can ship Geodis's domestic and European parcel and freight network. Specific shipping methods depend on your contract; the Sendcloud shipping-methods endpoint returns the up-to-date list.
Geodis is a major French logistics provider with parcel and freight services across France and into European destinations. Multicollo (multi-parcel) shipments are supported. Contact your Geodis account manager for the full destinations and service matrix.
Which Geodis-specific features does the API expose?
Geodis-specific features exposed through the integration:
Separate ZoomClient API key for tracking, distinct from the shipments API key
Multicollo (multi-parcel) shipments for grouped deliveries
End-of-day Geodis manifest generation directly in the Sendcloud platform
Depot Code (CodeSA) and Customer Account (CodeClient) routing per shipment
Geodis supports one Depot Code per Sendcloud account; for multiple depots, set up multiple Sendcloud accounts.
How do I track Geodis parcels?
Geodis tracking comes through the ZoomClient API, configured with the separate API Key (Tracking) at contract setup. The tracking key is distinct from the shipments API key. Once both are in place, events flow through Sendcloud's standard taxonomy.
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 Geodis return labels?
Geodis return method availability depends on your contract setup. Multicollo (multi-parcel) return shipments are supported when the contract enables them, useful for grouped reverse logistics. The Sendcloud shipping-methods endpoint returns the methods enabled for your account.
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 carriers individually?
The Sendcloud REST API gives you access to 170+ carriers, including Geodis, through one credential set, one schema, one webhook stream, and one error model. Connecting carriers individually means handling separate authentication, payload formats, and tracking systems for each, and redoing the work every time a carrier ships breaking changes upstream.
With Sendcloud, you ship Geodis alongside Colissimo, Chronopost, DPD, and DHL, or any other carrier in your account using the same code. Route shipments between carriers based on rules (weight, destination, service level, cost) without writing carrier-specific routing logic. Fall back to alternative carriers automatically if Geodis's upstream system has issues.
Adding a new carrier later means adding it to your Sendcloud account, not building a new integration.
Questions & answers
Why integrate the Geodis API through Sendcloud instead of directly?
Direct Geodis integration means managing separate API keys for shipments and tracking (the ZoomClient API), handling the Identifier, Depot Code (CodeSA), and Customer Account (CodeClient) on every shipment, and generating end-of-day Geodis manifests in your own code.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Geodis alongside every other carrier in your account. A direct Geodis contract is required either way; Sendcloud rates aren't offered for Geodis.
What happens when Geodis updates or breaks their API?
Geodis maintains separate API endpoints for shipments and tracking (ZoomClient). Direct integrators have to track changes across both, refresh credentials when authentication updates, and re-test payloads when rate codes or depot configurations change.
When you ship Geodis through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Geodis's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same regardless of upstream Geodis changes.
Can I use my own Geodis contract?
Yes, and you have to. Geodis requires a direct contract; Sendcloud rates aren't offered.
Contact Geodis directly for the contract. In Sendcloud, go to Shipping > Carriers > My Contracts, click Add your own contract, find Geodis, and click Add Contract. Enter the Identifier, API Key (Shipments), API Key (Tracking, also called ZoomClient), Depot Code (CodeSA), and Customer Account (CodeClient) from your Geodis account manager.
One depot code per Sendcloud account. If you have multiple Depot codes, you'll need separate Sendcloud accounts. A Lite, Growth, or Premium plan is required.
Which Geodis products are supported through the API?
Through Sendcloud, you can ship Geodis's domestic and European parcel and freight network. Specific shipping methods depend on your contract; the Sendcloud shipping-methods endpoint returns the up-to-date list.
Geodis is a major French logistics provider with parcel and freight services across France and into European destinations. Multicollo (multi-parcel) shipments are supported. Contact your Geodis account manager for the full destinations and service matrix.
Which Geodis-specific features does the API expose?
Geodis-specific features exposed through the integration:
Separate ZoomClient API key for tracking, distinct from the shipments API key
Multicollo (multi-parcel) shipments for grouped deliveries
End-of-day Geodis manifest generation directly in the Sendcloud platform
Depot Code (CodeSA) and Customer Account (CodeClient) routing per shipment
Geodis supports one Depot Code per Sendcloud account; for multiple depots, set up multiple Sendcloud accounts.
How do I track Geodis parcels?
Geodis tracking comes through the ZoomClient API, configured with the separate API Key (Tracking) at contract setup. The tracking key is distinct from the shipments API key. Once both are in place, events flow through Sendcloud's standard taxonomy.
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 Geodis return labels?
Geodis return method availability depends on your contract setup. Multicollo (multi-parcel) return shipments are supported when the contract enables them, useful for grouped reverse logistics. The Sendcloud shipping-methods endpoint returns the methods enabled for your account.
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 carriers individually?
The Sendcloud REST API gives you access to 170+ carriers, including Geodis, through one credential set, one schema, one webhook stream, and one error model. Connecting carriers individually means handling separate authentication, payload formats, and tracking systems for each, and redoing the work every time a carrier ships breaking changes upstream.
With Sendcloud, you ship Geodis alongside Colissimo, Chronopost, DPD, and DHL, or any other carrier in your account using the same code. Route shipments between carriers based on rules (weight, destination, service level, cost) without writing carrier-specific routing logic. Fall back to alternative carriers automatically if Geodis's upstream system has issues.
Adding a new carrier later means adding it to your Sendcloud account, not building a new integration.
One API for all your shipping needs
No setup fees
Same-day integration
Ship with Europe’s top carriers
One API for all your shipping needs
No setup fees
Same-day integration
Ship with Europe’s top carriers
One API for all your shipping needs
No setup fees
Same-day integration
Ship with Europe’s top carriers
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