Manage identifiers

Use the identifier resource to inspect, update, suspend, or remove a controller-owned mapping while preserving its audit history.

Required headers

Authorization: Bearer <approved-provider-key>
X-Controller-Wallet: 0xController…
X-Controller-Authorization: <signed authorization payload>

Read current state

GET /v1/identifiers/:id

Update destinations

PATCH /v1/identifiers/:id
{
  "payment_options": [
    {
      "chain": "base",
      "asset": "USDC",
      "address": "0xNewRecipient…",
      "network_identifier": "eip155:8453"
    }
  ]
}

A changed destination enters update_pending. Resolve the identifier again only after the new destination is active.

Common operations

• GET /v1/identifiers/:id — read current state
• PATCH /v1/identifiers/:id — update metadata or destinations
• DELETE /v1/identifiers/:id — remove with cooldown
• GET /v1/identifiers/:id/history — inspect registry events
• POST /v1/identifiers/:id/emergency-suspend — stop payment immediately

Important state rules

• Destination changes enter update_pending during the safety period.
• Removed mappings may become available only after available_at.
• Suspended and revoked mappings are not payable.
• Registry events must remain auditable after changes.