The easiest way to integrate with the BRT API

Add the BRT API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship with Italy's largest private parcel carrier alongside Poste Italiane, GLS, and 170+ other carriers.

Courier API integration graphic for brt

The easiest way to integrate with the BRT API

Add the BRT API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship with Italy's largest private parcel carrier alongside Poste Italiane, GLS, and 170+ other carriers.

Courier API integration graphic for brt

The easiest way to integrate with the BRT API

Add the BRT API to your WMS, ERP, or e-commerce backend through one Sendcloud integration. Ship with Italy's largest private parcel carrier alongside Poste Italiane, GLS, and 170+ other carriers.

Courier API integration graphic for brt

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?

Skip the BRT contract negotiation

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

Mid-transit redirects and morning delivery

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?

Skip the BRT contract negotiation

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

Mid-transit redirects and morning delivery

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?

Skip the BRT contract negotiation

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

Mid-transit redirects and morning delivery

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 BRT API through Sendcloud instead of directly?

Direct BRT (Bartolini) integration requires customer codes, FTP passwords, and separate rate codes for national and international (EuroExpress, DPDGroup, Direct2PUDO, Return from Shop). On top of that, you need webservices activation by your BRT account manager, including IP allowlisting for production.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for BRT alongside every other carrier. If you don't have a direct BRT contract, Sendcloud's negotiated rates work in Italy with a minimum of 100 parcels per month and 10 per pickup.

What happens when BRT updates or breaks their API?

BRT periodically updates webservice payloads, rate codes, and surcharge rules. Direct integrators have to re-test against BRT's webservice environment, request new credentials when changes affect authentication, and update field mappings whenever rate codes shift.

When you ship BRT through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering monitors BRT's webservice changes and adjusts the carrier connector internally. One caveat: if you rotate BRT credentials (customer code, FTP password, or rate codes), update them in your Sendcloud contract too. Otherwise the connection breaks.

Can I use my own BRT contract?

Yes. Sendcloud supports both Sendcloud-negotiated BRT rates and your own direct BRT contract.

Sendcloud rates require a minimum of 100 parcels per month and 10 per pickup. If you ship fewer than 100 parcels for three consecutive months, BRT may deactivate the carrier on your account. A Lite plan or above is required.

For your own BRT contract: go to Shipping > Carriers > My Contracts, find BRT, click Add Contract, enter your customer code, FTP password, rate codes, and tick Use BRT webservice. Ask your BRT account manager to enable webservices for your customer code and to whitelist Sendcloud's production IPs.

See the BRT (Bartolini) own contract activation Help Center article.

Which BRT (Bartolini) products are supported through the API?

Through Sendcloud, you can ship the full BRT (Bartolini) product line:

  • BRT Express: next-working-day national home delivery

  • BRT Priority 12:00: delivery by midday the next working day

  • BRT 10:30: urgent express delivery by 10:30 AM

  • BRT Express to Fermopoint: pickup-point delivery

  • BRT Returns: standard return service

  • International methods through EuroExpress, DPDGroup, and Direct2PUDO rate codes (own-contract only)

Sicily, Calabria, and Sardinia have a 2 to 3 working day transit time on most methods. See the BRT (Bartolini) shipping conditions Help Center article.

Which BRT-specific features does the API expose?

BRT-specific features exposed through the integration:

  • NOT@HOME procedure: automatic Fermopoint redirect after the first failed delivery, with a 10-day pickup window plus 10-day extended hold

  • Fermopoint pickup-point routing: recipient picks one of three nearby pickup locations within 1 to 3 km

  • Multi-parcel shipments for national delivery

  • CashService cash-on-delivery (own-contract only)

  • AdditionalInsuranceService for declared values (own-contract only)

  • Same-day grouping: parcels for the same recipient on the same day are auto-grouped

  • Proof of delivery available on request as a paid add-on

How do I track BRT parcels?

BRT tracking includes the NOT@HOME Fermopoint redirect: when the first delivery attempt fails, the parcel is redirected to a Fermopoint pickup point and the redirect appears as a standard delivery event with the redirected location in the payload.

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

BRT exposes returns through BRT Express to Fermopoint (drop-off at a BRT pickup point) and the standard BRT Returns service. For own-contract shipping, the Return from Shop rate code must be enabled on your contract to generate Fermopoint return labels.

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 BRT, 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 BRT alongside DHL, GLS, Poste Italiane, and DPD, 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 BRT'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 BRT API through Sendcloud instead of directly?

Direct BRT (Bartolini) integration requires customer codes, FTP passwords, and separate rate codes for national and international (EuroExpress, DPDGroup, Direct2PUDO, Return from Shop). On top of that, you need webservices activation by your BRT account manager, including IP allowlisting for production.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for BRT alongside every other carrier. If you don't have a direct BRT contract, Sendcloud's negotiated rates work in Italy with a minimum of 100 parcels per month and 10 per pickup.

What happens when BRT updates or breaks their API?

BRT periodically updates webservice payloads, rate codes, and surcharge rules. Direct integrators have to re-test against BRT's webservice environment, request new credentials when changes affect authentication, and update field mappings whenever rate codes shift.

When you ship BRT through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering monitors BRT's webservice changes and adjusts the carrier connector internally. One caveat: if you rotate BRT credentials (customer code, FTP password, or rate codes), update them in your Sendcloud contract too. Otherwise the connection breaks.

Can I use my own BRT contract?

Yes. Sendcloud supports both Sendcloud-negotiated BRT rates and your own direct BRT contract.

Sendcloud rates require a minimum of 100 parcels per month and 10 per pickup. If you ship fewer than 100 parcels for three consecutive months, BRT may deactivate the carrier on your account. A Lite plan or above is required.

