Skip to content
BuildBase
HTTP API menu

Start checkout for a cart of items across sellers

Creates one order per seller, sharing a cartId, for the signed-in user, holds stock and bookings, and returns a Stripe Checkout URL (a storefront checks out...

Warning

Not fully described yet. The API description has no described successful answer for this operation yet. The method, path, sign-in, rate limits and request fields on this page are read from the server's code and are accurate; what a successful call returns is not written down here yet. Until it is, search engines and the agent index leave this page out.

POST/api/v1/public/cart/checkout

Sign-in
A signed-in user's session: send the session id in the x-session-id header.
Rate limit
Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted).

Creates one order per seller, sharing a cartId, for the signed-in user, holds stock and bookings, and returns a Stripe Checkout URL (a storefront checks out in steps). Refused when the cart is empty or has more lines than allowed. The buyer is always the session's user.

Request

Send the body as application/json.

Body

FieldTypeRequiredConstraintsDescription
linesarray of objectYesat least 1 items, at most 10 items-
lines[].itemIdstringYesmatches ^[a-f0-9]{24}$-
lines[].variantIdstringNoat most 64 characters-
lines[].priceIdstringNoat most 64 characters-
lines[].optionValuesobjectNo--
lines[].quantityintegerNoat least 1, at most 100-
lines[].amountintegerNoat least 0, at most 99999999-
lines[].slotStartstringNo1 to 40 characters-
lines[].slotStartsobjectNo--
successUrlstringYes1 to 2000 characters-
cancelUrlstringYes1 to 2000 characters-
couponCodestringNo1 to 40 characters-
referralstringNo1 to 1024 characters-
shippingQuotestringNo1 to 8192 characters-
buyerCountrystringNo2 to 2 characters, matches ^[A-Za-z]{2}$-

Example request

Replace each YOUR_... value with your own, and set the credential in the environment variable the sample reads.

curl -X POST "https://api.console.buildbase.app/api/v1/public/cart/checkout" \
  -H "x-session-id: $BUILDBASE_SESSION_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "lines": [
    {
      "itemId": "YOUR_ITEM_ID"
    }
  ],
  "successUrl": "https://example.com",
  "cancelUrl": "https://example.com"
}'
const response = await fetch(
  'https://api.console.buildbase.app/api/v1/public/cart/checkout',
  {
    method: 'POST',
    headers: {
      'x-session-id': process.env.BUILDBASE_SESSION_ID ?? '',
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      lines: [
        {
          itemId: 'YOUR_ITEM_ID',
        },
      ],
      successUrl: 'https://example.com',
      cancelUrl: 'https://example.com',
    }),
  }
);
if (!response.ok) {
  throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.text();
import os

import requests

response = requests.post(
    "https://api.console.buildbase.app/api/v1/public/cart/checkout",
    headers={
        "x-session-id": os.environ["BUILDBASE_SESSION_ID"],
    },
    json={
        "lines": [
            {
                "itemId": "YOUR_ITEM_ID",
            },
        ],
        "successUrl": "https://example.com",
        "cancelUrl": "https://example.com",
    },
    timeout=30,
)
response.raise_for_status()
data = response.text

Responses

A successful answer is not described yet. The server answers with the status and body its handler sends.

Any other status

The handler's own answer. Not described yet: response bodies come from captured responses (server/openapi/captured) and overlays (server/openapi/overlays).

Errors

Each refusal, what it means, and what to do. The request changed nothing.

400 Bad Request

What it means: The request failed a validate() schema, or an id in the path is not a valid id. path names the field.

What to do: Fix the field the body names in path (or read message) and send the request again. Nothing was changed.

Example
{
  "error": true,
  "success": false,
  "path": "string",
  "message": "string"
}

401 Unauthorized

What it means: The credential is missing, expired or not accepted here, or the caller's role has no grant for x-permission (refused with 401 too). The body is the plain text Unauthorized, or a JSON body with a code where the gate says why.

What to do: Send the credential this operation asks for (see Sign-in above), or sign in again if it expired. A valid credential is also refused when the role has no grant for the permission above.

Example
Unauthorized

429 Too Many Requests

What it means: A rate limit in x-rateLimit was reached. retryAfter and the Retry-After header say how many seconds until the window resets.

What to do: Wait the number of seconds in the Retry-After header (also retryAfter in the body), then retry. Slow down repeated calls.

Example
{
  "success": false,
  "message": "string",
  "reason": "rate_limited",
  "retryAfter": 1
}

Events

A successful call can send these webhook events to the endpoints that subscribe to them: