Skip to main content
The visitor-data API uses a data key (mk_live_...) in the X-API-Key header. GET /v1/health is public and needs no key. Partner provisioning uses a separate management key (pk_live_...) on /v1/partner/domains, /v1/partner/domain-groups, and /v1/partner/api-keys. Get that key from Partner Dashboard → Domain Management API Key. It belongs to your Wildcard partner account; store it in your own application’s backend secrets. It cannot read /v1/people. See Partners for the complete site-builder workflow.

Getting an API key

  1. Log in to your Wildcard dashboard
  2. Open Integrations from the sidebar
  3. Find the Developer API card and click Manage Keys
  4. Click Create API Key
  5. Copy the key immediately — it’s only shown once

Data key format

Data keys follow the format mk_live_ followed by 40 random hex characters:

Security best practices

  • Never expose keys in client-side code — use your API key from a backend server only
  • Store keys securely — use environment variables or a secrets manager
  • Rotate keys regularly — you can have up to 5 active keys at a time
  • Revoke compromised keys immediately — revocation is instant

Data key limits

  • Maximum 5 active keys per account
  • Keys can be revoked instantly from the dashboard
  • All keys share the same rate limit pool (1,000 requests/hour)

Domain-scoped keys

Partner accounts can issue keys restricted to a single tracked client domain, so one client’s key cannot read another client’s visitors. These keys sit outside the 5-key limit and each carries its own rate limit pool rather than sharing yours. See Partners for how to issue them.

Error responses