Loop Returns integration
Loop Returns integration for AI agents.
Loop Returns integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Loop Returns tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
What your agents can do
Real Loop Returns actions, managed and audited.
Your user connects Loop Returns once; your agent can then use Loop Returns to inspect and action ecommerce returns, create return deep links, manage notes, and retrieve returns reports — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Loop Returns access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Tools & triggers
Supported Loop Returns tools.
12 tools are generated from the published Loop Returns catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 12 tools. All published catalog entries are included in this page's server-rendered HTML.
- Cancel Return
- Cancel a return in Loop. Canceling a return will allow a customer to make another return with the same items. ### Required API key scope - Returns
- Return Actions
- Close Return
- Close a return. Closing a return will not fulfill any outcomes such as exchanges or gift cards, and the items are not able to be used in a new return. Returns closed using this endpoint will also be closed in the commerce provider (e.g. Shopify). ### Required API key scope - Returns
- Return Actions
- Create Return Deep Link
- Create a deep link URL. Depending on a shop's settings, the `zip` value could be an email, phone number, or postal code. All use the key `zip`. ### Required API key scope - Orders
- Return Actions
- Create Return Deep Link with QR Code
- Generate a link to a QR code image file that, when scanned, will take the user directly to their order in Loop so they can initiate a return without requiring them to enter their order information. The deep link URL is also returned. If `type` is not included in the request, or is a non-supported format, a `png` will be returned. ### Required API key scope - Orders
- Return Actions
- Create Return Note
- Post a new note to a return. ### Required API key scope - Returns
- Return Actions
- Flag Return
- Flag a return in Loop for review. This will prevent automated processing and will require a human to go into the merchant admin in Loop and review this return. ### Required API key scope - Returns
- Return Actions
- Advanced Shipping Notice
- This endpoint will pull all packages by tracking statuses/timeframe. The ASN endpoint will return an array of objects. Those objects will contain order and return information. ### Required API key scope - Returns
- Return Data
- Detailed Returns List
- Pull a detailed list of returns created within a given timeframe. This endpoint supports pagination. We _highly_ encourage using [pagination](https://docs.loopreturns.com/reference/paginated-requests) for this endpoint. Read the guide on [paginating requests](https://docs.loopreturns.com/reference/paginated-requests) for details. **Note**: If neither `from` nor `to` is passed, the response defaults to only contain returns from the previous 24 hours. See [`from`](#parameter-from) and [`to`](#parameter-to) below for more information. **Note**: The maximum number of days in the range of the from and to properties is 120 days. If the number of days in this range exceeds 120 days, a validation error will be returned. **Note**: If no `state` is passed, the response defaults to only contain open, closed, and expired returns. See [`state`](#parameter-state) below for more information. ### Required API key scope - Returns
- Return Data
- Get Return Details
- Get the details of a specific return based on a return's ID, an order name, or an order ID from the commerce provider (e.g. Shopify) depending on the query value of the call. ### Required API key scope - Returns
- Return Data
- Get Return Notes
- Get notes on a specific return using the return's ID. ### Required API key scope - Returns
- Return Actions
- Process Return
- Process a return in Loop based on the return ID. Processing a return will archive it in Loop and fulfill any remaining outcomes, such as placing exchange orders or creating gift cards. > ⚡ **Processing Note** > > This endpoint queues the return for processing. The actual processing occurs in the background. > A successful response indicates the return has been queued, not that processing has completed. > **Note on instant refunds** > > If the return has an open Reshop instant-refund credit, processing is intentionally skipped: a > successful (`true`) response is returned without dispatching any processing jobs. Optionally, you may include a JSON payload in the request body. If you choose to do so, Loop will add these values to any new orders in the commerce provider (e.g. Shopify) that result from processing the return. For example, if the return includes an exchange when the return is processed, Loop will create that exchange order and these values will be added to the order as "Additional Details." Loop will also add a note to the return timeline with the values in the request body. > 🚧 Process Error Codes > > Returns must be in a processable state to successfully process. If your return is not in a > processable state, your response will include an `errors` object with a corresponding message and > error code. > > > If you would like to configure your flagged returns to process, please reach out to > support@loopreturns.com. ```json { "errors": { "message": "Return is open and therefore cannot be processed.", "code": "UNPROCESSABLE_FLAGGED_RETURN" } } ``` ### Required API key scope - Returns
- Return Actions
- Remove Line Items
- Remove line items from a return and process the return. Currently, only line items tied to a refund or store credit outcome allow for line items to be removed programmatically. ### Required API key scope - Returns
- Return Actions
FAQ
Loop Returns integration, answered
- How do AI agents use Loop Returns through Open Connector?
- Your user connects Loop Returns once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Loop Returns tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Loop Returns MCP server?
- Yes. Open Connector can serve Loop Returns as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Loop Returns actions with credentials injected server-side.
- Where do Loop Returns credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Loop Returns — keep the keys.
Open source, self-hostable, with Loop Returns credentials that never leave your infrastructure. Run it from source today.