For your own BRT contract: go to Shipping > Carriers > My Contracts, find BRT, click Add Contract, enter your customer code, FTP password, rate codes, and tick Use BRT webservice. Ask your BRT account manager to enable webservices for your customer code and to whitelist Sendcloud's production IPs.

See the BRT (Bartolini) own contract activation Help Center article.

Which BRT (Bartolini) products are supported through the API?

Through Sendcloud, you can ship the full BRT (Bartolini) product line:

  • BRT Express: next-working-day national home delivery

  • BRT Priority 12:00: delivery by midday the next working day

  • BRT 10:30: urgent express delivery by 10:30 AM

  • BRT Express to Fermopoint: pickup-point delivery

  • BRT Returns: standard return service

  • International methods through EuroExpress, DPDGroup, and Direct2PUDO rate codes (own-contract only)

Sicily, Calabria, and Sardinia have a 2 to 3 working day transit time on most methods. See the BRT (Bartolini) shipping conditions Help Center article.

Which BRT-specific features does the API expose?

BRT-specific features exposed through the integration:

  • NOT@HOME procedure: automatic Fermopoint redirect after the first failed delivery, with a 10-day pickup window plus 10-day extended hold

  • Fermopoint pickup-point routing: recipient picks one of three nearby pickup locations within 1 to 3 km

  • Multi-parcel shipments for national delivery

  • CashService cash-on-delivery (own-contract only)

  • AdditionalInsuranceService for declared values (own-contract only)

  • Same-day grouping: parcels for the same recipient on the same day are auto-grouped

  • Proof of delivery available on request as a paid add-on

How do I track BRT parcels?

BRT tracking includes the NOT@HOME Fermopoint redirect: when the first delivery attempt fails, the parcel is redirected to a Fermopoint pickup point and the redirect appears as a standard delivery event with the redirected location in the payload.

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

BRT exposes returns through BRT Express to Fermopoint (drop-off at a BRT pickup point) and the standard BRT Returns service. For own-contract shipping, the Return from Shop rate code must be enabled on your contract to generate Fermopoint return labels.

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 BRT, 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 BRT alongside DHL, GLS, Poste Italiane, and DPD, 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 BRT'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 BRT API through Sendcloud instead of directly?

Direct BRT (Bartolini) integration requires customer codes, FTP passwords, and separate rate codes for national and international (EuroExpress, DPDGroup, Direct2PUDO, Return from Shop). On top of that, you need webservices activation by your BRT account manager, including IP allowlisting for production.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for BRT alongside every other carrier. If you don't have a direct BRT contract, Sendcloud's negotiated rates work in Italy with a minimum of 100 parcels per month and 10 per pickup.

What happens when BRT updates or breaks their API?

BRT periodically updates webservice payloads, rate codes, and surcharge rules. Direct integrators have to re-test against BRT's webservice environment, request new credentials when changes affect authentication, and update field mappings whenever rate codes shift.

When you ship BRT through the Sendcloud REST API, the abstraction layer takes the hit. Sendcloud's engineering monitors BRT's webservice changes and adjusts the carrier connector internally. One caveat: if you rotate BRT credentials (customer code, FTP password, or rate codes), update them in your Sendcloud contract too. Otherwise the connection breaks.

Can I use my own BRT contract?

Yes. Sendcloud supports both Sendcloud-negotiated BRT rates and your own direct BRT contract.

Sendcloud rates require a minimum of 100 parcels per month and 10 per pickup. If you ship fewer than 100 parcels for three consecutive months, BRT may deactivate the carrier on your account. A Lite plan or above is required.

For your own BRT contract: go to Shipping > Carriers > My Contracts, find BRT, click Add Contract, enter your customer code, FTP password, rate codes, and tick Use BRT webservice. Ask your BRT account manager to enable webservices for your customer code and to whitelist Sendcloud's production IPs.

See the BRT (Bartolini) own contract activation Help Center article.

Which BRT (Bartolini) products are supported through the API?

Through Sendcloud, you can ship the full BRT (Bartolini) product line:

  • BRT Express: next-working-day national home delivery

  • BRT Priority 12:00: delivery by midday the next working day

  • BRT 10:30: urgent express delivery by 10:30 AM

  • BRT Express to Fermopoint: pickup-point delivery

  • BRT Returns: standard return service

  • International methods through EuroExpress, DPDGroup, and Direct2PUDO rate codes (own-contract only)

Sicily, Calabria, and Sardinia have a 2 to 3 working day transit time on most methods. See the BRT (Bartolini) shipping conditions Help Center article.

Which BRT-specific features does the API expose?

BRT-specific features exposed through the integration:

  • NOT@HOME procedure: automatic Fermopoint redirect after the first failed delivery, with a 10-day pickup window plus 10-day extended hold

  • Fermopoint pickup-point routing: recipient picks one of three nearby pickup locations within 1 to 3 km

  • Multi-parcel shipments for national delivery

  • CashService cash-on-delivery (own-contract only)

  • AdditionalInsuranceService for declared values (own-contract only)

  • Same-day grouping: parcels for the same recipient on the same day are auto-grouped

  • Proof of delivery available on request as a paid add-on

How do I track BRT parcels?

BRT tracking includes the NOT@HOME Fermopoint redirect: when the first delivery attempt fails, the parcel is redirected to a Fermopoint pickup point and the redirect appears as a standard delivery event with the redirected location in the payload.

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

BRT exposes returns through BRT Express to Fermopoint (drop-off at a BRT pickup point) and the standard BRT Returns service. For own-contract shipping, the Return from Shop rate code must be enabled on your contract to generate Fermopoint return labels.

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 BRT, 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 BRT alongside DHL, GLS, Poste Italiane, and DPD, 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 BRT'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