The easiest way to integrate with the TNT API
Add the TNT API to your e-commerce backend, WMS, or 3PL stack through one Sendcloud integration. Ship with TNT alongside DHL, FedEx, and 170+ other carriers, with no separate FedEx migration to manage.
The easiest way to integrate with the TNT API
Add the TNT API to your e-commerce backend, WMS, or 3PL stack through one Sendcloud integration. Ship with TNT alongside DHL, FedEx, and 170+ other carriers, with no separate FedEx migration to manage.
The easiest way to integrate with the TNT API
Add the TNT API to your e-commerce backend, WMS, or 3PL stack through one Sendcloud integration. Ship with TNT alongside DHL, FedEx, and 170+ other carriers, with no separate FedEx migration to manage.
Thoroughly documented
Tested on millions of shipments
Available on all plans
Why integrate TNT through the Sendcloud API?
Italy and cross-border pallet, FedEx-powered
TNT is now part of FedEx but continues as a distinct service in Italy for domestic and pallet freight. Sendcloud connects via the FedEx v2 API, so the carrier migration history stays on Sendcloud's side.
Pallet shipping with duties pre-paid or recipient-paid
Sendcloud can pre-calculate duties at label time (DDP) or transfer customs liability to the recipient (DAP). Both options are set per shipment through the REST API.
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 TNT through the Sendcloud API?
Italy and cross-border pallet, FedEx-powered
TNT is now part of FedEx but continues as a distinct service in Italy for domestic and pallet freight. Sendcloud connects via the FedEx v2 API, so the carrier migration history stays on Sendcloud's side.
Pallet shipping with duties pre-paid or recipient-paid
Sendcloud can pre-calculate duties at label time (DDP) or transfer customs liability to the recipient (DAP). Both options are set per shipment through the REST API.
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 TNT through the Sendcloud API?
Italy and cross-border pallet, FedEx-powered
TNT is now part of FedEx but continues as a distinct service in Italy for domestic and pallet freight. Sendcloud connects via the FedEx v2 API, so the carrier migration history stays on Sendcloud's side.
Pallet shipping with duties pre-paid or recipient-paid
Sendcloud can pre-calculate duties at label time (DDP) or transfer customs liability to the recipient (DAP). Both options are set per shipment through the REST API.
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.
Where do you start?
Where do you start?
Where do you start?
One API for all your shipping needs
No setup fees
Same-day integration
Ship with Europe's top carriers
Questions & answers
Why integrate the TNT API through Sendcloud instead of directly?
TNT is now part of FedEx, and new TNT contracts run through the FedEx v2 integration. Direct integrators have to handle FedEx v2 authentication, TNT-specific Italy/Europe pallet shipment payloads, and rate-code mapping per service tier.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for TNT alongside every other carrier in your account. A direct TNT contract is required either way; Sendcloud rates aren't offered for TNT.
What happens when TNT updates or breaks their API?
The TNT integration is in transition: legacy TNT setups are being deprecated in favor of FedEx v2. Direct integrators have to migrate from old TNT credentials to FedEx v2 production credentials, re-test pallet shipment payloads, and update rate codes.
When you ship TNT through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering tracks the FedEx v2 transition and adjusts the carrier connector internally. Your Sendcloud request schema stays the same whether TNT runs through legacy credentials or FedEx v2.
Can I use my own TNT contract?
Yes, and you have to. New TNT contracts in Sendcloud connect through FedEx v2; Sendcloud rates aren't offered for TNT. Get your FedEx v2 contract credentials from your FedEx or TNT account manager first.
In Sendcloud, go to Shipping > Carriers > My Contracts, search "TNT" (the FedEx logo will appear), and click Add Contract. Enter the FedEx v2 credentials and click Add this contract.
If you have an old standalone TNT contract still in use, contact Sendcloud Support to confirm whether to keep it or migrate. New contracts must use FedEx v2.
See the TNT Italy contract activation via FedEx v2 Help Center article.
Which TNT products are supported through the API?
Through the FedEx v2 integration, you can ship TNT's pallet and international parcel line:
TNT Economy Express International Pallet: pallet shipping up to 1000 kgTNT Economy Express International Palletwithincoterm DDPorincoterm DAP: customs treatment optionsTNT 12:00 Economy Express International Pallet: time-specific pallet delivery
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled for your contract. Specific destinations and rate codes depend on your FedEx v2 contract setup.
Which TNT-specific features does the API expose?
TNT-specific features exposed through the FedEx v2 integration:
International pallet shipping up to 1000 kg per pallet
Time-specific pallet delivery with
TNT 12:00 Economy ExpressIncoterm options at the shipping-method level:
DDP(Delivered Duty Paid) andDAP(Delivered at Place)Same Sendcloud endpoints as every other carrier in your account, no TNT-specific code path needed
Available TNT methods and rates depend on your FedEx v2 contract; ask your FedEx or TNT account manager for the full service matrix.
How do I track TNT parcels?
TNT tracking flows through the FedEx v2 connector. Pallet-shipment events and incoterm-specific milestones (DDP customs clearance, DAP arrival) appear in the standard webhook stream alongside generic delivery events.
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 TNT return labels?
TNT return method availability depends on your FedEx v2 contract setup. International incoterm options (DDP, DAP) carry through to return shipments where supported. 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 TNT, 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 TNT alongside DHL, FedEx, UPS, and GLS, 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 TNT'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 TNT API through Sendcloud instead of directly?
TNT is now part of FedEx, and new TNT contracts run through the FedEx v2 integration. Direct integrators have to handle FedEx v2 authentication, TNT-specific Italy/Europe pallet shipment payloads, and rate-code mapping per service tier.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for TNT alongside every other carrier in your account. A direct TNT contract is required either way; Sendcloud rates aren't offered for TNT.
What happens when TNT updates or breaks their API?
The TNT integration is in transition: legacy TNT setups are being deprecated in favor of FedEx v2. Direct integrators have to migrate from old TNT credentials to FedEx v2 production credentials, re-test pallet shipment payloads, and update rate codes.
When you ship TNT through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering tracks the FedEx v2 transition and adjusts the carrier connector internally. Your Sendcloud request schema stays the same whether TNT runs through legacy credentials or FedEx v2.
Can I use my own TNT contract?
Yes, and you have to. New TNT contracts in Sendcloud connect through FedEx v2; Sendcloud rates aren't offered for TNT. Get your FedEx v2 contract credentials from your FedEx or TNT account manager first.
In Sendcloud, go to Shipping > Carriers > My Contracts, search "TNT" (the FedEx logo will appear), and click Add Contract. Enter the FedEx v2 credentials and click Add this contract.
If you have an old standalone TNT contract still in use, contact Sendcloud Support to confirm whether to keep it or migrate. New contracts must use FedEx v2.
See the TNT Italy contract activation via FedEx v2 Help Center article.
Which TNT products are supported through the API?
Through the FedEx v2 integration, you can ship TNT's pallet and international parcel line:
TNT Economy Express International Pallet: pallet shipping up to 1000 kgTNT Economy Express International Palletwithincoterm DDPorincoterm DAP: customs treatment optionsTNT 12:00 Economy Express International Pallet: time-specific pallet delivery
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled for your contract. Specific destinations and rate codes depend on your FedEx v2 contract setup.
Which TNT-specific features does the API expose?
TNT-specific features exposed through the FedEx v2 integration:
International pallet shipping up to 1000 kg per pallet
Time-specific pallet delivery with
TNT 12:00 Economy ExpressIncoterm options at the shipping-method level:
DDP(Delivered Duty Paid) andDAP(Delivered at Place)Same Sendcloud endpoints as every other carrier in your account, no TNT-specific code path needed
Available TNT methods and rates depend on your FedEx v2 contract; ask your FedEx or TNT account manager for the full service matrix.
How do I track TNT parcels?
TNT tracking flows through the FedEx v2 connector. Pallet-shipment events and incoterm-specific milestones (DDP customs clearance, DAP arrival) appear in the standard webhook stream alongside generic delivery events.
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 TNT return labels?
TNT return method availability depends on your FedEx v2 contract setup. International incoterm options (DDP, DAP) carry through to return shipments where supported. 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 TNT, 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 TNT alongside DHL, FedEx, UPS, and GLS, 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 TNT'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 TNT API through Sendcloud instead of directly?
TNT is now part of FedEx, and new TNT contracts run through the FedEx v2 integration. Direct integrators have to handle FedEx v2 authentication, TNT-specific Italy/Europe pallet shipment payloads, and rate-code mapping per service tier.
Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for TNT alongside every other carrier in your account. A direct TNT contract is required either way; Sendcloud rates aren't offered for TNT.
What happens when TNT updates or breaks their API?
The TNT integration is in transition: legacy TNT setups are being deprecated in favor of FedEx v2. Direct integrators have to migrate from old TNT credentials to FedEx v2 production credentials, re-test pallet shipment payloads, and update rate codes.
When you ship TNT through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering tracks the FedEx v2 transition and adjusts the carrier connector internally. Your Sendcloud request schema stays the same whether TNT runs through legacy credentials or FedEx v2.
Can I use my own TNT contract?
Yes, and you have to. New TNT contracts in Sendcloud connect through FedEx v2; Sendcloud rates aren't offered for TNT. Get your FedEx v2 contract credentials from your FedEx or TNT account manager first.
In Sendcloud, go to Shipping > Carriers > My Contracts, search "TNT" (the FedEx logo will appear), and click Add Contract. Enter the FedEx v2 credentials and click Add this contract.
If you have an old standalone TNT contract still in use, contact Sendcloud Support to confirm whether to keep it or migrate. New contracts must use FedEx v2.
See the TNT Italy contract activation via FedEx v2 Help Center article.
Which TNT products are supported through the API?
Through the FedEx v2 integration, you can ship TNT's pallet and international parcel line:
TNT Economy Express International Pallet: pallet shipping up to 1000 kgTNT Economy Express International Palletwithincoterm DDPorincoterm DAP: customs treatment optionsTNT 12:00 Economy Express International Pallet: time-specific pallet delivery
The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled for your contract. Specific destinations and rate codes depend on your FedEx v2 contract setup.
Which TNT-specific features does the API expose?
TNT-specific features exposed through the FedEx v2 integration:
International pallet shipping up to 1000 kg per pallet
Time-specific pallet delivery with
TNT 12:00 Economy ExpressIncoterm options at the shipping-method level:
DDP(Delivered Duty Paid) andDAP(Delivered at Place)Same Sendcloud endpoints as every other carrier in your account, no TNT-specific code path needed
Available TNT methods and rates depend on your FedEx v2 contract; ask your FedEx or TNT account manager for the full service matrix.
How do I track TNT parcels?
TNT tracking flows through the FedEx v2 connector. Pallet-shipment events and incoterm-specific milestones (DDP customs clearance, DAP arrival) appear in the standard webhook stream alongside generic delivery events.
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 TNT return labels?
TNT return method availability depends on your FedEx v2 contract setup. International incoterm options (DDP, DAP) carry through to return shipments where supported. 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 TNT, 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 TNT alongside DHL, FedEx, UPS, and GLS, 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 TNT's upstream system has issues.
Adding a new carrier later means adding it to your Sendcloud account, not building a new integration.
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