Reference · built on requestConnectorShipping & logistics

Sendcloud

Parcels, labels, service points, tracking events, returns, and pickups for European carriers from the Sendcloud API.

Request accessPricing ↗

About

Sendcloud is a shipping platform for European retailers that connects shops to carriers under one account. The Shipments API v3 creates and announces outgoing parcels in one call, returns the tracking_number, tracking_url, and label documents, and accepts a to_service_point when the customer picked a parcel shop or locker. The Returns API creates return parcels even for orders that never shipped through Sendcloud. Parcel tracking exposes each event with a Sendcloud status code and the carrier's own message. Webhooks fire per integration when a parcel changes status or a return is created.

With Fibric, an operator reads those status changes and proposes the customer message, the cancellation, or the return for your approval.

This is a reference listing. It documents what Fibric would read from Sendcloud and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Parcel tracking events through GET /parcels/tracking/{tracking_number}, each typed calculated, carrier, claim, or internal, with an expected delivery date
  • parcel_status_changed webhooks per integration, signed in the Sendcloud-Signature header, with a timestamp to order late arrivals
  • return_created webhooks, and returns with per-item return reasons and up-to-date tracking
  • Parcels and their status.code, such as READY_TO_SEND or ANNOUNCED, from the full list at GET /parcels/statuses
  • Orders per integration, including batch-created ones, and the integrations connected to the account
  • Service points for chosen carriers near an address, with an availability check before you ship to one
  • Shipping options and contracts available to the account

Proposed actions

  • Target capability: propose a shipment through POST /shipments/announce with ship_with.shipping_option_code and up to 15 parcels
  • Target capability: propose cancelling a parcel or shipment before the carrier collects it
  • Target capability: propose a return parcel through the Returns API after validating it to avoid unwanted carrier charges
  • Target capability: propose a pickup through the Pickups API
  • Target capability: propose a batch create or update of orders for an integration

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Tell the customer before the carrier does

    Read parcel_status_changed for exceptions and delays, match the parcel to the order, and propose the customer message with the expected delivery date.

    With Carrier Exception, ETA Notice

  • Offer a parcel shop when home delivery fails

    When an address will not validate or a delivery attempt fails, search service points near the customer, check availability, and propose the switch to to_service_point.

    With Missed Delivery, Address Repair

  • Start the return from the support conversation

    Create the return parcel through the Returns API, validate it first, and propose the label and return reasons for the agent to send. The original parcel need not have shipped through Sendcloud.

    With Returns Triage

Requirements

  • A Sendcloud account with an API integration and its Public and Secret keys
  • Carrier contracts or Sendcloud shipping options enabled for the routes you ship
  • An endpoint set as webhook_url on the integration, with webhook feedback enabled
  • For service point delivery, the customer's chosen service point id sent as to_service_point
Authentication
Basic Authentication with the account's Public Key as username and Secret Key as password, or an OAuth 2.0 client_credentials token from account.sendcloud.com with scope api that expires after one hour.

Limits

  • GET calls are limited to 1,000 per minute; POST, PATCH, PUT, and DELETE to 100 per minute with a 15-per-second burst; excess returns 429
  • Failed webhooks are retried 10 times with exponential delay, from 5 minutes up to 1 hour apart, then logged and dropped
  • Shipments API v3 creates outgoing shipments only; returns go through the Returns API
  • Webhooks arrive per integration and may be out of order; use the timestamp in each one

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Sendcloud ↗

Questions and answers

How do I know a webhook came from Sendcloud?
Each request carries a Sendcloud-Signature header: an HMAC-SHA256 of the body using your Secret Key or the Webhook Signature Key. Compute the same hash and compare. Webhooks are scoped to one integration and include a timestamp, since retries can arrive out of order.
What rate limits apply?
Safe methods such as GET allow 1,000 requests per minute. Unsafe methods, meaning POST, PATCH, PUT, and DELETE, allow 100 per minute with a burst of 15 per second. Beyond that Sendcloud answers HTTP 429.
Can I create a return for a parcel that did not ship through Sendcloud?
Yes. The Returns API creates return parcels from national and international destinations without an outgoing parcel in Sendcloud. Validate the return first to avoid unwanted carrier charges, and request cancellation through the API if the customer changes their mind.
Ask about Sendcloud

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Sendcloud through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy