API reference · Identity & onboarding

PediID Owner

GET/id/meYour own PediID record, in summary
GET/id/me/earningsWhat you have earned
GET/id/me/releasesWhat has left your record, to whom, and at what grade

GET Your own PediID record, in summary

GET /id/me

Answers about the caller and nobody else: the subject is resolved from the token, never from a path or a query parameter. There is no variant of this endpoint that takes somebody else's identifier, because an endpoint that can name another person is one an attacker only has to find.

Headers

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

Example

Response: GenericResponseOwnerSummaryResponse

curl -X GET "https://api.bridgemoni.com/id/me" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV"

{
  "data": {
    "piid": "string",
    "handle": "string",
    "subjectStatus": "ENROLLING",
    "identityAssuranceLevel": "IAL1",
    "lastProofedDateTime": "2026-09-25T10:00:00Z",
    "nextReproofDueDateTime": "2026-09-25T10:00:00Z"
  },
  "description": "Your record"
}

Responses

Status	When
`200`	Your record
`404`	You hold no PediID identity. The same answer is given whether none exists or it is simply not visible to this caller.

GET What you have earned

GET /id/me/earnings

Unmatured earnings are still inside the dispute window and can be clawed back; matured earnings have reached your main wallet and cannot. The two are reported separately because a balance that mixes them tells you that you have money you may yet lose.

Headers

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

Example

Response: GenericResponseEarningsResponse

curl -X GET "https://api.bridgemoni.com/id/me/earnings" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV"

{
  "data": {
    "currencyCode": "string",
    "unmatured": 0,
    "matured": 0,
    "clawedBack": 0,
    "eventCount": 0
  },
  "description": "Your earnings"
}

Responses

Status	When
`200`	Your earnings

GET What has left your record, to whom, and at what grade

GET /id/me/releases

The release ledger, not the consent ledger. A consent says somebody was ALLOWED to read something; this says they DID. The honest answer to most 'were we exposed' questions is 'they were allowed to and never asked', and that is only sayable because the two are recorded separately. Each entry carries the grade the fact held WHEN IT LEFT, never the grade it holds today - recomputing would quietly rewrite history in the integrator's favour.

Headers

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

Example

Response: GenericResponseListReleaseHistoryEntry

curl -X GET "https://api.bridgemoni.com/id/me/releases" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV"

{
  "data": [
    {
      "integratorDisplayName": "string",
      "resourceCode": "string",
      "fieldName": "string",
      "assuranceGradeAtRelease": "string",
      "derivedAnswer": true,
      "releasedDateTime": "2026-09-25T10:00:00Z"
    }
  ],
  "description": "Your release history"
}

Responses

Status	When
`200`	Your release history

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