Developer documentation

Scope reference

Granular scopes map to backend permissions. Request only the scopes your integration needs.

How scopes work

At key creation, requested scopes are intersected with the creator's role permissions. Routes enforce scopes independently.

  • Studio-licensed project required for API usage
  • Schedule and budget AI reruns require Studio scopes
  • Activity logs record api_key_used events for mutating calls

Scope reference

Projects

ScopeDescription
projects:readList and read project metadata
projects:createCreate projects in the workspace
projects:updateUpdate project settings
projects:archiveArchive projects
projects:deleteDelete projects
projects:exportExport project deliverables

Screenplay & breakdown

ScopeDescription
screenplay:uploadUpload screenplay versions
screenplay:editEdit screenplay content
screenplay:lockLock or unlock production scripts
screenplay:breakdownManage breakdown tags and elements
screenplay:share_linksCreate and manage share links
breakdown:rerunRerun AI breakdown

Scheduling

ScopeDescription
scheduling:readRead schedules and stripboards
scheduling:editEdit schedule data
scheduling:rerunRerun AI schedule generation (Studio)

Budgeting

ScopeDescription
budgeting:readRead budget topsheets and line items
budgeting:editEdit budget data
budgeting:rerunRerun AI budget analysis (Studio)

Coverage

ScopeDescription
coverage:readRead coverage reports
coverage:editEdit coverage content
coverage:rerunRerun AI coverage

Workspace

ScopeDescription
workspace:readRead workspace metadata
workspace:members:readList workspace members
workspace:activity:readRead workspace activity logs
API scopes reference | RivetAI Developers · RivetAI