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

Terminal Cart API

The Cart API from Terminal — 5 operation(s) for cart.

Terminal Cart API is one of 11 APIs that Terminal publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cart. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 5 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.terminal.shop, https://api.dev.terminal.shop.

6 operations 5 paths 9 schemas 1 DELETE1 GET1 POST3 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.terminal.shop
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — Personal access token (trmlive in production, trmtest in the dev sandbox) or OAuth 2.0 access token, passed as Authorization: Bearer .

Paths & Operations 6

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

Cart 6
GET
/cart
Get cart
getCart → 200
DELETE
/cart
Clear cart
clearCart → 200
PUT
/cart/item
Add or update cart item
setCartItem body → 200
PUT
/cart/address
Set cart shipping address
setCartAddress body → 200
PUT
/cart/card
Set cart payment card
setCartCard body → 200
POST
/cart/convert
Convert cart to order
convertCart → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are OrderShipping (8 properties), Order (7 properties), OrderTracking (6 properties), Cart (6 properties). Each schema is shown below with its type and property counts.

OrderTracking
object
6 properties
Order
object
7 properties 6 required
OrderAmount
object
2 properties 2 required
OrderShipping
object
8 properties 5 required
Cart
object
6 properties 3 required
CartAmount
object
3 properties 1 required
CartShipping
object
2 properties
OrderItem
object
5 properties 3 required
CartItem
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

terminal-shop-cart-api-openapi.yml Raw ↑

Other APIs Terminal publishes across the network.

Terminal Address API
Terminal App API
Terminal Card API
Terminal Email API
Terminal Order API
Terminal Product API
Terminal Profile API
Terminal Subscription API
Terminal Token API
Terminal View API
Where this information came from

This is an independent, third-party profile of Terminal Cart 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.