Update Customer

​

Overview

The customer update endpoint allows you to modify existing customer information. You can perform both partial and full updates to customer records.

​

Base URL

PATCH /customers/{id}

​

Authentication

Authorization: Bearer YOUR_API_KEY

​

Request Parameters

​

Path Parameters

​

Body Parameters

​

Examples

curl -X PATCH "https://api.spendjuice.com/customers/6f7e1e7f-93d1-4fcc-b7a4-738f869615c8" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone_number": "+2348012345678",
    "billing_address": {
      "line1": "123 Test lane",
      "city": "Anon"
    }
  }'

​

Response

​

Success Response (200 OK)

{
    "data": {
        "id": "6f7e1e7f-93d1-4fcc-b7a4-738f869615c8",
        "first_name": "Test",
        "last_name": "Customer",
        "email": "test@custom.er",
        "phone_number": "+2348012345678",
        "billing_address": {
            "line1": "123 Test lane",
            "line2": "3456 Mike Drive",
            "city": "Anon",
            "state": "Acme",
            "zip_code": "12345",
            "country": "US"
        }
    }
}

​

Error Responses

{
  "error": {
    "code": "invalid_request",
    "message": "Invalid parameters provided",
    "details": {
      "phone_number": ["Invalid phone number format"]
    }
  }
}

{
  "error": {
    "code": "not_found",
    "message": "Customer not found"
  }
}

{
  "error": {
    "code": "validation_error",
    "message": "The request contains invalid parameters",
    "details": {
      "email": ["Invalid email format"]
    }
  }
}

​

Update Rules

​

Rate Limits

​

Versioning

The current version of this API is v1. We recommend including a version accept header:

Accept: application/json;version=1

​

Best Practices

1. Partial Updates

   • Only send fields that need to be changed
   • Use PATCH for partial updates
   • Validate data before sending

2. Error Handling

   • Implement proper error handling
   • Validate response status codes
   • Log failed update attempts

3. Idempotency

   • Use idempotency keys for critical updates
   • Retry failed requests with the same idempotency key

4. Validation

   • Validate all input fields client-side
   • Handle validation errors appropriately
   • Check response data matches expected format