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

Commerce Layer attachments API

resource type

Commerce Layer attachments API is one of 148 APIs that Commerce Layer publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Attachments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, a JSON-LD context, and 2 JSON Schemas.

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

Requests are made against 3 base URLs: https://{your_organization_slug}.commercelayer.io/api, https://core.commercelayer.io/users/sign_in, https://docs.commercelayer.io/api.

5 operations 2 paths 63 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
7.10.1
Base URL
https://{your-organization-slug}.commercelayer.io/api
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Commerce Layer attachments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 5

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

attachments 5

resource type

GET
/attachments
List all attachments
GET/attachments → 200
POST
/attachments
Create an attachment
POST/attachments body → 201
GET
/attachments/{attachmentId}
Retrieve an attachment
GET/attachments/attachmentId 1 param → 200
PATCH
/attachments/{attachmentId}
Update an attachment
PATCH/attachments/attachmentId 1 param body → 200
DELETE
/attachments/{attachmentId}
Delete an attachment
DELETE/attachments/attachmentId 1 param → 204

Schemas 63

The contract defines 63 schemas that model the data the API accepts and returns. The most detailed are klarnaPayment (1 property), stripeTaxAccount (1 property), customerGroup (1 property), geocoder (1 property). Each schema is shown below with its type and property counts.

klarnaPayment
object
1 property
paymentOption
object
1 property
giftCardRecipient
object
1 property
taxjarAccount
object
1 property
giftCard
object
1 property
satispayPayment
object
1 property
parcel
object
1 property
wireTransfer
object
1 property
order
object
1 property
package
object
1 property
skuList
object
1 property
paymentMethod
object
1 property
refund
object
1 property
adyenPayment
object
1 property
return
object
1 property
shipment
object
1 property
shippingCategory
object
1 property
avalaraAccount
object
1 property
taxCategory
object
1 property
externalPayment
object
1 property
checkoutComPayment
object
1 property
customer
object
1 property
inventoryModel
object
1 property
sku
object
1 property
promotion
object
1 property
subscriptionModel
object
1 property
carrierAccount
object
1 property
attachmentUpdate
object
1 property 1 required
shippingMethod
object
1 property
merchant
object
1 property
stockTransfer
object
1 property
attachment
object
1 property
attachmentCreate
object
1 property 1 required
capture
object
1 property
stockItem
object
1 property
shippingMethodTier
object
1 property
priceList
object
1 property
axervePayment
object
1 property
market
object
1 property
stockLocation
object
1 property
price
object
1 property
couponRecipient
object
1 property
discountEngine
object
1 property
shippingZone
object
1 property
externalTaxCalculator
object
1 property
transaction
object
1 property
manualTaxCalculator
object
1 property
void
object
1 property
skuOption
object
1 property
braintreePayment
object
1 property
deliveryLeadTime
object
1 property
attachmentResponse
object
1 property
priceTier
object
1 property
bundle
object
1 property
taxCalculator
object
1 property
stripePayment
object
1 property
paypalPayment
object
1 property
attachmentResponseList
object
1 property
vertexAccount
object
1 property
geocoder
object
1 property
customerGroup
object
1 property
stripeTaxAccount
object
1 property
authorization
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

commerce-layer-attachments-api-openapi.yml Raw ↑

Other APIs Commerce Layer publishes across the network.

Commerce Layer addresses API
Commerce Layer adjustments API
Commerce Layer adyen_gateways API
Commerce Layer adyen_payments API
Commerce Layer analysis API
Commerce Layer api_credentials API
Commerce Layer application API
Commerce Layer application_memberships API
Commerce Layer authorizations API
Commerce Layer avalara_accounts API
Commerce Layer axerve_gateways API
Commerce Layer axerve_payments API
Where this information came from

This is an independent, third-party profile of Commerce Layer attachments 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.