Two minutes, and worth doing before anything else: almost every integration problem later turns out to be one of the two things this proves.
1. Mint a key
Create key on the dashboard. You see the whole key once. Put it somewhere your code reads from the environment rather than from a file in the repository.
2. Ask who you are
curl "https://makehybrid.com/premium/api/v1/users/me?account_id=$ACCOUNT_ID" \ -H "X-API-KEY: $MAKEHYBRID_KEY"
An answer means the key is valid, the plan is active and the account id is one your organisation connected. Three things, one call.
3. Learn the error shape now
{"type":"errors/payment_required","status":402,"detail":"..."}
- 401 — the key is missing, wrong or revoked.
- 402 — the plan is not paid for, or the trial is over.
- 404 — not there, or not yours. Deliberately the same answer.
- 429 — too many requests, or LinkedIn throttling the account.
- 503 — the hop in front of LinkedIn did not answer; the body carries the bare status it saw.
Write one handler against that shape and every route in the catalog is covered. The detail field is written to be shown to a person, so showing it is usually the right thing to do.