Gravv DOCS
Docs Agent Get Started
API Reference Update a customer

Update a customer

Update details of a specific customer. The path customer_id parameter is cosmetic — the service reads customer_id from the request body (marked required there). Only provided fields are updated.

PUT/v1/customers/{customer_id}

Path Parameters

Cosmetic path parameter — the service resolves the customer from customer_id in the request body, not this value.

Request Body

UUID of the customer to update. Required in the request body — the path customer_id parameter is cosmetic only.

Possible values: male, female, other

List of associated persons to update or add. If id is provided the existing record is updated; if omitted a new person is created (all required fields must then be present).

UUID of an existing associated person. Omit to add a new person.

Possible values: male, female, other

Request Examples

{
"customer_id": "e59daa17-20ed-4727-833c-e1c633782cc8",
"first_name": "Jane",
"last_name": "Smith",
"phone": "+15555550199"
}
{
"customer_id": "e59daa17-20ed-4727-833c-e1c633782cc8",
"business_name": "Acme Corp Ltd",
"business_description": "Enterprise software solutions",
"business_type": "private_limited",
"business_industry": "Technology",
"registration_number": "RC-111222",
"associated_persons": [
{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "first_name": "Jane",
  "last_name": "Doe",
  "phone": "+15555550102"
}
]
}

Responses

Status Description
200 Customer updated
400 Bad request — invalid or missing parameters

200 response

{
"data": {
"message": "customer updated successfully",
"status": true
},
"error": null
}

400 response

{
"data": null,
"error": "invalid request body"
}

Authorization

  • ApiKeyAuth
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.

Ask me anything about the documentation.

ESC