👥 Customers & VaultCustomers

Update customer details

Update an existing customer's information

PATCH/customers/{id}

Update an existing customer's information


Related endpoints

  • GET /customers/{id}/state — Get customer billing state
  • POST /customers — Create a new customer
  • GET /customers — List customers
  • GET /customers/{id} — Get customer by ID
  • GET /customers/{id}/payment-methods — Get customer payment methods

Common errors

  • 400 invalid_request — malformed payload or failed validation.
  • 401 authentication_error — missing, invalid, expired, or revoked credential. Codes: authentication_failed, invalid_api_key, expired_api_key, api_key_revoked, session_invalid, merchant_required. Carries a WWW-Authenticate: Bearer challenge.
  • 404 resource_missing — the referenced resource does not exist or is not visible to your key.
  • 409 conflict — Idempotency-Key collision with a different body, or a concurrent state-transition conflict.

Idempotency

Pass an Idempotency-Key header (UUID v4 recommended) to make retries safe. Keys are valid for 24 hours; see the idempotency guide.

x-api-key<token>

Your RevKeen merchant API key. Create and manage keys in Dashboard → Settings → Developer. Use rk_sandbox_* for staging/test and rk_live_* for production. The same key may be sent as Authorization: Bearer <key> if that suits your HTTP client better. A missing, invalid, expired, or revoked key returns 401 with a WWW-Authenticate: Bearer challenge; a valid key without the required scope returns 403.

In: header

Path Parameters

id*string

Customer UUID

Formatuuid

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

Stuck on an error response? Ask the RevKeen assistant to explain it.
curl -X PATCH "https://api.revkeen.com/v2/customers/11111111-1111-4111-8111-111111111111" \
  -H "x-api-key: $REVKEEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "customer@example.com",
    "name": "example",
    "phone": "+15551234567",
    "city": "example"
  }'

Synthetic documentation data, validated against the response schema; not a live API result.

{  "data": {    "id": "c2a1e7d4-5b3f-4a8e-9d21-6f0b3e4c7a11",    "merchant_id": "8f14e45f-ceea-4e7a-9b4b-7c3f1a2d5e60",    "merchant_ref_id": "CRM-10482",    "external_id": "usr_123",    "email": "ada.lovelace@example.com",    "name": "Ada Lovelace",    "phone": "+44 20 7946 0958",    "company_name": "Analytical Engines Ltd",    "address_line1": "1 Example Street",    "address_line2": "Suite 4",    "city": "London",    "state": "Greater London",    "postal_code": "EC1A 1BB",    "country": "GB",    "auth_user_id": "00000000-0000-4000-8000-000000000001",    "metadata": {      "crm_id": "10482"    },    "custom_fields": {      "membership_tier": "gold"    },    "created_at": "2026-04-02T10:00:00.000Z",    "updated_at": "2026-04-02T10:05:00.000Z"  }}

Put this endpoint to work