1
Make a key
Open Workspace settings → API keys and choose Create key. Give it a name that says where it will live, so you know which one to revoke later. Every read scope is ticked for you; leave the two write scopes off for now.The whole key is shown once, in its own box. Copy it then: after you leave the screen only its short prefix is shown. Only a workspace owner or admin can make keys.
2
Keep it out of your code
Put the key in an environment variable rather than in a file you commit. In a terminal,
read -rs CITINO_API_KEY && export CITINO_API_KEY asks for the key without showing it, so it stays out of your shell history too. Every sample on this site reads the key from CITINO_API_KEY.3
List your projects
id of the project you want. The samples below read it from PROJECT_ID.4
Read your headline figures
The same four numbers as the top of Overview, for the last 30 days by default.Each figure carries its
band (the ± range), n (how many answers it rests on) and within_noise. Keep them with the value wherever it goes. See Metric objects.5
Pull yesterday's report rows
One row per brand per engine for yesterday. Days are your project’s market days, so yesterday is yesterday in the market’s time zone (A report can take more than one page. Follow
America/New_York for a US market): the Python and JavaScript samples read it from MARKET_TZ. For curl, FROM and TO are dates as YYYY-MM-DD; set both to that day.next_cursor until has_more is false; Pulling data nightly has the whole loop.Related
Authentication
Scopes, project limits, expiry and revoking a key.
Reports
Dimensions, filters, budgets and paging.
Errors
Every error code and what to do about it.
API reference
Every route and its response.