API overview

Your first call

Create a key at Settings › API keys, then:

curl "https://api.slashtrace.com/v1/status" \
  -H "Authorization: Bearer $API_KEY"

A 200 means the key works and tells you the plan, how many boards you track and how much of the rate limit is left. Anything else, and Errors says what to do about it.

Base URL

https://api.slashtrace.com/v1

Everything lives under /v1. The app’s own routes under /api are not the API — they are the frontend’s private contract, they change shape whenever the interface does, and they do not accept keys.

The model

Two nouns carry the whole product. Everything any endpoint returns is one of them, or a list of them.

• Board — one company’s careers page. Boards are global: ten accounts tracking Stripe share one board and one scrape. What you own is a subscription to it, which is why deleting one leaves the board and its history alone.
• Role — one posting on a board, with the moment we first saw it. That last field is the one that matters: “new” means new to us, not a date the employer published.

True of every endpoint

• A key acts as you. It reaches your boards and nothing else — no billing, no other account, no admin. See Authentication.
• Pro and Ultra only. On Free every request is refused with plan_required rather than returning an empty list, so a client can tell “not allowed” from “nothing to show”.
• Ten requests a minute, per account. All your keys share one budget. See Rate limits.
• Reads never trigger a fetch. You get what the last scheduled read found. Nothing makes you wait on a careers page.
• Plan limits are counted server-side. A board added through the API counts exactly as it does in the app, and one past the limit is kept and marked locked rather than refused.

Endpoints