Skip to content
GitmoapAPIBeta
Organizegroups
GET/groups/{group_id}/limits

Get the full usage-and-limits view for a group's namespace

get_namespace_limits
  • group:read
    A token needs the group:read scope: View groups and namespace usageGranted by mcp_agent, mcp_agent_write, read_api, write_api.Every operation this scope unlocks

Every limit that applies, with its effective maximum after any increase granted to the organization, and live usage beside it. Storage and pipeline figures are the organization's; counts such as repositories, members, teams, webhooks and open issues are for the named group itself. Anyone who can see the group may read it.

Parameters

Path
  • group_idGroupId (string · uuid)Group ID (namespace usage is reported for its root; group-scoped counts for this group)

Responses

200Namespace usage and effective limitsapplication/json
  • group_countsarray of UsageLimitEntryGroup-scoped caps with live counts evaluated on group_id itself.
    • The UsageLimitEntry schema
    • limitinteger · int640–∞
    • nameLimitNamestorage_bytesconcurrent_pipeline_runspipeline_runs_this_monthpipeline_minutes_this_monthreposmembersteamscustom_rolesaccess_limitsapproval_rulesscim_tokenswebhooksservice_accountsbranch_rulesprovider_connectionsprovider_installsopen_issueslabelsmilestonesblueprintswiki_pagesservicesenvironmentsscorecardspipeline_componentsopen_mrs_per_repocomments_per_mrbranches_per_repotags_per_reporeviewers_per_mrreleases_per_repopipelines_per_repoanchors_per_repocriteria_per_repocode_todos_per_reporeactions_per_commentcommit_statuses_per_commitcomments_per_issuerelations_per_issuechildren_per_issueanchors_per_issuecriteria_per_issuesso_invites_per_scopepush_bytespackage_bytesrelease_asset_bytespipeline_dag_nodesversions_per_pipeline_componentmembers_per_teamWhich limit a usage-and-limits entry describes.
    • usedinteger · int640–∞
  • group_idGroupId (string · uuid)The group the request named; the group-scoped counts are evaluated on it.
  • namespacearray of UsageLimitEntryNamespace-wide quotas with live usage.
    • The UsageLimitEntry schema
    • limitinteger · int640–∞
    • nameLimitNamestorage_bytesconcurrent_pipeline_runspipeline_runs_this_monthpipeline_minutes_this_monthreposmembersteamscustom_rolesaccess_limitsapproval_rulesscim_tokenswebhooksservice_accountsbranch_rulesprovider_connectionsprovider_installsopen_issueslabelsmilestonesblueprintswiki_pagesservicesenvironmentsscorecardspipeline_componentsopen_mrs_per_repocomments_per_mrbranches_per_repotags_per_reporeviewers_per_mrreleases_per_repopipelines_per_repoanchors_per_repocriteria_per_repocode_todos_per_reporeactions_per_commentcommit_statuses_per_commitcomments_per_issuerelations_per_issuechildren_per_issueanchors_per_issuecriteria_per_issuesso_invites_per_scopepush_bytespackage_bytesrelease_asset_bytespipeline_dag_nodesversions_per_pipeline_componentmembers_per_teamWhich limit a usage-and-limits entry describes.
    • usedinteger · int640–∞
  • plan_tierPlanTierfreeproteamenterpriseThe subscription plan an organization is on, which sets its resource limits. From smallest to largest: free, pro, team, enterprise.
  • root_group_idGroupId (string · uuid)The root group the queried group belongs to; namespace usage is reported for it.
  • scope_limitsarray of ScopeLimitEntryLimits that apply per repository, merge request, issue or operation, with what each applies to. Usage is reported on each resource.
    • The ScopeLimitEntry schema
    • limitinteger · int640–∞
    • nameLimitNamestorage_bytesconcurrent_pipeline_runspipeline_runs_this_monthpipeline_minutes_this_monthreposmembersteamscustom_rolesaccess_limitsapproval_rulesscim_tokenswebhooksservice_accountsbranch_rulesprovider_connectionsprovider_installsopen_issueslabelsmilestonesblueprintswiki_pagesservicesenvironmentsscorecardspipeline_componentsopen_mrs_per_repocomments_per_mrbranches_per_repotags_per_reporeviewers_per_mrreleases_per_repopipelines_per_repoanchors_per_repocriteria_per_repocode_todos_per_reporeactions_per_commentcommit_statuses_per_commitcomments_per_issuerelations_per_issuechildren_per_issueanchors_per_issuecriteria_per_issuesso_invites_per_scopepush_bytespackage_bytesrelease_asset_bytespipeline_dag_nodesversions_per_pipeline_componentmembers_per_teamWhich limit a usage-and-limits entry describes.
    • scopeLimitScoperepomerge_requestissuecommentcommitreleasepushrunpackagepipeline_componentteamnamespaceWhat a per-resource limit applies to — each repository, each merge request, each team, and so on. Usage against it is reported on that resource, not in the organization-wide view.
200 exampleSynthesized example
{
"group_counts": [
{
"limit": 2,
"name": "storage_bytes",
"used": 15
}
],
"group_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69",
"namespace": [
{
"limit": 60,
"name": "storage_bytes",
"used": 7
},
{
"limit": 79,
"name": "storage_bytes",
"used": 53
}
],
"plan_tier": "free",
"root_group_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69",
"scope_limits": [
{
"limit": 71,
"name": "storage_bytes",
"scope": "repo"
},
{
"limit": 37,
"name": "storage_bytes",
"scope": "repo"
}
]
}
400Bad request — a path parameter is not a well-formed value of its typeapplication/json
Error codes
  • BAD_REQUESTThe request is malformed: a parameter or a body field is not a well-formed value of its type
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
400 exampleSynthesized example
{
"error": {
"code": "code-8a32",
"message": "Label every synthesized example"
}
}
401Unauthenticated — no credential, or an invalid oneapplication/json
Error codes
  • UNAUTHORIZEDNo credential was sent, or the one sent is invalid, expired or revoked
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
401 exampleSynthesized example
{
"error": {
"code": "code-c63d",
"message": "Inline scalar newtypes but keep their brand"
}
}
403Forbidden — the caller's access level or token scope is insufficientapplication/json
Error codes
  • FORBIDDENYou are signed in but may not do this here; reason names the permission or the rule that refused it
  • INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs; required_scope names it
  • PERMISSION_REQUIREDYou need a permission you do not hold here; the message names it
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
403 exampleSynthesized example
{
"error": {
"code": "code-aafe",
"message": "Pin a page's payload to the build that rendered it"
}
}
404Group not foundapplication/json
Error codes
  • NOT_FOUNDThe resource does not exist — or exists and you cannot see it: a private resource you have no access to answers exactly as an absent one does
  • errorErrorBody
    • The ErrorBody schema
    • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
    • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
    • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
    • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
404 exampleSynthesized example
{
"error": {
"code": "code-9d06",
"message": "Inline scalar newtypes but keep their brand"
}
}

CLI

gitmoap groups get-namespace-limits

  • --group-ididGroup ID (namespace usage is reported for its root; group-scoped counts for this group) (id or group path)

Used in these guides