tickets

Support ticket or issue tracking record with customer information, assignee, priority, status, category, and resolution timestamps. Used for customer support systems, help desks, and issue tracking platforms.

🎯 Request Builder

https://api.mockly.codes/tickets?page=1&limit=10&count=10
📡

Configure your request and click Send Request to see the response here.

Endpoints

GET/tickets

Get a collection of tickets

Alternative: /productivity/tickets
GET/tickets/:id

Get a single ticket by ID

Alternative: /productivity/tickets/:id
GET/tickets/meta

Get resource metadata and schema

Alternative: /productivity/tickets/meta
🔍

How to Use Search

The search feature allows you to filter results by searching for text across all or specific fields. Choose between ?q= or ?search= parameter names.

1. Basic Search

Search across all text fields:

Basic Search
GET https://api.mockly.codes/tickets?q=laptop

2. Search Specific Fields

Field-Specific Search
GET https://api.mockly.codes/tickets?q=laptop&search_fields=name,description

💡 Pro Tips

  • Search is case-insensitive and performs partial matching
  • Without search_fields, all text fields are searched
  • Combine with pagination to handle large result sets efficiently

Code Examples

JavaScript

Fetch Collection
// Get 10 tickets
fetch('https://api.mockly.codes/tickets?count=10')
  .then(res => res.json())
  .then(data => console.log(data));

Python

Fetch with Requests
import requests

response = requests.get(
    'https://api.mockly.codes/tickets?count=10'
)
data = response.json()

cURL

Command Line
curl "https://api.mockly.codes/tickets?count=10"

Bypass Cache

Get Fresh Data
fetch('https://api.mockly.codes/tickets?nocache=true')

Schema Properties

idinteger

Unique identifier for the ticket

Gen:random_int
ticket_numberstring

Unique ticket reference number for customer tracking

Gen:ticket_number
subjectstring

Ticket subject or summary

Gen:sentence
descriptionstring

Detailed description of the issue or request

Gen:paragraph
customer_idinteger

Foreign key reference to the customer who created the ticket

Gen:random_int
customer_namestring

Full name of the customer

Gen:name
customer_emailstring

Customer email address for ticket communications

Gen:emailemail
assigned_tostring

Full name of the support agent assigned to handle this ticket

Gen:name
prioritystring

Ticket priority level (e.g., low, medium, high, urgent)

Gen:priority
statusstring

Current ticket status (e.g., open, in_progress, waiting, resolved, closed)

Gen:ticket_status
categorystring

Ticket category (e.g., technical, billing, feature_request, bug)

Gen:ticket_category
created_atstring

Timestamp when the ticket was created

Gen:past_datedate-time
updated_atstring

Timestamp when the ticket was last updated

Gen:past_datedate-time
resolved_atstring

Timestamp when the ticket was resolved, null if still open

Gen:past_datedate-time

Query Parameters

countinteger

Number of items to return (default: 10, max: 100)

seedinteger

Seed for reproducible data generation

nocacheboolean

Bypass cache and generate fresh data on every request