This walkthrough takes you from an empty workspace to a customer, contact, and onboarding visible in the Pivotal UI. Total wall time: about three minutes.
Open Admin > API Keys inside your workspace and click Create key. Pick a name (local-dev, prod-server, ci) and the environment:
pivotal_… — mutates production state, fires webhooks, counts against the live quota.pivotal_test_… — mutates production state too, but skips outbound integration calls (Slack, Resend, Stripe). See Test mode.Copy the key once and stash it in your secret manager. Pivotal stores only a hash; the cleartext is shown exactly once at create time.
Treat keys like passwords. They grant full read/write across the workspace. Rotate by creating a new key, swapping it in your services, then revoking the old one — there is no “downtime” between create and revoke.
Hit /me. It echoes the key’s identity and the workspace it belongs to. No side effects, costs one request from your rate limit.
You should see something like:
If you get a 401, double-check the header format — it’s Authorization: Bearer <key>, not Bearer: <key> or Authorization: <key>.
slug is the URL-safe handle. Pivotal also returns a display_id (the small integer that appears in URLs like /customers/245).
Note the path — contacts always live under a customer. The 245 is the customer’s display_id; the customer’s cuid works just as well.
Refresh /customers/aurora in the Pivotal UI. You should see Mira on the customer card and the loyalty launch onboarding in the sidebar. The activity feed will show an entry for each API call — the calling key’s name is the actor.