POST /api/demo-vendor/login HTTP/1.1
Host: <API_HOST>
Accept: application/json
Content-Type: application/json

{
  "emailId": "vendor@example.com",
  "password": "<PASSWORD>"
}

{
  "status": 1,
  "message": "Resource created successfully",
  "data": {
    "id": 1,
    "name": "Example resource",
    "status": 1
  }
}

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

Vendor account and authentication

Authenticate or process Demo Login

Post /api/demo-vendor/login

Authentication: Login endpoint; no bearer token is sent.

Feature area: Vendor Access & Login

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

Request example provenance: Illustrative login body; confirm the legacy demo-login DTO before using this route. Prefer /api/demo-vendor/login-new when following the documented email/password flow.

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.

POST

api

demo-vendor

POST /api/demo-vendor/login HTTP/1.1
Host: <API_HOST>
Accept: application/json
Content-Type: application/json

{
  "emailId": "vendor@example.com",
  "password": "<PASSWORD>"
}

{
  "status": 1,
  "message": "Resource created successfully",
  "data": {
    "id": 1,
    "name": "Example resource",
    "status": 1
  }
}

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

Body

application/json

Sample request body. Illustrative login body; confirm the legacy demo-login DTO before using this route. Prefer /api/demo-vendor/login-new when following the documented email/password flow. Treat this as an illustrative example, not a complete DTO contract.

emailId

string

password

string

write-only

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

Store API

Vendor API

Authenticate or process Demo Login

Body

Response