Shop It Docs
Developer ResourcesSupport

Support Requests Mobile API Reference

Integration reference for mobile support request endpoints.

Support Requests Mobile API Reference

Audience: Mobile/frontend developers Scope: Mobile support request contracts currently implemented.


Mobile APIs

Create Support Request

Endpoint

POST /api/mobile/support-requests

Auth

  • Authorization: Bearer <user-jwt>

Request body

{
	"category": "account",
	"subject": "Unable to log in",
	"message": "I cannot log in on Android."
}

Rules:

  • creates the parent support request and the initial requester message in one transaction
  • categories: account, payment, technical, other

List Support Requests

Endpoint

GET /api/mobile/support-requests

Returns only the current mobile user’s own support requests.

Response notes:

  • mobile responses do not expose internal admin UUIDs
  • use isAssigned to decide whether the ticket already has staff ownership

Get Support Request Detail

Endpoint

GET /api/mobile/support-requests/{id}

Returns:

  • support request metadata
  • ordered message thread

Response (messages shape)

{
	"message": "Support request fetched successfully",
	"data": {
		"id": 1,
		"category": "technical",
		"subject": "App crashes on checkout",
		"status": "in_progress",
		"isAssigned": true,
		"resolutionNote": null,
		"resolvedAt": null,
		"closedAt": null,
		"lastCustomerMessageAt": "2026-03-17T10:05:00.000Z",
		"lastAdminMessageAt": "2026-03-17T10:06:00.000Z",
		"messages": [
			{
				"id": 10,
				"authorType": "customer",
				"authorName": "Alex Customer",
				"authorImage": "https://cdn.example.com/customer.png",
				"body": "App crashes on checkout.",
				"createdAt": "2026-03-17T10:04:00.000Z"
			},
			{
				"id": 11,
				"authorType": "admin",
				"authorName": "Support Agent",
				"authorImage": "https://cdn.example.com/admin.png",
				"body": "Thanks, we are looking into it.",
				"createdAt": "2026-03-17T10:06:00.000Z"
			}
		],
		"createdAt": "2026-03-17T10:00:00.000Z",
		"updatedAt": "2026-03-17T10:06:00.000Z"
	}
}

Add Mobile User Reply

Endpoint

POST /api/mobile/support-requests/{id}/messages

Request body

{
	"body": "Here is more detail about the issue."
}

Frontend notes:

  • allow reply UI when status is open, in_progress, or resolved
  • disable reply UI when status is closed
  • render messages in chronological order
  • a mobile reply on a resolved request reopens it back to open

Common Error Scenarios

  • 400: invalid numeric path param
  • 401: missing or invalid JWT
  • 404: support request not found or not owned by the current mobile user
  • 422: invalid category/status/body validation
  • 400: mobile user reply attempted on a closed support request