Authentication

Every REST call needs an API key in the Authorization header.

shell

curl https://plonki.com.au/v1/account \
  -H "Authorization: Bearer plk_live_..."

Keys

Prefix	Mode	Behaviour
`plk_live_`	Live	Real registrations, paid from your balance or a checkout link.
`plk_test_`	Test	Simulated registry, nothing charged. See Test mode.

Create and revoke keys under API keys in the dashboard. A key is shown once.
Plonki stores only a hash of each key. If you lose one, revoke it and make a new one.
Keys work from servers, serverless functions and AI assistants. There's no IP allowlist.
Keep live keys on the server side. Anyone with a live key can spend your balance.
The same keys work as Bearer tokens on the MCP server.

Check a key

shell

curl https://plonki.com.au/v1/account \
  -H "Authorization: Bearer $PLONKI_KEY"

json

{
  "account_id": "acc_8m2k4q9w1x7n3b5v6c0z",
  "email": "you@example.com",
  "tier": "retail",
  "mode": "live",
  "balance": 25000,
  "currency": "AUD",
  "default_contact_id": "con_4f7h2k9m1q3w8e5r6t0y"
}

balance is null for test keys. A missing or wrong key returns 401 unauthorized.