The LandMark Global API, minus the integration work
Add the LandMark Global API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship cross-border with flexible customs handling alongside DHL, UPS, and 170+ other carriers.
The LandMark Global API, minus the integration work
Add the LandMark Global API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship cross-border with flexible customs handling alongside DHL, UPS, and 170+ other carriers.
The LandMark Global API, minus the integration work
Add the LandMark Global API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship cross-border with flexible customs handling alongside DHL, UPS, and 170+ other carriers.
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?
Cross-border delivery with flexible customs handling
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Two label types for import and export
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?
Cross-border delivery with flexible customs handling
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Two label types for import and export
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?
Cross-border delivery with flexible customs handling
Ship under Sendcloud's negotiated PostNL rates from day one, or bring your own contract when you're ready.
Two label types for import and export
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 LandMark Global API through Sendcloud instead of directly?
Direct LandMark Global integration means choosing between Import Request (white-label) and Ship Request (final-mile carrier label) flows, managing Username, Password, Client ID, Account Number, Region, and Label Type per shipment, plus handling per-final-mile-carrier label routing.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for LandMark Global alongside every other carrier in your account. A direct LandMark Global contract is required either way; Sendcloud rates aren't offered for LandMark Global.
What happens when LandMark Global updates or breaks their API?
LandMark Global periodically updates the Import Request and Ship Request flows, final-mile carrier integrations, and customs documentation requirements. Direct integrators have to track changes across both label types and re-test payloads when final-mile carriers shift.
When you ship LandMark Global through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors LandMark Global's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own LandMark Global contract?
Yes, and you have to. LandMark Global requires a direct contract; Sendcloud rates aren't offered.
In Sendcloud, go to Shipping > Carriers > My Contracts, click Add your own contract, find LandMark Global, and click Add Contract. Enter Username, Password, Client ID, Account Number, Label Type (Import Request or Ship Request), and Region from the LandMark Global portal.
A Lite, Growth, or Premium plan is required. See the LandMark Global own contract activation Help Center article.
Which LandMark Global products are supported through the API?
Through Sendcloud, you can ship LandMark Global's international last-mile services:
LandMark Global Bpack Bussable(Belgium)LandMark Global MaxiPak DAPandMaxiPak DDPLandMark Global Maxipak Scan DDPwith optional Saturday deliveryRegion-specific final-mile carriers depending on destination and contract
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your account.
Which LandMark Global-specific features does the API expose?
LandMark Global-specific features exposed through the integration:
Import Request: white-label generic label to ship items to LandMark's facility, where they're processed and re-labeled with the final-mile carrier labelShip Request: final-mile carrier label API directly, label generated at your facility using the final-mile carrier's label, ready for direct injectionCross-border last-mile through region-specific final-mile carriers
DDP and DAP incoterms on international shipments
How do I track LandMark Global parcels?
LandMark Global tracking includes final-mile carrier handoffs and customs clearance status. Whether your label is generated through Import Request or Ship Request, the event stream stays consistent in Sendcloud's status 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 LandMark Global return labels?
LandMark Global return method availability depends on your contract and region, including DDP and DAP incoterms for international return shipments. The Sendcloud shipping-methods endpoint shows which methods are 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 LandMark Global, 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 LandMark Global alongside DHL, UPS, FedEx, and Asendia, 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 LandMark Global'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 LandMark Global API through Sendcloud instead of directly?
Direct LandMark Global integration means choosing between Import Request (white-label) and Ship Request (final-mile carrier label) flows, managing Username, Password, Client ID, Account Number, Region, and Label Type per shipment, plus handling per-final-mile-carrier label routing.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for LandMark Global alongside every other carrier in your account. A direct LandMark Global contract is required either way; Sendcloud rates aren't offered for LandMark Global.
What happens when LandMark Global updates or breaks their API?
LandMark Global periodically updates the Import Request and Ship Request flows, final-mile carrier integrations, and customs documentation requirements. Direct integrators have to track changes across both label types and re-test payloads when final-mile carriers shift.
When you ship LandMark Global through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors LandMark Global's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own LandMark Global contract?
Yes, and you have to. LandMark Global requires a direct contract; Sendcloud rates aren't offered.
In Sendcloud, go to Shipping > Carriers > My Contracts, click Add your own contract, find LandMark Global, and click Add Contract. Enter Username, Password, Client ID, Account Number, Label Type (Import Request or Ship Request), and Region from the LandMark Global portal.
A Lite, Growth, or Premium plan is required. See the LandMark Global own contract activation Help Center article.
Which LandMark Global products are supported through the API?
Through Sendcloud, you can ship LandMark Global's international last-mile services:
LandMark Global Bpack Bussable(Belgium)LandMark Global MaxiPak DAPandMaxiPak DDPLandMark Global Maxipak Scan DDPwith optional Saturday deliveryRegion-specific final-mile carriers depending on destination and contract
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your account.
Which LandMark Global-specific features does the API expose?
LandMark Global-specific features exposed through the integration:
Import Request: white-label generic label to ship items to LandMark's facility, where they're processed and re-labeled with the final-mile carrier labelShip Request: final-mile carrier label API directly, label generated at your facility using the final-mile carrier's label, ready for direct injectionCross-border last-mile through region-specific final-mile carriers
DDP and DAP incoterms on international shipments
How do I track LandMark Global parcels?
LandMark Global tracking includes final-mile carrier handoffs and customs clearance status. Whether your label is generated through Import Request or Ship Request, the event stream stays consistent in Sendcloud's status 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 LandMark Global return labels?
LandMark Global return method availability depends on your contract and region, including DDP and DAP incoterms for international return shipments. The Sendcloud shipping-methods endpoint shows which methods are 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 LandMark Global, 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 LandMark Global alongside DHL, UPS, FedEx, and Asendia, 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 LandMark Global'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 LandMark Global API through Sendcloud instead of directly?
Direct LandMark Global integration means choosing between Import Request (white-label) and Ship Request (final-mile carrier label) flows, managing Username, Password, Client ID, Account Number, Region, and Label Type per shipment, plus handling per-final-mile-carrier label routing.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for LandMark Global alongside every other carrier in your account. A direct LandMark Global contract is required either way; Sendcloud rates aren't offered for LandMark Global.
What happens when LandMark Global updates or breaks their API?
LandMark Global periodically updates the Import Request and Ship Request flows, final-mile carrier integrations, and customs documentation requirements. Direct integrators have to track changes across both label types and re-test payloads when final-mile carriers shift.
When you ship LandMark Global through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors LandMark Global's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same.
Can I use my own LandMark Global contract?
Yes, and you have to. LandMark Global requires a direct contract; Sendcloud rates aren't offered.
In Sendcloud, go to Shipping > Carriers > My Contracts, click Add your own contract, find LandMark Global, and click Add Contract. Enter Username, Password, Client ID, Account Number, Label Type (Import Request or Ship Request), and Region from the LandMark Global portal.
A Lite, Growth, or Premium plan is required. See the LandMark Global own contract activation Help Center article.
Which LandMark Global products are supported through the API?
Through Sendcloud, you can ship LandMark Global's international last-mile services:
LandMark Global Bpack Bussable(Belgium)LandMark Global MaxiPak DAPandMaxiPak DDPLandMark Global Maxipak Scan DDPwith optional Saturday deliveryRegion-specific final-mile carriers depending on destination and contract
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your account.
Which LandMark Global-specific features does the API expose?
LandMark Global-specific features exposed through the integration:
Import Request: white-label generic label to ship items to LandMark's facility, where they're processed and re-labeled with the final-mile carrier labelShip Request: final-mile carrier label API directly, label generated at your facility using the final-mile carrier's label, ready for direct injectionCross-border last-mile through region-specific final-mile carriers
DDP and DAP incoterms on international shipments
How do I track LandMark Global parcels?
LandMark Global tracking includes final-mile carrier handoffs and customs clearance status. Whether your label is generated through Import Request or Ship Request, the event stream stays consistent in Sendcloud's status 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 LandMark Global return labels?
LandMark Global return method availability depends on your contract and region, including DDP and DAP incoterms for international return shipments. The Sendcloud shipping-methods endpoint shows which methods are 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 LandMark Global, 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 LandMark Global alongside DHL, UPS, FedEx, and Asendia, 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 LandMark Global'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