Users API — orders, likes, and issues

The users API provides endpoints for authenticated users to manage their activity on the platform. Users can view their full order history, toggle likes on events (which increments or decrements the event’s likes_count), and submit support issues with an optional image attachment.

GET /api/user/get-orders/:userId

Returns all ticket records for a user, ordered by most recent first. Each record comes directly from the tickets table.

No authentication middleware is applied to this endpoint in the current router. Validate user identity in your client before exposing order data.

userId

string

required

UUID of the user whose orders to fetch.

curl https://api.tktplz.me/api/user/get-orders/user-uuid

Response

success

boolean

true on success.

data

array

Array of ticket objects ordered by createdAt descending.

Show ticket object properties

string

Ticket UUID.

userId

string

Owner’s user UUID.

eventId

string

Event UUID.

bookingID

string

Human-readable booking reference.

orderId

string

Razorpay order ID.

paymentId

string

Razorpay payment ID.

eventType

string

Event category.

numberOfTickets

number

Quantity purchased.

totalAmount

string

Total paid (decimal string).

baseAmount

string

Base price excluding convenience fee.

status

string

"CONFIRMED", "PENDING", "CANCELLED - REFUND DUE", or "CANCELLED - REFUND PROCESSED".

seat_no

string

Seat labels for Seating events.

zone

string

Zone name for Open/Online events.

checkInStatus

string

"NOT_CHECKED_IN" or "CHECKED_IN".

valid_till

string

ISO 8601 expiry datetime.

createdAt

string

ISO 8601 purchase timestamp.

eventDetails

object

Snapshot of event metadata stored at purchase time.

{
  "success": true,
  "data": [
    {
      "id": "ticket-uuid",
      "bookingID": "BKG-12345",
      "orderId": "order_Razorpay123",
      "eventType": "Seating",
      "numberOfTickets": 2,
      "totalAmount": "550.00",
      "baseAmount": "500.00",
      "status": "CONFIRMED",
      "seat_no": "A5, A6",
      "checkInStatus": "NOT_CHECKED_IN",
      "valid_till": "2026-08-01T20:28:00.000Z",
      "createdAt": "2026-07-15T09:00:00.000Z"
    }
  ]
}

POST /api/user/events/like

Adds a like for an event. If the user has already liked the event, the endpoint returns success without inserting a duplicate. On a new like, the event’s likes_count field is incremented by 1.

eventId

string

required

UUID of the event to like.

userId

string

required

UUID of the user liking the event.

curl -X POST https://api.tktplz.me/api/user/events/like \
  -H "Content-Type: application/json" \
  -d '{"eventId": "event-uuid", "userId": "user-uuid"}'

Response

{ "success": true, "message": "Event liked" }

Or, if already liked:

{ "success": true, "message": "Already liked" }

DELETE /api/user/events/like

Removes a like from an event. If the like record is found and deleted, the event’s likes_count is decremented by 1.

eventId

string

required

UUID of the event to unlike.

userId

string

required

UUID of the user removing the like.

curl -X DELETE https://api.tktplz.me/api/user/events/like \
  -H "Content-Type: application/json" \
  -d '{"eventId": "event-uuid", "userId": "user-uuid"}'

Response

{ "success": true, "message": "Event unliked" }

POST /api/user/submit-issue

Submits a support issue to the admin team. An optional screenshot image can be attached as multipart/form-data. Images are uploaded to Cloudinary under the issue-screenshots folder and the resulting URL is stored in the issues table.

name

string

required

Name of the person submitting the issue.

string

required

Contact email address.

subject

string

required

Brief title describing the issue.

description

string

required

Full description of the problem.

image

file

Optional screenshot. Send as multipart/form-data with the field name image.

# Without image
curl -X POST https://api.tktplz.me/api/user/submit-issue \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Alice",
    "email": "alice@example.com",
    "subject": "Payment deducted but ticket not issued",
    "description": "I completed payment for order_Xyz123 but did not receive a ticket."
  }'

# With image
curl -X POST https://api.tktplz.me/api/user/submit-issue \
  -F "name=Alice" \
  -F "email=alice@example.com" \
  -F "subject=Payment deducted but ticket not issued" \
  -F "description=I completed payment for order_Xyz123 but did not receive a ticket." \
  -F "image=@/path/to/screenshot.png"

Response

{
  "success": true,
  "message": "Issue submitted successfully. Our team will review it and get back to you soon."
}

Stored fields in the issues table

string

Auto-generated UUID.

name

string

Submitter’s name.

string

Contact email.

subject

string

Issue title.

description

string

Full description.

imageUrl

string

Cloudinary URL of the screenshot, or null.

status

string

"open" by default; updated to "resolved" by admins.

createdAt

string

ISO 8601 timestamp.

Overview

Endpoints

Users API — orders, likes, and issues

GET /api/user/get-orders/:userId

POST /api/user/events/like

DELETE /api/user/events/like

POST /api/user/submit-issue

Build docs developers (and LLMs) love

Overview

Endpoints

Documentation Index

​GET /api/user/get-orders/:userId

​POST /api/user/events/like

​DELETE /api/user/events/like

​POST /api/user/submit-issue

Build docs developers (and LLMs) love

GET /api/user/get-orders/:userId

POST /api/user/events/like

DELETE /api/user/events/like

POST /api/user/submit-issue