Stats, runs and the log
Numbers per project and script, recent runs, the workspace log and its members.
Reading only: these routes need no scope. A key limited to some projects sees only those projects; the two routes that concern the whole workspace (/audit and /members) refuse it with 403 INSUFFICIENT_SCOPE.
Numbers for a project
GET /v3/projects/:id/stats
days (1 to 90, default 30) sets the window. The answer has users (total, unused, active, reset, banned), executions (ok and failed in the window and a series with one entry per day, quiet days as zeros), top_scripts, top_executors and top_countries. GET /v3/projects/:id/scripts/:script_id/stats gives the same runs for one script. The numbers come from the daily rollup, in UTC days.
Recent runs
GET /v3/projects/:id/executions
| Parameter | Meaning |
|---|---|
| limit | 1 to 200, default 50. |
| before | The next_before of the previous page. |
| status | Only runs with this result, such as KEY_VALID or KEY_INVALID. |
| script_id, user_key | Only runs of that script, or by that key. |
Newest first. Each run has id, script_id, user_key (null when no key was involved), status, executor, platform, country, game_name, place_id and created_at. The raw runs are kept for 30 days; older days are in the numbers above. A player's address and Roblox id are not part of the answer.
The workspace log and its people
GET /v3/audit
The workspace's log, newest first: limit (1 to 200), before (the next_before of the previous page) and action (for example script.upload). Each entry has id, action, target, detail, actor (a person's name, or the name of the API key when a program did it), via (dashboard, api or system) and created_at. Addresses are never part of it.
GET /v3/members
The people in the workspace, oldest first: member_id, name, role (owner, admin or member) and joined_at. Email addresses are not part of the answer.