The easiest way to integrate with the MRW API

One Sendcloud integration connects your WMS, ERP, or e-commerce backend to the MRW API plus 170+ other carriers. No separate MRW contract to set up, no carrier-specific integration to build.

Courier API integration graphic for mrw

The easiest way to integrate with the MRW API

One Sendcloud integration connects your WMS, ERP, or e-commerce backend to the MRW API plus 170+ other carriers. No separate MRW contract to set up, no carrier-specific integration to build.

Courier API integration graphic for mrw

The easiest way to integrate with the MRW API

One Sendcloud integration connects your WMS, ERP, or e-commerce backend to the MRW API plus 170+ other carriers. No separate MRW contract to set up, no carrier-specific integration to build.

Courier API integration graphic for mrw

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?

Same-day and next-morning across Iberia

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

Pre-10:00 and same-day delivery options

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?

Same-day and next-morning across Iberia

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

Pre-10:00 and same-day delivery options

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?

Same-day and next-morning across Iberia

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

Pre-10:00 and same-day delivery options

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

Direct MRW integration means coordinating with integracion@mrw.es to obtain webservice credentials in production mode, configuring Username, Password, Department, Franchise code (5 digits), Subscriber code (6 digits), and managing parcel dimensions for Urgent 19 and multicollo shipments.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for MRW alongside every other carrier in your account. A direct MRW contract is required either way; Sendcloud rates aren't offered for MRW.

What happens when MRW updates or breaks their API?

MRW periodically updates webservice authentication and shipping-method definitions. Direct integrators have to coordinate with their MRW representative when credentials need rotation, request new production-mode access, and re-test payloads.

When you ship MRW through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors MRW's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same. If you change MRW credentials, update them in Sendcloud too. Otherwise the connection breaks.

Can I use my own MRW contract?

Yes, and you have to. MRW requires a direct contract; Sendcloud rates aren't offered.

Email integracion@mrw.es to request webservice credentials. Confirm they're activated in production mode (not test). In Sendcloud, go to Shipping > Carriers > My Contracts > Add my own contract, find MRW, and click Add Contract. Enter Username, Password, Department, Franchise code, and Subscriber code.

For tracking, ask MRW to enable Webservices tracking on your contract. Without it, tracking statuses won't update in Sendcloud. A Lite, Growth, or Premium plan is required.

See the MRW contract activation Help Center article.

Which MRW products are supported through the API?

Through Sendcloud, you can ship MRW's full Iberian product line:

  • MRW Urgent 10:00 0-80kg: next-day before 10:00

  • MRW Urgent 10:00 with delivery confirmation

  • MRW Urgent Today: same-day delivery

  • Standard MRW shipping methods up to 80 kg

  • Multicollo (multi-parcel) shipments

MRW covers Spain (mainland and islands) and Portugal. The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your account.

Which MRW-specific features does the API expose?

MRW-specific features exposed through the integration:

  • Time-specific Urgent products: 10:00, Today, with delivery confirmation variants

  • Multicollo shipments for grouped deliveries

  • Iberian network: Spain mainland and islands plus Portugal

  • Use Sendcloud's Boxes feature with a shipping rule to automate parcel dimensions for Urgent 19 and multicollo shipments (mandatory)

If your MRW credentials change, update them in Sendcloud immediately to maintain the connection.

How do I track MRW parcels?

MRW tracking via Webservices needs to be enabled by MRW on your contract. If statuses aren't updating, confirm Webservices tracking is active on MRW's side. Once enabled, events flow through Sendcloud's standard 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 MRW return labels?

MRW return method availability depends on your contract setup. Webservices tracking enabled by MRW also applies to return tracking, so confirm both are active to get full return-cycle visibility.

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 MRW, 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 MRW alongside Correos, SEUR, NACEX, 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 MRW'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 MRW API through Sendcloud instead of directly?

Direct MRW integration means coordinating with integracion@mrw.es to obtain webservice credentials in production mode, configuring Username, Password, Department, Franchise code (5 digits), Subscriber code (6 digits), and managing parcel dimensions for Urgent 19 and multicollo shipments.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for MRW alongside every other carrier in your account. A direct MRW contract is required either way; Sendcloud rates aren't offered for MRW.

What happens when MRW updates or breaks their API?

MRW periodically updates webservice authentication and shipping-method definitions. Direct integrators have to coordinate with their MRW representative when credentials need rotation, request new production-mode access, and re-test payloads.

When you ship MRW through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors MRW's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same. If you change MRW credentials, update them in Sendcloud too. Otherwise the connection breaks.

Can I use my own MRW contract?

Yes, and you have to. MRW requires a direct contract; Sendcloud rates aren't offered.

Email integracion@mrw.es to request webservice credentials. Confirm they're activated in production mode (not test). In Sendcloud, go to Shipping > Carriers > My Contracts > Add my own contract, find MRW, and click Add Contract. Enter Username, Password, Department, Franchise code, and Subscriber code.

