The easiest way to integrate with the NACEX API
Add the NACEX API to your WMS, ERP, or e-commerce backend through one Sendcloud integration, alongside 170+ other carriers. Skip the NACEX onboarding, skip the breaking-change chase.
The easiest way to integrate with the NACEX API
Add the NACEX API to your WMS, ERP, or e-commerce backend through one Sendcloud integration, alongside 170+ other carriers. Skip the NACEX onboarding, skip the breaking-change chase.
The easiest way to integrate with the NACEX API
Add the NACEX API to your WMS, ERP, or e-commerce backend through one Sendcloud integration, alongside 170+ other carriers. Skip the NACEX onboarding, skip the breaking-change chase.
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?
Correos Group express for the Iberian peninsula
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
2,300+ convenience store drop-off points
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?
Correos Group express for the Iberian peninsula
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
2,300+ convenience store drop-off points
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?
Correos Group express for the Iberian peninsula
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
2,300+ convenience store drop-off points
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 NACEX API through Sendcloud instead of directly?
Direct NACEX integration means managing Client ID, Secret, Customer Code (NACEX subscriber number), and Customer Delegation, plus coordinating with your local NACEX branch for setup.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for NACEX alongside every other carrier in your account. A direct NACEX contract is required either way; Sendcloud rates aren't offered for NACEX.
What happens when NACEX updates or breaks their API?
NACEX periodically updates authentication and shipping-method definitions. Direct integrators have to refresh credentials when changes affect authentication and re-test payloads when NACEX adjusts service tiers.
When you ship NACEX through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors NACEX's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own NACEX contract?
Yes, and you have to. NACEX requires a direct contract; Sendcloud rates aren't offered. Activate direct debit in Sendcloud first.
Contact your local NACEX branch or account manager for your customer code and customer delegation number. In Sendcloud, go to Shipping > Carriers > My Contracts, find NACEX, and click Add Contract. Enter your Client ID, Secret, Customer Code (NACEX subscriber number), and Customer Delegation. A Lite, Growth, or Premium plan is required.
Which NACEX products are supported through the API?
Through Sendcloud, you can ship NACEX's full Iberian product line:
e-NACEX 0-40 kg: next-day delivery (or by 1 PM second working day for locations 50+ km from a NACEX office), with optional Cash on Deliverye-NACEX Shop 0-20 kg: delivery to 2,300+ NACEX.shop locationse-NACEX Economy 0-20 kg: 48-72 hour deliveryReturn Service via e-NACEX Shop: drop-off return at NACEX.shop locations
NACEX covers Spain, Andorra, and Portugal. See the NACEX shipping conditions Help Center article.
Which NACEX-specific features does the API expose?
NACEX-specific features exposed through the integration:
2,300+ NACEX.shop locations across Spain, Andorra, and Portugal
Express tier (24-hour) and Economy tier (48-72 hour)
Cash on Delivery on most methods
2 delivery attempts on standard home delivery
Distance rule: locations more than 50 km from a NACEX office (100 km round trip) deliver by 1 PM the second working day
Proof of delivery on every shipment
How do I track NACEX parcels?
NACEX tracking surfaces NACEX.shop drop-off events alongside home-delivery events through the same webhook stream. The 2,300+ NACEX.shop locations show up in the payload as drop-off and pickup points where applicable.
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 NACEX return labels?
NACEX exposes returns through Return Service via e-NACEX Shop. Customers drop returns at any of the 2,300+ NACEX.shop locations across Spain, Andorra, and Portugal.
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 NACEX, 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 NACEX alongside Correos, SEUR, MRW, 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 NACEX'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 NACEX API through Sendcloud instead of directly?
Direct NACEX integration means managing Client ID, Secret, Customer Code (NACEX subscriber number), and Customer Delegation, plus coordinating with your local NACEX branch for setup.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for NACEX alongside every other carrier in your account. A direct NACEX contract is required either way; Sendcloud rates aren't offered for NACEX.
What happens when NACEX updates or breaks their API?
NACEX periodically updates authentication and shipping-method definitions. Direct integrators have to refresh credentials when changes affect authentication and re-test payloads when NACEX adjusts service tiers.
When you ship NACEX through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors NACEX's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own NACEX contract?
Yes, and you have to. NACEX requires a direct contract; Sendcloud rates aren't offered. Activate direct debit in Sendcloud first.
Contact your local NACEX branch or account manager for your customer code and customer delegation number. In Sendcloud, go to Shipping > Carriers > My Contracts, find NACEX, and click Add Contract. Enter your Client ID, Secret, Customer Code (NACEX subscriber number), and Customer Delegation. A Lite, Growth, or Premium plan is required.
Which NACEX products are supported through the API?
Through Sendcloud, you can ship NACEX's full Iberian product line:
e-NACEX 0-40 kg: next-day delivery (or by 1 PM second working day for locations 50+ km from a NACEX office), with optional Cash on Deliverye-NACEX Shop 0-20 kg: delivery to 2,300+ NACEX.shop locationse-NACEX Economy 0-20 kg: 48-72 hour deliveryReturn Service via e-NACEX Shop: drop-off return at NACEX.shop locations
NACEX covers Spain, Andorra, and Portugal. See the NACEX shipping conditions Help Center article.
Which NACEX-specific features does the API expose?
NACEX-specific features exposed through the integration:
2,300+ NACEX.shop locations across Spain, Andorra, and Portugal
Express tier (24-hour) and Economy tier (48-72 hour)
Cash on Delivery on most methods
2 delivery attempts on standard home delivery
Distance rule: locations more than 50 km from a NACEX office (100 km round trip) deliver by 1 PM the second working day
Proof of delivery on every shipment
How do I track NACEX parcels?
NACEX tracking surfaces NACEX.shop drop-off events alongside home-delivery events through the same webhook stream. The 2,300+ NACEX.shop locations show up in the payload as drop-off and pickup points where applicable.
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 NACEX return labels?
NACEX exposes returns through Return Service via e-NACEX Shop. Customers drop returns at any of the 2,300+ NACEX.shop locations across Spain, Andorra, and Portugal.
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 NACEX, 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 NACEX alongside Correos, SEUR, MRW, 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 NACEX'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 NACEX API through Sendcloud instead of directly?
Direct NACEX integration means managing Client ID, Secret, Customer Code (NACEX subscriber number), and Customer Delegation, plus coordinating with your local NACEX branch for setup.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for NACEX alongside every other carrier in your account. A direct NACEX contract is required either way; Sendcloud rates aren't offered for NACEX.
What happens when NACEX updates or breaks their API?
NACEX periodically updates authentication and shipping-method definitions. Direct integrators have to refresh credentials when changes affect authentication and re-test payloads when NACEX adjusts service tiers.
When you ship NACEX through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors NACEX's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own NACEX contract?
Yes, and you have to. NACEX requires a direct contract; Sendcloud rates aren't offered. Activate direct debit in Sendcloud first.
Contact your local NACEX branch or account manager for your customer code and customer delegation number. In Sendcloud, go to Shipping > Carriers > My Contracts, find NACEX, and click Add Contract. Enter your Client ID, Secret, Customer Code (NACEX subscriber number), and Customer Delegation. A Lite, Growth, or Premium plan is required.
Which NACEX products are supported through the API?
Through Sendcloud, you can ship NACEX's full Iberian product line:
e-NACEX 0-40 kg: next-day delivery (or by 1 PM second working day for locations 50+ km from a NACEX office), with optional Cash on Deliverye-NACEX Shop 0-20 kg: delivery to 2,300+ NACEX.shop locationse-NACEX Economy 0-20 kg: 48-72 hour deliveryReturn Service via e-NACEX Shop: drop-off return at NACEX.shop locations
NACEX covers Spain, Andorra, and Portugal. See the NACEX shipping conditions Help Center article.
Which NACEX-specific features does the API expose?
NACEX-specific features exposed through the integration:
2,300+ NACEX.shop locations across Spain, Andorra, and Portugal
Express tier (24-hour) and Economy tier (48-72 hour)
Cash on Delivery on most methods
2 delivery attempts on standard home delivery
Distance rule: locations more than 50 km from a NACEX office (100 km round trip) deliver by 1 PM the second working day
Proof of delivery on every shipment
How do I track NACEX parcels?
NACEX tracking surfaces NACEX.shop drop-off events alongside home-delivery events through the same webhook stream. The 2,300+ NACEX.shop locations show up in the payload as drop-off and pickup points where applicable.
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 NACEX return labels?
NACEX exposes returns through Return Service via e-NACEX Shop. Customers drop returns at any of the 2,300+ NACEX.shop locations across Spain, Andorra, and Portugal.
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 NACEX, 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 NACEX alongside Correos, SEUR, MRW, 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 NACEX'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



