How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Loop Returns Destinations API

The Destinations API from Loop Returns — 2 operation(s) for destinations.

Loop Returns Destinations API is one of 7 APIs that Loop Returns publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Destinations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and rate-limit docs.

This API exposes 5 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.loopreturns.com/api/v1.

5 operations 2 paths 7 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.loopreturns.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Loop Returns Destinations API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Authorization (api_key).

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Destinations 5
GET
/destinations
Get All Destinations
getAllDestinations → 200401
POST
/destinations
Create Destination
createDestination body → 200401422
GET
/destinations/{id}
Get Destination Details
getDestinationDetails 1 param → 200401404
PUT
/destinations/{id}
Update Destination
updateDestination 1 param → 200404
DELETE
/destinations/{id}
Delete Destination
deleteDestination 1 param → 200404500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Address (7 properties), Destination (6 properties), CreateDestinationRequest (4 properties), DestinationLimitExceeded (2 properties). Each schema is shown below with its type and property counts.

Address
object
The destination's address.
7 properties
CreateDestinationRequest
object
4 properties 3 required
Destination
object
A physical location such as a warehouse or donation center to which returns are shipped.
6 properties
UnauthorizedResponse
object
1 property
NotFoundResponse
object
2 properties
UnprocessableResponse
object
1 property
DestinationLimitExceeded
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

loop-returns-destinations-api-openapi.yml Raw ↑

Other APIs Loop Returns publishes across the network.

Loop Returns Cart API
Loop Returns Fraud Reports API
Loop Returns Label Requests API
Loop Returns Programmatic Webhooks API
Loop Returns Return Actions API
Loop Returns Return Data API
Where this information came from

This is an independent, third-party profile of Loop Returns Destinations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.