Pre-Built Tooling
| Category | Details |
|---|---|
| Authentication | API Key (Header-based: X-Authorization) |
| Two-Way Sync | No |
| Events Supported | No |
| Realtime | Polling |
| Supports Rate Limiting | Yes |
| Authentication Scopes Supported | N/A (API Key) |
Objects Supported
Alloy Automation supports syncing the following objects from Loop Returns:- Return Actions (process, cancel, close, flag returns)
- Return Data (returns list, advanced shipping notices)
- Return Notes
- Allowlist Items
- Blocklist Items
- Destinations
- Carts
Set Up Guide
Trial Access
| Question | Answer |
|---|---|
| Offers free trial? | Contact Loop Returns for trial information at https://www.loopreturns.com/. Trials are typically available for Shopify merchants. You can also install via the Shopify App Store. |
| Requires paid sandbox | No. Loop provides a test/staging environment for development. |
| Requires partnership to obtain authentication? | No, but you must be a Loop Returns customer (typically a Shopify merchant). |
Authentication (API Key)
Loop Returns uses API Key authentication passed via theX-Authorization header.
How to obtain your API Key
- Sign up for Loop Returns at https://www.loopreturns.com/ or install via the Shopify App Store
- Log in to your Loop Returns admin dashboard
- Navigate to Integrations > Developer Tools or Settings > API
- Generate a new API Key or copy your existing key
- Give it a descriptive name (e.g., “Alloy Automation Integration”)
- Store the key securely immediately after generation
- Configure in Alloy Automation:
- Header name:
X-Authorization - Header value: Your Loop Returns API Key
- Header name:
API Documentation
- Loop Returns API Base URL: https://api.loopreturns.com
- API Documentation: https://docs.loopreturns.com/api-reference/authentication
- Developer Tools: Available in your Loop Returns admin under Integrations
Use Cases
1) Automated returns processing
Automatically process, flag, or close returns based on business rules, inventory availability, or fraud detection signals, reducing manual intervention in the returns workflow.2) Returns data synchronization
Sync return requests, tracking information, and refund data from Loop Returns to your ERP, data warehouse, or customer service platform for unified visibility across systems.3) Warehouse management integration
Send Advanced Shipping Notices (ASN) to your warehouse management system when returns are in transit, enabling better inventory planning and receiving workflows.4) Customer fraud prevention
Automatically manage allowlists and blocklists based on return patterns, customer behavior, or external fraud signals to protect your business from returns abuse.5) Returns analytics and reporting
Pull Loop Returns data into business intelligence tools to analyze return rates, reasons, costs, and trends, informing product improvements and policy decisions.API Gotchas
- Return state transitions: Returns can only be processed when they’re in specific states. For example, flagged, cancelled, or expired returns cannot be processed. Always check the return’s current state before attempting state-changing operations, and handle
400errors gracefully when transitions aren’t allowed. - Date range limitations: The returns list endpoint has a maximum date range of 120 days. If you need historical data beyond this range, you’ll need to make multiple API calls with different date ranges. Plan your data synchronization strategy accordingly.
- Return processing is final: When you process a return via the API, Loop will archive it and fulfill any remaining outcomes (exchanges, gift cards, refunds). This action cannot be undone. Always implement confirmation steps in your workflows before processing returns programmatically.
- Line item removal restrictions: Currently, only returns with refund outcomes allow line items to be removed. If you attempt to remove line items from an exchange-based return, the API will return a
400error. Check the return’s outcome type before attempting line item modifications. - Pagination parameters: Different endpoints use different pagination parameter names (
page,per_page,limit). The returns list endpoint usespageandlimit, while other endpoints may usepageandper_page. Check the specific endpoint documentation for correct parameter names. - Deep links and Shopify store IDs: When creating deep links, you must provide the Shopify
store_id, not your Loop Returns account ID. This ID can be found in your Loop Returns admin or Shopify admin settings. - Webhooks vs polling: Loop Returns supports webhooks for real-time notifications of return events (created, updated, closed, label created, etc.). Consider implementing webhooks instead of frequent polling for more efficient and responsive integrations.
For questions or troubleshooting, contact support@runalloy.com.