PressScape Public API
Programmatic access to your PressScape marketplace activity — orders, websites, balances, notifications. Bearer-token authenticated, JSON in & out, scoped to the issuing buyer's account.
Getting your token
Open Settings → API tokens and click Generate token. Tokens are shown once — copy yours immediately into your password manager. Max 5 active tokens per account.
The token format is ps_… followed by 32+ characters.
Authentication
Send the token as a Bearer credential in the Authorization header on every request:
bashcurl https://api.pressscape.com/v1/orders \ -H "Authorization: Bearer ps_YOUR_TOKEN_HERE"
Rate limits
429s return a Retry-After header in seconds. Implement exponential backoff — the limit is a sliding window, so quick retries will continue to fail.
Endpoints
| Method | Path | Purpose |
|---|---|---|
| GET | /v1/orders | List your orders. Supports ?status=, ?page=, ?per_page= |
| GET | /v1/orders/[id] | Single order detail + timeline |
| POST | /v1/orders | Create a new order against a marketplace website |
| GET | /v1/websites | Browse the marketplace (filter by DR, traffic, category, language) |
| GET | /v1/websites/[id] | Single website detail + price + contributors |
| GET | /v1/wallet | Current balance, reserved, bonus |
| GET | /v1/notifications | Recent notifications + unread count |
Quickstart — Node + fetch
jsconst token = process.env.PRESSSCAPE_TOKEN; const res = await fetch('https://api.pressscape.com/v1/orders?status=pending', { headers: { Authorization: `Bearer ${token}` }, }); if (!res.ok) { throw new Error(`API ${res.status}: ${await res.text()}`); } const { orders, pagination } = await res.json(); console.log(`${orders.length} of ${pagination.total} pending`);
Error format
All non-2xx responses use this shape:
json{ "error": "Invalid input: expected string, received undefined", "code": "validation_error", "details": { "field": "domain" } }
code values: unauthorized, forbidden, not_found, validation_error, rate_limited, internal_error.
Security notes
- Tokens carry the same permissions as your account — treat them like a password.
- Revoke compromised tokens immediately at Settings → API tokens.
- Never embed tokens in client-side code or commit them to git.
- Server-side use only — every request from a browser will be CORS-rejected.