Authentication

Every Walker Street Data API request must be authenticated with an API key, passed in the x-api-key header.

curl -X GET "https://api.walkerstdata.com.au/v1/jobs" \
  -H "x-api-key: YOUR_API_KEY"

A request with a missing, empty, invalid, or expired key is rejected with 401 Unauthorized.

Getting a key

We don't offer self-service keys. Contact us to request an API key and discuss your use case.

Each key is scoped to the operations your integration needs (for example, transactions:enrich, transactions:extract, transactions:aggregate, customer:completeness, or customer:riskscore). If a request returns a 403 Forbidden, your key is valid but missing the scope required for that endpoint - get in touch and we'll adjust it. (A 401, by contrast, means the key itself wasn't accepted.)

Environments

Environment	Base URL
Sandbox	https://sandbox.walkerstdata.com.au
Production	https://api.walkerstdata.com.au

Use your sandbox key against the sandbox base URL while you build and test, then switch to your production key and base URL when you go live. Code samples throughout these docs use the production host - swap in the sandbox host above while testing.

Keep your key secret

Treat your API key like a password. Send requests from your server, never from browser or mobile client code, and never commit keys to source control.

Requests are also subject to rate limits.