The easiest way to integrate with the Budbee API
Add the Budbee API to your WMS, ERP, or marketplace through one Sendcloud integration alongside 170+ other carriers. Ship via Nordic last-mile with consumer-controlled delivery windows, without a separate Budbee connector.
The easiest way to integrate with the Budbee API
Add the Budbee API to your WMS, ERP, or marketplace through one Sendcloud integration alongside 170+ other carriers. Ship via Nordic last-mile with consumer-controlled delivery windows, without a separate Budbee connector.
The easiest way to integrate with the Budbee API
Add the Budbee API to your WMS, ERP, or marketplace through one Sendcloud integration alongside 170+ other carriers. Ship via Nordic last-mile with consumer-controlled delivery windows, without a separate Budbee connector.
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?
Consumer-controlled Nordic last-mile
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Recipient-chosen delivery windows
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?
Consumer-controlled Nordic last-mile
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Recipient-chosen delivery windows
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?
Consumer-controlled Nordic last-mile
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Recipient-chosen delivery windows
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 Budbee API through Sendcloud instead of directly?
Direct Budbee integration means managing API Key, API Secret, and Collection ID per region (Dutch and Belgian Collection IDs need separate accounts), plus the 2,000+ shipments-per-month minimum to qualify for a contract.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Budbee alongside every other carrier in your account. A direct Budbee contract is required either way; Sendcloud rates aren't offered for Budbee.
What happens when Budbee updates or breaks their API?
Budbee periodically updates API authentication and Collection ID handling. Direct integrators have to refresh credentials when changes affect authentication and re-test payloads when Budbee adjusts flexible delivery window logic.
When you ship Budbee through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Budbee's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own Budbee contract?
Yes, and you have to. Budbee requires a direct contract with at least 2,000+ shipments per month. Reach out to Budbee directly to set one up; Sendcloud rates aren't offered.
In Sendcloud, go to Shipping > Carriers, find Budbee, and click Enable own contract. Add your contract under My Contracts with the API Key, API Secret, and Collection ID from your Budbee account information. A Lite, Growth, or Premium plan is required.
If you have both a Dutch and a Belgian Collection ID, only one is visible per Sendcloud account. Create two separate Sendcloud accounts to manage both Collection IDs and have correct sender addresses on labels.
Which Budbee products are supported through the API?
Sendcloud connects to Budbee's last-mile delivery network in the Benelux and the Nordics. Specific shipping methods depend on your contract and Collection ID; the Sendcloud shipping-methods endpoint returns the up-to-date list.
Budbee specializes in flexible delivery windows, where the recipient can pick a precise time slot for delivery instead of waiting for a generic delivery window.
Which Budbee-specific features does the API expose?
Budbee-specific last-mile features exposed through the integration:
Flexible delivery windows: recipient picks a precise time slot
Collection ID-based sender address: each Collection ID maps to one sender address per Sendcloud account
Nordic and Benelux network coverage
Same Sendcloud endpoints as every other carrier in your account
For Dutch and Belgian operations under the same brand, set up two Sendcloud accounts (one per Collection ID).
How do I track Budbee parcels?
Budbee tracking surfaces the recipient's chosen flexible delivery window alongside standard delivery events. Events flow through Sendcloud's webhook stream, including last-mile updates as the parcel moves through Budbee's Nordic and Benelux network.
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 Budbee return labels?
Budbee returns are tied to your Collection ID, which determines the sender address on the return label. Use separate Sendcloud accounts for Dutch vs Belgian return flows so each Collection ID maps to the right return-from address.
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 Budbee, 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 Budbee alongside PostNord, Bring, PostNL, 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 Budbee'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 Budbee API through Sendcloud instead of directly?
Direct Budbee integration means managing API Key, API Secret, and Collection ID per region (Dutch and Belgian Collection IDs need separate accounts), plus the 2,000+ shipments-per-month minimum to qualify for a contract.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Budbee alongside every other carrier in your account. A direct Budbee contract is required either way; Sendcloud rates aren't offered for Budbee.
What happens when Budbee updates or breaks their API?
Budbee periodically updates API authentication and Collection ID handling. Direct integrators have to refresh credentials when changes affect authentication and re-test payloads when Budbee adjusts flexible delivery window logic.
When you ship Budbee through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Budbee's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own Budbee contract?
Yes, and you have to. Budbee requires a direct contract with at least 2,000+ shipments per month. Reach out to Budbee directly to set one up; Sendcloud rates aren't offered.
In Sendcloud, go to Shipping > Carriers, find Budbee, and click Enable own contract. Add your contract under My Contracts with the API Key, API Secret, and Collection ID from your Budbee account information. A Lite, Growth, or Premium plan is required.
If you have both a Dutch and a Belgian Collection ID, only one is visible per Sendcloud account. Create two separate Sendcloud accounts to manage both Collection IDs and have correct sender addresses on labels.
Which Budbee products are supported through the API?
Sendcloud connects to Budbee's last-mile delivery network in the Benelux and the Nordics. Specific shipping methods depend on your contract and Collection ID; the Sendcloud shipping-methods endpoint returns the up-to-date list.
Budbee specializes in flexible delivery windows, where the recipient can pick a precise time slot for delivery instead of waiting for a generic delivery window.
Which Budbee-specific features does the API expose?
Budbee-specific last-mile features exposed through the integration:
Flexible delivery windows: recipient picks a precise time slot
Collection ID-based sender address: each Collection ID maps to one sender address per Sendcloud account
Nordic and Benelux network coverage
Same Sendcloud endpoints as every other carrier in your account
For Dutch and Belgian operations under the same brand, set up two Sendcloud accounts (one per Collection ID).
How do I track Budbee parcels?
Budbee tracking surfaces the recipient's chosen flexible delivery window alongside standard delivery events. Events flow through Sendcloud's webhook stream, including last-mile updates as the parcel moves through Budbee's Nordic and Benelux network.
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 Budbee return labels?
Budbee returns are tied to your Collection ID, which determines the sender address on the return label. Use separate Sendcloud accounts for Dutch vs Belgian return flows so each Collection ID maps to the right return-from address.
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 Budbee, 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 Budbee alongside PostNord, Bring, PostNL, 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 Budbee'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 Budbee API through Sendcloud instead of directly?
Direct Budbee integration means managing API Key, API Secret, and Collection ID per region (Dutch and Belgian Collection IDs need separate accounts), plus the 2,000+ shipments-per-month minimum to qualify for a contract.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for Budbee alongside every other carrier in your account. A direct Budbee contract is required either way; Sendcloud rates aren't offered for Budbee.
What happens when Budbee updates or breaks their API?
Budbee periodically updates API authentication and Collection ID handling. Direct integrators have to refresh credentials when changes affect authentication and re-test payloads when Budbee adjusts flexible delivery window logic.
When you ship Budbee through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors Budbee's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own Budbee contract?
Yes, and you have to. Budbee requires a direct contract with at least 2,000+ shipments per month. Reach out to Budbee directly to set one up; Sendcloud rates aren't offered.
In Sendcloud, go to Shipping > Carriers, find Budbee, and click Enable own contract. Add your contract under My Contracts with the API Key, API Secret, and Collection ID from your Budbee account information. A Lite, Growth, or Premium plan is required.
If you have both a Dutch and a Belgian Collection ID, only one is visible per Sendcloud account. Create two separate Sendcloud accounts to manage both Collection IDs and have correct sender addresses on labels.
Which Budbee products are supported through the API?
Sendcloud connects to Budbee's last-mile delivery network in the Benelux and the Nordics. Specific shipping methods depend on your contract and Collection ID; the Sendcloud shipping-methods endpoint returns the up-to-date list.
Budbee specializes in flexible delivery windows, where the recipient can pick a precise time slot for delivery instead of waiting for a generic delivery window.
Which Budbee-specific features does the API expose?
Budbee-specific last-mile features exposed through the integration:
Flexible delivery windows: recipient picks a precise time slot
Collection ID-based sender address: each Collection ID maps to one sender address per Sendcloud account
Nordic and Benelux network coverage
Same Sendcloud endpoints as every other carrier in your account
For Dutch and Belgian operations under the same brand, set up two Sendcloud accounts (one per Collection ID).
How do I track Budbee parcels?
Budbee tracking surfaces the recipient's chosen flexible delivery window alongside standard delivery events. Events flow through Sendcloud's webhook stream, including last-mile updates as the parcel moves through Budbee's Nordic and Benelux network.
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 Budbee return labels?
Budbee returns are tied to your Collection ID, which determines the sender address on the return label. Use separate Sendcloud accounts for Dutch vs Belgian return flows so each Collection ID maps to the right return-from address.
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 Budbee, 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 Budbee alongside PostNord, Bring, PostNL, 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 Budbee'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