SLAB
In this section

API REFERENCE

The full endpoint reference is served by the API itself — always in sync with the running server.

Every endpoint, every field, every error is documented in the API's OpenAPI spec, which is generated from the server's own routes and schemas. Explanations of what each endpoint is for, what the numbers mean, and where the traps are live in there too. We don't reprint it here, for the same reason we don't reprint the CLI's commands: a copy can go stale, and the generated one can't.

📖

Browse the API

Swagger UI — read the reference and send real requests from the browser. Start here.

📕

Read it long-form

ReDoc — the same spec in a three-column reading layout, better for a cover-to-cover pass.

⚙️

Download the spec

Raw openapi.json — feed it to a client generator, Postman, or your own tooling.

💡In Swagger UI, hit Authorize and paste an API key once — every "Try it out" below it then runs against the real API as you.

BEFORE YOU OPEN IT

Three things explain most of the shape of the API. The spec covers all of them in depth; this is enough to make the endpoint list read sensibly.

one headerEvery data request carries x-api-key. Mint a key under Account. The accountgroup in the spec is the portal's own surface and needs a browser session instead — with one exception, GET /account, which tells you which collector your key acts for.
search is POSTSearches take a JSON body, not a query string — the filter grammar is nested and list-valued, which query strings handle badly. Within a list values are OR'd; across fields they're AND'd.
UUIDs everywhereEvery identifier on the wire is a UUID string, and paths say so ({card_uuid}, never {card_id}). Treat them as opaque.

CHECK YOUR KEY WORKS

Two calls: one that needs nothing, and one that proves your key is live and tells you which collector it acts for.

first contact
curl -s https://api.slab.dev-jeb.com/health

curl -s https://api.slab.dev-jeb.com/account -H "x-api-key: $SLAB_API_KEY"

WHAT'S IN THERE

The reference is grouped by tag, and each group opens with what it's for. Roughly:

cards / sets / sealedThe catalog and its prices — search, a card's parallels, what it's worth, the sales behind that number, and what a sealed box costs.
collectionYour cards and your money — copies, breaks, lots, costs, plus the dashboard and portfolio history built from them. This is the write surface.
custom-setsChase sets: the set you decided to complete, tracked against what you own.
community / statsPublic, aggregate, no key required — catalog totals and anonymized leaderboards.
meta/vocab and /glossary — every valid value, and plain-language text for every metric. Read these instead of hardcoding lists or writing your own captions.

CONCEPTS FIRST, IF YOU'RE NEW

The spec tells you what each endpoint does; it assumes you know what a parallel is, or how cost basis is put together. If those are new, the Concepts pages cover the model, and First Run walks from nothing to an authenticated call. Prefer not to write HTTP at all? The CLI wraps the same endpoints.

📋Building a typed Python client? slab-schemas ships the exact request and response models the API validates against — pydantic only, no server dependencies.