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 receivable-invoices API

The receivable-invoices API from Loop — 3 operation(s) for receivable-invoices.

Loop receivable-invoices API is one of 14 APIs that Loop publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include receivable-invoices. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 4 operations across 3 paths, and defines 49 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://onboarding.api.loop.com.

4 operations 3 paths 49 schemas 1 DELETE2 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.loop.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Loop receivable-invoices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey) (bearer). By default, every request must be authenticated.

  • bearer — Bearer HTTP authentication. Allowed headers: Authorization: Bearer

Paths & Operations 4

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

receivable-invoices 4
GET
/v1/receivable-invoices
List receivable invoices
ReceivableInvoices_list 10 params → 200
GET
/v1/receivable-invoices/{qid}
Retrieve a receivable invoice
ReceivableInvoices_get 2 params → 200400
DELETE
/v1/receivable-invoices/{qid}
Delete a draft receivable invoice
ReceivableInvoices_delete 1 param → 204
PUT
/v1/receivable-invoices/{qid}/void
Void an open receivable invoice
ReceivableInvoices_void 2 params → 200

Schemas 49

The contract defines 49 schemas that model the data the API accepts and returns. The most detailed are ReceivableInvoice (22 properties), ShipmentJobLtlInfo (19 properties), ShipmentJobFtlInfo (16 properties), ShipmentJobOceanInfo (14 properties). Each schema is shown below with its type and property counts.

CurrencyCode
string
ShipmentJobAirAddress
object
4 properties 4 required
ShipmentJobUnknownInfo
object
2 properties 1 required
NmfcClass
string
ShipmentJobFtlStopArticle
object
7 properties 7 required
Volume
object
2 properties 2 required
ShipmentJobFtlStopReferenceNumber
object
2 properties 2 required
ShipmentJobLtlInfo
object
19 properties 14 required
ReceivableInvoice
object
22 properties 15 required
Address
object
7 properties 5 required
OrganizationExpanded
object
3 properties 2 required
PackageCountInput
object
2 properties 2 required
ShipmentJobAirDate
object
4 properties 4 required
ShipmentJobArtifactExpanded
object
4 properties 4 required
BusinessException
object
5 properties 4 required
ShipmentJobGenericV1Info
object
1 property 1 required
ShipmentJobOceanDate
object
4 properties 4 required
ShipmentJobOceanContainer
object
3 properties 3 required
ShipmentJobAirInfo
object
13 properties 13 required
FreightChargeTerms
string
ShipmentJobTonuInfo
object
2 properties 1 required
ShipmentJobOceanAddress
object
4 properties 4 required
ShipmentJobOceanRouteLocation
object
4 properties 4 required
Money
object
2 properties 2 required
ShipmentJobOceanInfo
object
14 properties 14 required
ShipmentJobSeaAirAddress
object
4 properties 4 required
User
object
3 properties 3 required
ShipmentJobFtlInfo
object
16 properties 11 required
Weight
object
2 properties 2 required
Dimensions
object
4 properties 4 required
ShipmentJobAirRouteAirportLocation
object
3 properties 3 required
ShipmentJobAirRouteUnlocodeLocation
object
3 properties 3 required
RawShipmentReferenceNumbers
object
13 properties
ShipmentJobAddress
object
4 properties 3 required
ShipmentWithoutShipmentJobsExpanded
object
2 properties 1 required
ShipmentExpanded
object
3 properties 1 required
ShipmentJobSeaAirContainer
object
3 properties 3 required
ShipmentJobLtlInfoArticle
object
7 properties 7 required
ReceivableInvoiceLineItem
object
5 properties 4 required
ShipmentJobFtlStop
object
10 properties 8 required
ReceivableInvoiceVoidReasonType
string
ShipmentReferenceNumber
object
3 properties 2 required
ShipmentJobSeaAirInfo
object
12 properties 12 required
PackageCount
object
2 properties 2 required
ShipmentJobExpanded
object
13 properties 9 required
ArtifactExpanded
object
2 properties 2 required
ShipmentJobArticlesSummary
object
3 properties 3 required
HandlingUnit
object
2 properties 2 required
ShipmentJobIntermodalInfo
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

loop-receivable-invoices-api-openapi.yml Raw ↑

Other APIs Loop publishes across the network.

Loop artifacts API
Loop artifacts-schema-validated API
Loop business-exceptions API
Loop factoring-relationships API
Loop invoicing-relationships API
Loop onboarding.api.loop.com API
Loop organizations API
Loop payable-allocations API
Loop payable-invoice-reviews API
Loop payable-invoices API
Loop payments API
Loop ping API
Where this information came from

This is an independent, third-party profile of Loop receivable-invoices 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.