Partner API · early access

Build on Slab Dynasty

A REST API for listing, pricing and fulfilling graded trading cards. If you have built a Shopify integration, you already know the shape of this one — the base URL is https://api.slabdynasty.com.

Request accessRead the docs

Verify a key

curl https://api.slabdynasty.com/2026-07/ping \
  -H "X-SlabDynasty-Access-Token: $SLAB_API_KEY"
Shopify-shaped on purpose
Resource envelopes, cursor pagination and X-…-Api-Call-Limit headers match Shopify's Admin REST API, so an existing integration ports with a host swap and a header rename rather than a rewrite.
Card-native
Graded cards are the first-class object. List by PSA, BGS, SGC or CGC certificate number and the grade, player, set and scans hydrate automatically — you do not maintain a catalogue.
Keys you can actually operate
Per-environment tokens, scoped permissions, rotation with an overlap window, revocation, and idempotency keys on every write.

How access works

Credentials belong to a seller account, so the path runs through seller onboarding rather than around it.

  1. 1.Create a Slab Dynasty account

    Standard signup on the main site. Takes a minute and needs nothing special.

    Sign up

  2. 2.Complete seller setup

    Connect a payout method and finish your selling profile. API credentials are scoped to a seller account — there is no standalone developer account, because every endpoint acts on a specific seller's listings, inventory and orders.

    Seller setup

  3. 3.Issue keys from the Developers tab

    Once your seller account is approved, test and live read keys are self-serve. Live WRITE access is reviewed by a human first — a write key can reprice or end an entire catalogue and buy shipping labels with real money.

    Developers tab

  4. 4.Build against the reference

    Shopify Admin REST conventions throughout: same envelopes, same cursor pagination, same leaky-bucket rate-limit headers.

    Read the docs
Where the API is today

The API is in early access and we are onboarding integrators in batches. Authentication, versioning, rate limiting and the credential lifecycle are live. Catalogue and inventory reads are rolling out now; write endpoints follow, and order writes after those.

Tell us what you are building and we will get you into the right batch — and tell you honestly if the endpoints you need are not ready.

Request access