Skip to content
GitmoapAPIBeta
Schema

LimitIncreaseRequestView

Wire view of a limit-increase request.

Shape

  • created_atstring
  • current_effectiveinteger · int640–∞
  • justificationstring
  • limit_keyLimitKeystorage_bytesmax_repos_per_groupmax_members_per_scopemax_teams_per_orgmax_members_per_teammax_custom_roles_per_orgmax_limits_per_scopemax_approval_rules_per_scopemax_scim_tokens_per_orgmax_ai_agents_per_orgmax_ai_concurrent_sessions_per_orgmax_ai_sessions_per_org_per_daymax_ai_revision_drafts_per_org_per_daymax_balance_adjustments_per_namespace_per_daymax_agent_workspace_minutes_per_monthai_management_fee_bpsmax_open_mrs_per_repomax_comments_per_mrmax_branches_per_repomax_tags_per_repomax_webhooks_per_scopemax_service_accounts_per_scopemax_branch_rules_per_scopemax_provider_connections_per_scopemax_reviewers_per_mrmax_reactions_per_commentmax_commit_statuses_per_commitmax_provider_installs_per_groupmax_concurrent_pipeline_runsmax_pipeline_runs_per_monthmax_pipeline_minutes_per_monthmax_pipeline_dag_nodesmax_push_bytesmax_package_bytesmax_release_asset_bytesmax_node_log_bytesmax_releases_per_repomax_pipelines_per_repomax_open_issues_per_scopemax_labels_per_scopemax_milestones_per_scopemax_blueprints_per_scopemax_wiki_pages_per_scopemax_services_per_scopemax_environments_per_scopemax_scorecards_per_scopemax_pipeline_components_per_scopemax_versions_per_pipeline_componentmax_comments_per_issuemax_relations_per_issuemax_children_per_issuemax_activities_per_issuemax_code_links_per_issuemax_mr_links_per_issuemax_anchors_per_issuemax_anchors_per_repomax_criteria_per_issuemax_criteria_per_repomax_code_todos_per_repomax_root_groupsA recognised limit name — every PlanLimits cap plus the user-scoped max_root_groups. The identity a limit-increase request and a namespace override are keyed by.
  • request_idLimitIncreaseRequestId (string · uuid)
  • requested_byUserId (string · uuid)
  • requested_valueinteger · int640–∞
  • root_group_idGroupId (string · uuid)
  • statusLimitRequestStatuspendingapproveddeniedappliedLifecycle of a limit-increase request. Applied is the terminal success state (the override was written); Approved exists for symmetry but the approve path applies immediately, so a persisted request is never left Approved-but-not-Applied.
  • updated_atstring
  • applied_valueinteger · int64 or nulloptional0–∞
  • decided_atstring or nulloptional
  • decided_bystring or nulloptional
  • decision_notestring or nulloptional

Example

Synthesized example
{
"created_at": "2026-10-16T19:37:40Z",
"current_effective": 9,
"justification": "justification-813d",
"limit_key": "storage_bytes",
"request_id": "af8008c2-ff67-42de-80ae-c9ea8860291c",
"requested_by": "a3f1c2d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
"requested_value": 28,
"root_group_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69",
"status": "pending",
"updated_at": "2026-10-14T00:04:54Z",
"applied_value": 47,
"decided_at": "2026-10-17T07:22:54Z",
"decided_by": "b7e2d1c0-9f8e-4d7c-a6b5-c4d3e2f1a0b9",
"decision_note": "decision-note-295d"
}

Graph

Contains

No named schema inside.

Used by