API reference · Identity & onboarding

PediID Rights

POST Exercise a right over your own record

POST /id/me/right/{kind}

EXPORT, CORRECTION, DISPUTE, RESTRICTION or ERASURE. A correction supersedes rather than overwrites, so 'what did you tell them in March' stays answerable in April. A disputed fact is withheld rather than released stale, because an integrator that receives a contested value has no way to know it is contested. On ERASURE the values are overwritten and the record closed. That is not destruction: backups taken before it still hold the data, and anything already released to an integrator is beyond reach. The response says so in those words.

Headers

NameNotes
AuthorizationBearer token
X-TenantYour tenant
X-Environmenttest or live

Path parameters

Name
kind

Query parameters

NameDefault
resourceCodeOptional
fieldNameOptional
detailOptional

Example

Response: GenericResponseRightsRequestResponse

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

Responses

StatusWhen
200Right recorded

GET Every right you have exercised, and what came of it

GET /id/me/rights

Including the ones that were refused, and why. A rights log that showed only successes would be a worse record than none.

Headers

NameNotes
AuthorizationBearer token
X-TenantYour tenant
X-Environmenttest or live

Example

Response: GenericResponseListRightsRequestResponse

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

Responses

StatusWhen
200Your rights history

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