View purchase history and sales orders

The order history API exposes two complementary views of the same cart data. Buyers can retrieve a paginated list of every cart they have created — each document shows exactly what was ordered, at what price, and when. Sellers can retrieve a paginated list of all carts that contain at least one product they listed, giving them a complete picture of their sales activity without requiring a separate orders collection. Both endpoints require a valid JWT token and share the same pagination interface.

Buyer: list purchase history

POST /api/carts/list-my-buy/:pag?/:perpage? Returns all cart documents where cart.user._id matches the authenticated user’s _id. Results are sorted by most recently created first (_id descending) and are split into pages.

Headers

token-access

string

required

A valid JWT token. Format: <jwt-token>

Path parameters (optional)

pag

number

The page number to retrieve. Defaults to 1 if omitted.

perpage

number

The number of cart documents per page. Defaults to 10 if omitted.

Response

msj

string

"Cargando mis compras" on success.

status

boolean

true on success.

data

array

Array of cart documents belonging to the authenticated buyer.

Show Cart document fields

data[]._id

string

Unique cart identifier.

data[].user

object

Buyer profile snapshot captured at cart creation.

Show Buyer fields

data[].user._id

string

Buyer ID.

data[].user.firstName

string

First name.

data[].user.lastName

string

Last name.

data[].user.email

string

Email address.

data[].user.phone

number

Phone number.

data[].user.sex

string

Sex.

data[].user.document

string

Document number.

data[].user.documentType

string

Document type.

data[].user.activate

array

Account activation flags ([{ name, value }]).

data[].products

array

All product line items in the cart.

Show Product line item fields

data[].products[]._id

string

Product ID.

data[].products[].user

object

Seller info snapshot (_id, firstName, lastName, roles, activate).

data[].products[].title

string

Product title.

data[].products[].description

string

Product description.

data[].products[].sizes

array

Selected sizes.

data[].products[].price

number

Original unit price.

data[].products[].discountPrice

string

Discounted price, if applicable.

data[].products[].discount

string

Discount label or percentage.

data[].products[].imageUrlIp

array

Product image URLs.

data[].products[].minCant

number

Stock snapshot at time of add.

data[].products[].cantBuy

number

Quantity purchased.

data[].products[].subtotal

number

Line subtotal (unit price × cantBuy).

data[].products[].date

string

Timestamp when the line was added.

data[].cantBuy

number

Total number of items in the cart.

data[].subtotal

number

Total monetary value of the cart.

data[].date_creation_cart_client

string

ISO date of cart creation.

data[].createdAt

string

Mongoose creation timestamp.

data[].updatedAt

string

Mongoose last-updated timestamp.

pagination

object

Pagination metadata for the result set.

Show Pagination fields

Error response

A 203 is returned with { msj: "Error al cargar mis compras", status: false } if the database query fails.

Example

curl -X POST https://api.example.com/api/carts/list-my-buy \
  -H "token-access: <jwt-token>"

Seller: list sales orders

This endpoint queries on the products[].user._id field — not the top-level cart.user._id. A cart appears in a seller’s sales list if any of its product lines were listed by that seller, even if the cart also contains products from other sellers.

POST /api/carts/list-my-sale/:pag?/:perpage? Returns all cart documents that contain at least one product whose user._id (the seller) matches the authenticated user’s _id. Results are sorted by most recently created first and are paginated using the same interface as the buyer endpoint.

Headers

token-access

string

required

A valid JWT token. Format: <jwt-token>

Path parameters (optional)

pag

number

The page number to retrieve. Defaults to 1 if omitted.

perpage

number

The number of cart documents per page. Defaults to 10 if omitted.

Response

The response shape is identical to the buyer history endpoint.

msj

string

"Cargando mis ventas" on success.

status

boolean

true on success.

data

array

Array of cart documents that contain at least one product listed by the authenticated seller. Each cart document has the same shape described in the buyer history response above, including full buyer info and all product lines.

pagination

object

Pagination metadata.

Show Pagination fields

Error response

A 203 is returned with { msj: "Error al cagar mis ventas", status: false } if the database query fails.

Example

curl -X POST https://api.example.com/api/carts/list-my-sale \
  -H "token-access: <jwt-token>"

Users

Products

Shopping Cart

View purchase history and sales orders

Buyer: list purchase history

Headers

Path parameters (optional)

Response

Error response

Example

Seller: list sales orders

Headers

Path parameters (optional)

Response

Error response

Example

Build docs developers (and LLMs) love

Users

Products

Shopping Cart

Documentation Index

​Buyer: list purchase history

​Headers

​Path parameters (optional)

​Response

​Error response

​Example

​Seller: list sales orders

​Headers

​Path parameters (optional)

​Response

​Error response

​Example

Build docs developers (and LLMs) love

Buyer: list purchase history

Headers

Path parameters (optional)

Response

Error response

Example

Seller: list sales orders

Headers

Path parameters (optional)

Response

Error response

Example