Zijra CLI
Download the command-line client and use your website-scoped permissions.
Download the client
Zijra provides a downloadable command-line helper for Node.js 22 or later, with no extra package dependencies. It is not a published package. Download the file, inspect it, then run it with Node. It uses the same versioned website API as the dashboard’s developer tools. Running commands against a saved website requires paid API access; downloading the helper does not grant that access.
Download Zijra CLIChoose your website and permissions
Create an expiring, website-scoped token in Developer settings. Store ZIJRA_API_TOKEN in your process environment; never put the secret in a command, URL or shared configuration file. Read-only permissions remain read-only.
Choose report filters
Analytics, breakdowns, goal-report and funnel-report accept --source, --filters, --goal-id and --visit-count. When specifying dates, supply both --start and --end; leaving both out uses the website’s local default range of the last 30 days. Filters use the same four operators and literal matching as the dashboard.
--dimension selects one of the 14 breakdown tables. --currency takes an uppercase currency code and --payment-mode selects live or test receipts. Payments also accept dates, currency and payment mode; provider-goal-report accepts dates and payment mode. Paged lists use --limit from 1 to 200 and the API’s opaque --cursor. Saved segment names and custom time grouping are not exposed by this API.
Measure a saved funnel
Use goal-report for goal totals, trends and property breakdowns. These two resources require reports:read and accept a limit from 1 to 20 (default 10), without a cursor. Append the definition UUID for one report. Goals and funnels still manage saved definitions.
Available resources
Analytics, breakdowns, visitors, identities, server goals, payments, websites, goals, provider goals, measured goal and funnel reports, funnels, notes, alerts, team and tokens each enforce the caller’s permission and website access. Paged resource lists use signed cursor pagination; measured report lists use the separate limits above.
Review writes deliberately
Create and update commands read a reviewed JSON object through --data-file. All writes require --confirm; update and delete need an exact record UUID. The client does not follow redirects or expose your token in output.