PUT /api/vendor-customer/1 HTTP/1.1
Host: <API_HOST>
Accept: application/json
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "customerGroupId": 1,
  "username": "sample.customer",
  "email": "customer@example.com",
  "mobileNumber": "9876543210",
  "newsletter": 1,
  "mailStatus": 1,
  "status": 1,
  "firstName": "Asha",
  "lastName": "Kumar"
}

{
  "status": 1,
  "message": "Resource updated successfully",
  "data": {
    "customerId": 1,
    "firstName": "Asha",
    "lastName": "Kumar",
    "email": "customer@example.com",
    "status": 1
  }
}

{
  "status": 0,
  "message": "Invalid request or resource."
}

Customer directory

Update Customer

Put /api/vendor-customer/:id

Authentication: Vendor bearer token required for protected operations; verify exact permission decorator in controller.

Feature area: Customers

Implementation source: src/api/vendor/controllers/CustomerController.ts

Request example provenance: Illustrative update body based on Vendor Customer create fields; verify update DTO and omit password unless explicitly required.

Response example provenance: Illustrative response envelope only. This route inventory does not include its route-specific @apiSuccessExample; response fields and messages must be verified in the matching controller/service. The example is intended to show the common response-wrapper style, not to define a guaranteed response schema.

Example status: Illustrative. The example is included to demonstrate request/response shape in the reference UI; verify the owning controller and request DTO before using it as a contract.

PUT

/

api

/

vendor-customer

/

{id}

PUT /api/vendor-customer/1 HTTP/1.1
Host: <API_HOST>
Accept: application/json
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "customerGroupId": 1,
  "username": "sample.customer",
  "email": "customer@example.com",
  "mobileNumber": "9876543210",
  "newsletter": 1,
  "mailStatus": 1,
  "status": 1,
  "firstName": "Asha",
  "lastName": "Kumar"
}

{
  "status": 1,
  "message": "Resource updated successfully",
  "data": {
    "customerId": 1,
    "firstName": "Asha",
    "lastName": "Kumar",
    "email": "customer@example.com",
    "status": 1
  }
}

{
  "status": 0,
  "message": "Invalid request or resource."
}

Authorizations

Authorization

string

header

required

Paste the JWT access token returned by the corresponding login endpoint.

Path Parameters

id

string

required

Value for id.

Body

application/json

Sample request body. Illustrative update body based on Vendor Customer create fields; verify update DTO and omit password unless explicitly required. Treat this as an illustrative example, not a complete DTO contract.

customerGroupId

integer

username

string

email

string

mobileNumber

string

mailStatus

integer

status

integer

firstName

string

lastName

string

Response

Successful response. Illustrative response envelope only. This route inventory does not include its route-specific @apiSuccessExample; response fields and messages must be verified in the matching controller/service. The example is intended to show the common response-wrapper style, not to define a guaranteed response schema. Example is illustrative and does not guarantee a stable response contract.

status

integer

message

string

data

object

Show child attributes