Quickstart

01Read the public catalog

No key is needed to see which sites Poacher can watch.

curl https://app.poacher.io/api/v1/sources

GET /api/v1/capabilities says what the API can do today and which features are switched off. Read it before planning paid work.

02Create a key

1. Sign in and open Account → Developer access.
2. Name the key, tick only the permissions it needs and choose 7, 30 or 90 days.
3. Copy the key. It is shown once.

Keys look like poacher_v1_…. Keep them in a secret store or environment variable, never in a URL, a repository or browser code. Permissions.

03Read your alerts

export POACHER_API_KEY=poacher_v1_…
curl https://app.poacher.io/api/v1/alerts -H "Authorization: Bearer $POACHER_API_KEY"

{"data":[{"id":42,"name":"Gatsby first editions","status":"active","edit_revision":"…","urgency":"normal","filters":{},"result_review":true,"billing_hold":false,"volume_hold":false,"created_at":"2026-11-01T10:00:00.000Z"}],"next_before":null}

Then read that alert’s results:

curl https://app.poacher.io/api/v1/alerts/42/results -H "Authorization: Bearer $POACHER_API_KEY"

04Or connect an assistant

Add https://app.poacher.io/mcp to your MCP client. No key to paste: the client opens Poacher for sign-in when it first needs your account. Client setup.

05Next

• Workflows: channels, edits, paid previews and checks, step by step.
• REST reference and MCP tools.
• Errors and limits.