How engineering teams authenticate and connect automation to CookieShift.
CookieShift is designed for operators in the dashboard. Engineering teams add API access when they need automation.
Get credentials
- Sign in to the dashboard with an account that can edit the property (owner or admin to rotate keys).
- Open Implementation for your property and use Property API key to view the masked key or rotate it.
- After rotation, copy the new key immediately — the dashboard shows the full value only once.
- Store the token in your secrets manager—never commit it to git.
For personal sign-in events (2FA, sessions), use Account → Security. Workspace owners and admins can review team and billing actions under Settings → Security & audit.
First request
Test connectivity:
curl -s -H "Authorization: Bearer YOUR_TOKEN" \
"https://YOUR_API_HOST/api/auth/me"A successful response confirms the token and base URL.
Typical automations
| Goal | Approach |
|---|---|
| Scan after deploy | POST scan start for siteId, poll status, fetch results |
| Pull compliance PDF | Request export endpoint for latest reportId |
| Sync config | GET config before/after CI-driven updates |
See API Reference for endpoint families.
Base URL
Use the same API host shown in Modules (data-api on your embed snippet). Staging and production hosts differ—point CI at the environment you intend to change.
Need help?
Describe your integration in a support ticket (property domain, environment, and read vs write needs). Most product questions are answered faster via Getting Started and feature guides than via raw API exploration.