Skip to content
GitmoapAPIBeta
Identity & platformlegal
GET/user/legal-acceptances/pending

The legal documents you have yet to accept

list_my_pending_legal_acceptances
  • user:read
    A token needs the user:read scope: Read user profilesGranted by mcp_agent, mcp_agent_write, read_api, write_api.Every operation this scope unlocks
  • Single-resource

    x-gitmoap-isolation: {"kind":"single_or_self_scoped"}

The version required of you, which until you accept it refuses your changes while reading stays open; a version introducing a charge, which is only ever accepted expressly and never refuses anything; and the version coming, which you can accept before it takes effect. Only a person owes an acceptance: a service account's or an agent's list is always empty.

Responses

200What you have yet to acceptapplication/json
  • itemsarray of PendingLegalAcceptanceEach document to accept. Empty when you owe nothing.
    • The PendingLegalAcceptance schema
    • document_keyLegalDocumentKeyterms-of-serviceacceptable-use-policycontent-reporting-policysecurity-disclosure-policyprivacy-statementcookie-statementdata-processing-addendumsubprocessorsentityThe document.
    • effective_dateCalendarDate (string)The day it takes effect, in UTC.
    • gatesbooleanWhether, until you accept it, your changes are refused. Reading always stays open.
    • introduces_chargebooleanWhether it introduces a charge, which is only ever accepted expressly and never blocks you.
    • takes_effect_in_futurebooleanWhether it has yet to take effect: it can be accepted now, before it binds.
    • titlestringIts title.
    • versionLegalVersion (string)The version to accept.
    • change_summarystring or nulloptionalWhat changed since the version before it, as its publisher summarised it. None for a first version.
200 exampleSynthesized example
{
"items": [
{
"document_key": "terms-of-service",
"effective_date": "effective-date-1bf8",
"gates": false,
"introduces_charge": false,
"takes_effect_in_future": false,
"title": "Draw the region map from operation density",
"version": "version-a608"
}
]
}
401Unauthorizedapplication/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-e2be",
"message": "Stream pipeline status into the run header"
}
}
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-33b4",
"message": "Label every synthesized example"
}
}

CLI

gitmoap legal list-my-pending-acceptances