> ## Documentation Index
> Fetch the complete documentation index at: https://sendcloud.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Returns overview

The Sendcloud Returns API lets you create standalone return labels programmatically. No need to have shipped the original parcel through Sendcloud — this API works with any return scenario.

## What you can do

* [Create return labels](/api/v3/returns/create-a-return)
* [Validate returns](/api/v3/returns/validate-a-return) before creating labels
* [Retrieve return](/api/v3/returns/retrieve-a-return) tracking information and status updates
* [Cancel return labels](/api/v3/returns/request-cancellation-of-a-return)
* [Filter returns](/api/v3/returns/retrieve-a-list-of-returns) by creation date, status, or other criteria

## Returns API

Easily and efficiently create returns, even if the outgoing parcel was not shipped by Sendcloud. The Returns API endpoints support international returns and customs documentation, and gives you the ability to quickly look up which shipping method is most appropriate for your return.

<Card title="Returns API" icon="rotate-left" href="/api/v3/returns" horizontal>
  Explore the Returns API documentation and API playground
</Card>

## Key differences from our Return portal API \[deprecated]

The old Return portal API required you to:

1. Look up the original outgoing parcel
2. Generate JWT tokens from the lookup
3. Use those tokens to create a return

The v3 Returns API is simpler:

* No outgoing parcel lookup required
* Works with standard API authentication
* Creates standalone returns from any source

## Synchronous vs Asynchronous

We offer both a [synchronous](/api/v3/returns/create-a-return-synchronously) and [asynchronous version](/api/v3/returns/create-a-return) of the same endpoint. Which one you should use generally depends on your data quality and performance needs. Provided your data quality is up to par using the [asynchronous endpoint](/api/v3/returns/create-a-return) is what we would recommend. It is a more performant endpoint.
