The easiest way to integrate with the Chronopost API

One Sendcloud integration handles the Chronopost API plus 170+ carriers for any WMS, ERP, or e-commerce backend. Ship with France's leading B2C express carrier, without a separate Chronopost account.

Courier API integration graphic for chronopost

The easiest way to integrate with the Chronopost API

One Sendcloud integration handles the Chronopost API plus 170+ carriers for any WMS, ERP, or e-commerce backend. Ship with France's leading B2C express carrier, without a separate Chronopost account.

Courier API integration graphic for chronopost

The easiest way to integrate with the Chronopost API

One Sendcloud integration handles the Chronopost API plus 170+ carriers for any WMS, ERP, or e-commerce backend. Ship with France's leading B2C express carrier, without a separate Chronopost account.

Courier API integration graphic for chronopost

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 leading B2C express carrier

Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.

Guaranteed delivery hour across France

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 leading B2C express carrier

Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.

Guaranteed delivery hour across France

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 leading B2C express carrier

Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.

Guaranteed delivery hour across France

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.

"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?

1. Set up your account

2. Get your free API key

3. Start sending requests to the PostNL API

1. Set up your account

2. Get your free API key

3. Start sending requests to the PostNL API

1. Set up your account

2. Get your free API key

3. Start sending requests to the PostNL API

Questions & answers

Why integrate the Chronopost API through Sendcloud instead of directly?

Direct Chronopost integration means managing your contract number and Chronotrace password, and if you use Shop2Shop, managing either a sub-account flow or a separate Chronopost contract entirely. Time-specific products (Chrono 10, 13, 18) and the BAL letterbox method add per-product configuration on top.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Chronopost alongside every other carrier. A direct Chronopost contract is required either way; Sendcloud rates aren't offered for Chronopost.

What happens when Chronopost updates or breaks their API?

Chronopost periodically updates time-specific service definitions, Chrono Shop2Shop routing, and contract-level surcharge rules. Direct integrators absorb credential rotations, payload changes, and method-code revisions for each product variant.

When you ship Chronopost through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering monitors Chronopost's documentation and updates the carrier connector internally. Your Sendcloud request schema stays consistent across Chrono 10, Chrono 13, Chrono 18, Chrono Relais Europe, and Chrono Shop2Shop.

Can I use my own Chronopost contract?

Yes, and you have to. Chronopost requires a direct contract; Sendcloud rates aren't offered. Contact Chronopost to activate one first.

In Sendcloud, go to Shipping > Carriers > My Contracts, find Chronopost, and click Add Contract. Enter the contract number and the password you use for Chronotrace. For Chrono Shop2Shop, enter your credentials in the dedicated Shop2Shop fields if it's a sub-account of your main Chronopost contract, or add a separate Chronopost contract if it's standalone. Activating the wrong contract type can incur public-rate surcharges from Chronopost.

See the Chronopost contract activation Help Center article.

Which Chronopost products are supported through the API?

Through Sendcloud, you can ship Chronopost's full express line:

  • Chrono 10: delivery before 10:00 the next working day

  • Chrono 13: delivery before 13:00

  • Chrono 18: delivery before 18:00

  • Chrono 18 BAL: letterbox delivery for parcels that fit standard letterbox dimensions

  • Chrono Relais Europe: European service-point delivery

  • Chrono Shop2Shop: budget parcel-shop to parcel-shop service (no home delivery, longer transit, separate contract or sub-account)

See the Chronopost shipping conditions Help Center article.

Which Chronopost-specific features does the API expose?

Chronopost-specific features exposed through the integration:

  • Time-specific delivery: Chrono 10, Chrono 13, Chrono 18 with destination postal-code eligibility checks

  • BAL letterbox routing: parcels matching letterbox dimensions go directly into the customer's mailbox without signature

  • Chrono Shop2Shop as a separate sub-account or standalone contract for parcel-shop to parcel-shop economy delivery

  • Pickup scheduling with a minimum of 5 parcels per pickup

  • Failed-delivery redirect: parcel held at a Post Office service point for 14 calendar days, or PUDO for 7 days, before return

  • Shipping rule support to default service-point shipments to Chrono Shop2Shop instead of Chrono Relais Europe

How do I track Chronopost parcels?

Chronopost tracking surfaces time-specific delivery confirmation for Chrono 10, Chrono 13, and Chrono 18. Failed deliveries flag a service-point hold (Post Office for 14 calendar days, PUDO for 7 days) before return.

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 Chronopost return labels?

Chronopost return method availability depends on your contract. The Sendcloud shipping-methods endpoint returns the methods enabled for your account. For Shop2Shop returns, make sure your contract supports the return service or you'll fall back to public rates.

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 Chronopost, 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 Chronopost alongside Colissimo, Mondial Relay, 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 Chronopost'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 Chronopost API through Sendcloud instead of directly?

Direct Chronopost integration means managing your contract number and Chronotrace password, and if you use Shop2Shop, managing either a sub-account flow or a separate Chronopost contract entirely. Time-specific products (Chrono 10, 13, 18) and the BAL letterbox method add per-product configuration on top.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Chronopost alongside every other carrier. A direct Chronopost contract is required either way; Sendcloud rates aren't offered for Chronopost.

What happens when Chronopost updates or breaks their API?

Chronopost periodically updates time-specific service definitions, Chrono Shop2Shop routing, and contract-level surcharge rules. Direct integrators absorb credential rotations, payload changes, and method-code revisions for each product variant.

When you ship Chronopost through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering monitors Chronopost's documentation and updates the carrier connector internally. Your Sendcloud request schema stays consistent across Chrono 10, Chrono 13, Chrono 18, Chrono Relais Europe, and Chrono Shop2Shop.

Can I use my own Chronopost contract?

Yes, and you have to. Chronopost requires a direct contract; Sendcloud rates aren't offered. Contact Chronopost to activate one first.

In Sendcloud, go to Shipping > Carriers > My Contracts, find Chronopost, and click Add Contract. Enter the contract number and the password you use for Chronotrace. For Chrono Shop2Shop, enter your credentials in the dedicated Shop2Shop fields if it's a sub-account of your main Chronopost contract, or add a separate Chronopost contract if it's standalone. Activating the wrong contract type can incur public-rate surcharges from Chronopost.

See the Chronopost contract activation Help Center article.

Which Chronopost products are supported through the API?

Through Sendcloud, you can ship Chronopost's full express line:

  • Chrono 10: delivery before 10:00 the next working day

  • Chrono 13: delivery before 13:00

  • Chrono 18: delivery before 18:00

  • Chrono 18 BAL: letterbox delivery for parcels that fit standard letterbox dimensions

  • Chrono Relais Europe: European service-point delivery

  • Chrono Shop2Shop: budget parcel-shop to parcel-shop service (no home delivery, longer transit, separate contract or sub-account)

See the Chronopost shipping conditions Help Center article.

Which Chronopost-specific features does the API expose?

Chronopost-specific features exposed through the integration:

  • Time-specific delivery: Chrono 10, Chrono 13, Chrono 18 with destination postal-code eligibility checks

  • BAL letterbox routing: parcels matching letterbox dimensions go directly into the customer's mailbox without signature

  • Chrono Shop2Shop as a separate sub-account or standalone contract for parcel-shop to parcel-shop economy delivery

  • Pickup scheduling with a minimum of 5 parcels per pickup

  • Failed-delivery redirect: parcel held at a Post Office service point for 14 calendar days, or PUDO for 7 days, before return

  • Shipping rule support to default service-point shipments to Chrono Shop2Shop instead of Chrono Relais Europe

How do I track Chronopost parcels?

