Namespace API

Namespace management requires an approved provider API key. Name mutations remain scoped to the authenticated provider’s namespace.

Authentication

Authorization: Bearer <approved-provider-key>
Content-Type: application/json

Free API keys cannot create or manage namespaces. The provider must be approved before namespace requests are accepted.

Submit a namespace

POST /v1/namespaces

{
  "slug": "redotpay",
  "description": "RedotPay wallet names",
  "registration_policy": "provider_managed",
  "reserved_names": ["support", "admin"]
}

{
  "slug": "redotpay",
  "provider_id": "provider_123",
  "status": "submitted",
  "registration_policy": "provider_managed",
  "reserved_names": ["support", "admin"]
}

Register and resolve a name

POST /v1/namespaces/redotpay/names

{
  "label": "alice",
  "controller_ref": "customer_42",
  "chain": "base",
  "asset": "USDC",
  "address": "0xRecipient…"
}

The namespace must be active. Check availability before registering a label and treat a 409 response as a conflict. The full name is resolved through the normal resolver:

POST /v1/resolve
Authorization: Bearer <approved-provider-key>

{ "type": "provider_name", "value": "alice.redotpay" }

Endpoints

• GET /v1/namespaces — list your namespaces
• POST /v1/namespaces — submit a namespace
• GET /v1/namespaces/:namespace — read namespace names and usage
• GET /v1/namespaces/:namespace/usage — read aggregate usage
• GET /v1/namespaces/:namespace/names/:label/availability — check a label
• POST /v1/namespaces/:namespace/names — register a name
• GET/PATCH/DELETE /v1/namespaces/:namespace/names/:label — manage a name

Update and remove

PATCH /v1/namespaces/redotpay/names/alice

{
  "chain": "base",
  "asset": "USDC",
  "address": "0xNewRecipient…"
}

Use DELETE to mark a name removed. Keep provider customer records outside Rezva; the API stores registry metadata and aggregate usage, not wallet account data.

Resolution behavior

A successful provider-name resolution returns an active, payment-ready response when the name has a usable destination. Missing, removed, or destination-less names return an error or no payable option. Always apply the same wallet gating rules as other identifiers.