API reference · Identity & onboarding

Attestation score

GET/accountholder/{type}/{value}/attestation/scoreAn account holder's own attestation score, decomposed
GET/accountholder/{type}/{value}/attestation/score/releasedThe releasable view of an account holder's attestation score

GET An account holder's own attestation score, decomposed

GET /accountholder/{type}/{value}/attestation/score

Scores the evidence, never the person. Five pillars — registry, community, documentary, physical and completeness — plus a bounded vouching adjustment, and the next actions that would raise it. A score without a way to act on it grades somebody and abandons them.

Headers

Name	Notes
`Authorization`	Bearer token
`X-Tenant`	Your tenant
`X-Environment`	test or live

Path parameters

Name
`type`
`value`

Example

Response: GenericResponseAttestationScoreResponse

curl -X GET "https://api.bridgemoni.com/accountholder/value/value/attestation/score" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV"

{
  "data": {
    "reference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
    "attestationLevel": "1",
    "pillars": [
      {
        "pillar": "REGISTRY",
        "score": "1",
        "of": "1",
        "status": "ABSENT"
      }
    ],
    "vouchingAdjustment": {
      "value": "1",
      "of": "1",
      "vouchesMade": "1",
      "laterVerifiedIndependently": "1",
      "adverseOutcomes": "1",
      "note": "string"
    },
    "community": {
      "liveAttestations": "1",
      "distinctBases": "1",
      "ceilingReachable": "1",
      "longestRelationshipYears": "1"
    },
    "nextBestActions": [
      {
        "action": "VERIFY_NATIONAL_IDENTIFIER",
        "pillar": "REGISTRY",
        "wouldAdd": "1",
        "suggestedBases": [
          "SAME_HOUSEHOLD"
        ]
      }
    ],
    "computedDateTime": "2026-09-25T10:00:00Z"
  },
  "description": "Attestation score fetched successfully"
}

Responses

Status	When
`200`	Attestation score fetched successfully

GET The releasable view of an account holder's attestation score

GET /accountholder/{type}/{value}/attestation/score/released

The level, the pillars, the counts, and only those attestors who chose to be named. There is no field on this payload that can carry a counted attestor, so the vouching graph cannot leave through it.

Headers

Name	Notes
`Authorization`	Bearer token
`X-Tenant`	Your tenant
`X-Environment`	test or live

Path parameters

Name
`type`
`value`

Example

Response: GenericResponseIntegratorAttestationScoreResponse

curl -X GET "https://api.bridgemoni.com/accountholder/value/value/attestation/score/released" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV"

{
  "data": {
    "attestationLevel": "1",
    "pillars": [
      {
        "pillar": "REGISTRY",
        "score": "1",
        "of": "1",
        "status": "ABSENT"
      }
    ],
    "communityAttestationCount": "1",
    "distinctBases": "1",
    "vouchingAdjustment": "1",
    "namedInstitutionalAttestors": [
      {
        "attestorName": {
          "name": "string"
        },
        "role": "TRADITIONAL_RULER",
        "basis": "SAME_HOUSEHOLD",
        "knownSinceYears": "1",
        "corroborationStatus": "CORROBORATED"
      }
    ]
  },
  "description": "Attestation score fetched successfully"
}

Responses

Status	When
`200`	Attestation score fetched successfully

Generated from the OpenAPI document. Branch on the HTTP status: there is no machine-readable error code on the wire. Errors