Chronopost tracking surfaces time-specific delivery confirmation for Chrono 10, Chrono 13, and Chrono 18. Failed deliveries flag a service-point hold (Post Office for 14 calendar days, PUDO for 7 days) before return.

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 Chronopost return labels?

Chronopost return method availability depends on your contract. The Sendcloud shipping-methods endpoint returns the methods enabled for your account. For Shop2Shop returns, make sure your contract supports the return service or you'll fall back to public rates.

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 Chronopost, 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 Chronopost alongside Colissimo, Mondial Relay, 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 Chronopost'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 Chronopost API through Sendcloud instead of directly?

Direct Chronopost integration means managing your contract number and Chronotrace password, and if you use Shop2Shop, managing either a sub-account flow or a separate Chronopost contract entirely. Time-specific products (Chrono 10, 13, 18) and the BAL letterbox method add per-product configuration on top.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Chronopost alongside every other carrier. A direct Chronopost contract is required either way; Sendcloud rates aren't offered for Chronopost.

What happens when Chronopost updates or breaks their API?

Chronopost periodically updates time-specific service definitions, Chrono Shop2Shop routing, and contract-level surcharge rules. Direct integrators absorb credential rotations, payload changes, and method-code revisions for each product variant.

When you ship Chronopost through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering monitors Chronopost's documentation and updates the carrier connector internally. Your Sendcloud request schema stays consistent across Chrono 10, Chrono 13, Chrono 18, Chrono Relais Europe, and Chrono Shop2Shop.

Can I use my own Chronopost contract?

Yes, and you have to. Chronopost requires a direct contract; Sendcloud rates aren't offered. Contact Chronopost to activate one first.

In Sendcloud, go to Shipping > Carriers > My Contracts, find Chronopost, and click Add Contract. Enter the contract number and the password you use for Chronotrace. For Chrono Shop2Shop, enter your credentials in the dedicated Shop2Shop fields if it's a sub-account of your main Chronopost contract, or add a separate Chronopost contract if it's standalone. Activating the wrong contract type can incur public-rate surcharges from Chronopost.

See the Chronopost contract activation Help Center article.

Which Chronopost products are supported through the API?

Through Sendcloud, you can ship Chronopost's full express line:

  • Chrono 10: delivery before 10:00 the next working day

  • Chrono 13: delivery before 13:00

  • Chrono 18: delivery before 18:00

  • Chrono 18 BAL: letterbox delivery for parcels that fit standard letterbox dimensions

  • Chrono Relais Europe: European service-point delivery

  • Chrono Shop2Shop: budget parcel-shop to parcel-shop service (no home delivery, longer transit, separate contract or sub-account)

See the Chronopost shipping conditions Help Center article.

Which Chronopost-specific features does the API expose?

Chronopost-specific features exposed through the integration:

  • Time-specific delivery: Chrono 10, Chrono 13, Chrono 18 with destination postal-code eligibility checks

  • BAL letterbox routing: parcels matching letterbox dimensions go directly into the customer's mailbox without signature

  • Chrono Shop2Shop as a separate sub-account or standalone contract for parcel-shop to parcel-shop economy delivery

  • Pickup scheduling with a minimum of 5 parcels per pickup

  • Failed-delivery redirect: parcel held at a Post Office service point for 14 calendar days, or PUDO for 7 days, before return

  • Shipping rule support to default service-point shipments to Chrono Shop2Shop instead of Chrono Relais Europe

How do I track Chronopost parcels?

Chronopost tracking surfaces time-specific delivery confirmation for Chrono 10, Chrono 13, and Chrono 18. Failed deliveries flag a service-point hold (Post Office for 14 calendar days, PUDO for 7 days) before return.

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 Chronopost return labels?

Chronopost return method availability depends on your contract. The Sendcloud shipping-methods endpoint returns the methods enabled for your account. For Shop2Shop returns, make sure your contract supports the return service or you'll fall back to public rates.

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 Chronopost, 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 Chronopost alongside Colissimo, Mondial Relay, 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 Chronopost'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