Loop Returns User Management API Guide

Auth method: API Key (X-Authorization header)

Setup steps

1. Log in to the Loop Returns merchant dashboard.
2. Navigate to Settings > Integrations > API.
3. Generate an API key.
4. Include the key in all requests as the X-Authorization header.

User object field mapping is not yet verified for this app.

Endpoint coverage is not yet verified for this app.

• Rate limits: No publicly documented rate limits found in official developer docs.

• Rate-limit headers: Unknown

• Retry-After header: Unknown

• Rate-limit notes: No rate limit tiers or headers documented in official sources as of research date.

• Pagination method: none

• Default page size: Not documented

• Max page size: Not documented

• Pagination pointer: Not documented

• Webhooks available: Yes

• Webhook notes: Loop Returns supports webhooks for returns lifecycle events (e.g., return created, return closed). These are not user-management webhooks.

• Alternative event strategy: No user-provisioning or team-member event webhooks documented.

• Webhook events: return.created, return.closed, return.label_created, return.refunded, return.exchange_created

• SCIM available: No
• SCIM version: Not documented
• Plan required: Not documented
• Endpoint: Not documented

Limitations:

• No SCIM provisioning documented in any official Loop Returns source.
• Team member access is managed manually via the merchant dashboard.
• Google SSO is available for merchant portal login but is not tied to a SCIM or IdP provisioning flow.

Two primary API-supported scenarios are documented. First, return data retrieval: generate an API key, issue GET requests to /api/v1/returns with the X-Authorization header, and parse return objects for order data, reasons, and status.

Second, real-time return lifecycle events via webhook: register an HTTPS endpoint in Settings > Webhooks, select events such as return. created or return.

closed, and validate payloads using the shared secret Loop provides. A third scenario - adding a team member - is UI-only: navigate to Settings > Team, enter the invitee's email, assign a role, and the invitee receives an email to complete setup.

No API endpoint exists to programmatically invite, update, or remove team members, and no user-provisioning webhook events are available.

Automate return data retrieval

1. Generate an API key from the Loop dashboard under Settings > Integrations > API.
2. Send GET requests to https://api.loopreturns.com/api/v1/returns with X-Authorization: .
3. Parse return objects for order data, return reasons, and status.

Watch out for: This is the primary documented use case; user/team-member management is not available via API.

Receive real-time return events via webhook

1. In the Loop dashboard, navigate to Settings > Webhooks.
2. Register an HTTPS endpoint URL.
3. Select events (e.g., return.created, return.closed).
4. Validate incoming payloads using the shared secret provided by Loop.

Watch out for: Webhook events cover returns lifecycle only; no user-provisioning events are available.

Add a team member to Loop Returns

1. Log in to the Loop merchant dashboard.
2. Navigate to Settings > Team.
3. Enter the team member's email and assign a role.
4. The invitee receives an email to accept and set up access.

Watch out for: This is a manual UI-only process. No API endpoint exists to programmatically invite, update, or remove team members.

The core API trap with Loop Returns is scope mismatch: developers expecting user management endpoints will find none. API keys are scoped to a shop/merchant account, not to individual team members, so there is no per-user token model to leverage for identity graph construction.

Google SSO is available for merchant portal login but is not configurable via API and is not linked to enterprise IdP provisioning flows (Okta, Entra, OneLogin).

Any integration that assumes Loop will expose team-member lifecycle events - joins, role changes, departures - via webhook or REST will need to be redesigned around manual dashboard workflows instead.