For tracking, ask MRW to enable Webservices tracking on your contract. Without it, tracking statuses won't update in Sendcloud. A Lite, Growth, or Premium plan is required.

See the MRW contract activation Help Center article.

Which MRW products are supported through the API?

Through Sendcloud, you can ship MRW's full Iberian product line:

  • MRW Urgent 10:00 0-80kg: next-day before 10:00

  • MRW Urgent 10:00 with delivery confirmation

  • MRW Urgent Today: same-day delivery

  • Standard MRW shipping methods up to 80 kg

  • Multicollo (multi-parcel) shipments

MRW covers Spain (mainland and islands) and Portugal. The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your account.

Which MRW-specific features does the API expose?

MRW-specific features exposed through the integration:

  • Time-specific Urgent products: 10:00, Today, with delivery confirmation variants

  • Multicollo shipments for grouped deliveries

  • Iberian network: Spain mainland and islands plus Portugal

  • Use Sendcloud's Boxes feature with a shipping rule to automate parcel dimensions for Urgent 19 and multicollo shipments (mandatory)

If your MRW credentials change, update them in Sendcloud immediately to maintain the connection.

How do I track MRW parcels?

MRW tracking via Webservices needs to be enabled by MRW on your contract. If statuses aren't updating, confirm Webservices tracking is active on MRW's side. Once enabled, events flow through Sendcloud's standard 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 MRW return labels?

MRW return method availability depends on your contract setup. Webservices tracking enabled by MRW also applies to return tracking, so confirm both are active to get full return-cycle visibility.

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 MRW, 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 MRW alongside Correos, SEUR, NACEX, 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 MRW'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 MRW API through Sendcloud instead of directly?

Direct MRW integration means coordinating with integracion@mrw.es to obtain webservice credentials in production mode, configuring Username, Password, Department, Franchise code (5 digits), Subscriber code (6 digits), and managing parcel dimensions for Urgent 19 and multicollo shipments.

Through Sendcloud, you authenticate once with your Sendcloud API key and use a single REST schema for MRW alongside every other carrier in your account. A direct MRW contract is required either way; Sendcloud rates aren't offered for MRW.

What happens when MRW updates or breaks their API?

MRW periodically updates webservice authentication and shipping-method definitions. Direct integrators have to coordinate with their MRW representative when credentials need rotation, request new production-mode access, and re-test payloads.

When you ship MRW through the Sendcloud REST API, the abstraction layer absorbs those changes. Sendcloud's engineering monitors MRW's documentation and adjusts the carrier connector internally. Your Sendcloud request schema stays the same. If you change MRW credentials, update them in Sendcloud too. Otherwise the connection breaks.

Can I use my own MRW contract?

Yes, and you have to. MRW requires a direct contract; Sendcloud rates aren't offered.

Email integracion@mrw.es to request webservice credentials. Confirm they're activated in production mode (not test). In Sendcloud, go to Shipping > Carriers > My Contracts > Add my own contract, find MRW, and click Add Contract. Enter Username, Password, Department, Franchise code, and Subscriber code.

For tracking, ask MRW to enable Webservices tracking on your contract. Without it, tracking statuses won't update in Sendcloud. A Lite, Growth, or Premium plan is required.

See the MRW contract activation Help Center article.

Which MRW products are supported through the API?

Through Sendcloud, you can ship MRW's full Iberian product line:

  • MRW Urgent 10:00 0-80kg: next-day before 10:00

  • MRW Urgent 10:00 with delivery confirmation

  • MRW Urgent Today: same-day delivery

  • Standard MRW shipping methods up to 80 kg

  • Multicollo (multi-parcel) shipments

MRW covers Spain (mainland and islands) and Portugal. The Sendcloud shipping-methods endpoint returns the up-to-date list of methods enabled on your account.

Which MRW-specific features does the API expose?

MRW-specific features exposed through the integration:

  • Time-specific Urgent products: 10:00, Today, with delivery confirmation variants

  • Multicollo shipments for grouped deliveries

  • Iberian network: Spain mainland and islands plus Portugal

  • Use Sendcloud's Boxes feature with a shipping rule to automate parcel dimensions for Urgent 19 and multicollo shipments (mandatory)

If your MRW credentials change, update them in Sendcloud immediately to maintain the connection.

How do I track MRW parcels?

MRW tracking via Webservices needs to be enabled by MRW on your contract. If statuses aren't updating, confirm Webservices tracking is active on MRW's side. Once enabled, events flow through Sendcloud's standard 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 MRW return labels?

MRW return method availability depends on your contract setup. Webservices tracking enabled by MRW also applies to return tracking, so confirm both are active to get full return-cycle visibility.

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 MRW, 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 MRW alongside Correos, SEUR, NACEX, 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 MRW'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