Fake helpdesk customers API

300 customers from the Helpdesk API, a fake helpdesk API. Companies with a support contract.

Reads with filters, sorting, search and relations; writes that answer like a real server and stay in your session token. Same ids on every build. Free, no key, CORS open.

Connect

List: https://api.sondahub.com/v1/helpdesk/customers
One record: https://api.sondahub.com/v1/helpdesk/customers/{id}
OpenAPI 3: https://api.sondahub.com/v1/helpdesk/openapi.json
GraphQL: https://api.sondahub.com/v1/helpdesk/graphql
JSON file: https://api.sondahub.com/data/helpdesk/customers.json
MCP: https://api.sondahub.com/mcp · list_records

The first three customers

curl "https://api.sondahub.com/v1/helpdesk/customers?limit=3"

Sample records

Records 1 to 3 of 300, exactly as GET /v1/helpdesk/customers/{id} answers them. The data file holds all of them.

[
  {
    "id": 1,
    "created_at": "2024-11-13T20:34:04Z",
    "updated_at": "2024-11-13T20:34:04Z",
    "name": "Golden Trading LLC",
    "domain": "goldentradingl.example",
    "plan": "starter",
    "contact_name": "Oscar Tanaka",
    "contact_email": "[email protected]",
    "sla_hours": 24,
    "open_tickets": 2,
    "satisfaction": null
  },
  {
    "id": 2,
    "created_at": "2025-11-30T17:36:36Z",
    "updated_at": "2025-11-30T17:36:36Z",
    "name": "Summit Holdings Co.",
    "domain": "summitholdings.example",
    "plan": "starter",
    "contact_name": "Ines Romero",
    "contact_email": "[email protected]",
    "sla_hours": 24,
    "open_tickets": 0,
    "satisfaction": 3
  },
  {
    "id": 3,
    "created_at": "2025-04-10T07:21:02Z",
    "updated_at": "2025-04-10T07:21:02Z",
    "name": "Bright Labs LLC",
    "domain": "brightlabsllc.example",
    "plan": "business",
    "contact_name": "Youssef Ali",
    "contact_email": "[email protected]",
    "sla_hours": 4,
    "open_tickets": 0,
    "satisfaction": 3.3
  }
]

Fields

Field	Type	Notes
`id`read-only	int	Assigned by the server. Seed records keep their ids across restarts; records you create continue after the seed.
`created_at`read-only	datetime	When the record was created (ISO 8601, UTC).
`updated_at`read-only	datetime	When the record last changed.
`name`required	string
`domain`	string
`plan`	enum	`free` `starter` `business` `enterprise`
`contact_name`	string
`contact_email`	string
`sla_hours`	int	First response target, hours.
`open_tickets`read-only	int
`satisfaction`read-only	float	Average CSAT, 1–5.

Relations: tickets → the tickets whose customer_id is this customer. Use ?expand=tickets to embed them, or the nested routes.

Endpoints

GET/v1/helpdesk/customersA page, with every filter, sort, search, field and expand option.

POST/v1/helpdesk/customersCreate one: 201 with the record, its id, a Location header and the session token that keeps it; 422 names each field that is wrong.

GET/v1/helpdesk/customers/{id}One record, with an ETag; If-None-Match earns a 304.

PATCH/v1/helpdesk/customers/{id}Change the fields you send.

PUT/v1/helpdesk/customers/{id}Replace the record; required fields must all be there.

DELETE/v1/helpdesk/customers/{id}Answers 200 with what was removed (a real server’s 204 lives at /v1/utils/status/204); gone for the session.

GET/v1/helpdesk/customers/{id}/ticketsIts tickets, as a page with all the list options.

Try it

List with a filter

curl "https://api.sondahub.com/v1/helpdesk/customers?plan=starter&sla_hours_gte=1&limit=3"

One record

curl https://api.sondahub.com/v1/helpdesk/customers/1

Its tickets

curl "https://api.sondahub.com/v1/helpdesk/customers/1/tickets?limit=5"

Create

curl -i -X POST https://api.sondahub.com/v1/helpdesk/customers \
  -H "Content-Type: application/json" \
  -d '{"name":"Blue Systems Inc.","domain":"bluesystems.example","plan":"free"}'

Read it back: newest first (send the session token)

curl "https://api.sondahub.com/v1/helpdesk/customers?sort=-id&limit=3" \
  -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"

Change one field

curl -X PATCH https://api.sondahub.com/v1/helpdesk/customers/1 \
  -H "Content-Type: application/json" \
  -d '{"plan":"starter"}'

Delete the one you created

curl -X DELETE https://api.sondahub.com/v1/helpdesk/customers/301 \
  -H "X-Sondahub-Session: THE_TOKEN_FROM_THE_CREATE"

Query recipes

Every list option works on customers; these are ready to paste. All the options.

What	Request
Page 2, 50 at a time (of 300)	/v1/helpdesk/customers?page=2&limit=50
Only plan = free	/v1/helpdesk/customers?plan=free
Sla hours between two values, largest first	/v1/helpdesk/customers?sla_hours_gte=1&sla_hours_lte=500&sort=-sla_hours
Newest first by created at	/v1/helpdesk/customers?sort=-created_at&limit=5
Name contains “golden”	/v1/helpdesk/customers?name_like=golden
Full-text search	/v1/helpdesk/customers?q=golden
Only some fields	/v1/helpdesk/customers?fields=id,name&limit=5
Its tickets (nested route)	/v1/helpdesk/customers/1/tickets?limit=5
Just the count	/v1/helpdesk/customers?limit=1&fields=id

GraphQL

The same customers as the customers query on https://api.sondahub.com/v1/helpdesk/graphql, and one customer as customer(id: 1). Introspection is on. More on the GraphQL API.

{
  customers(limit: 3, sort: "-id", filter: { plan: free }) {
    total
    data {
      id name domain plan
      tickets(limit: 2) { id }
    }
  }
}

Run it

curl https://api.sondahub.com/v1/helpdesk/graphql -H "Content-Type: application/json" -d '{"query": "{ customers(limit: 3, sort: \"-id\", filter: { plan: free }) { total data { id name domain plan tickets(limit: 2) { id } } } }"}'

From an AI agent (MCP)

The MCP server reaches the same rows with list_records, get_record, create_record, update_record and delete_record, and as the resource sondahub://helpdesk/customers.

tools/call

curl https://api.sondahub.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_records","arguments":{"api":"helpdesk","collection":"customers","filters":{"plan":"free"},"limit":3}}}'

More in the Helpdesk API

teams (4) · agents (25) · tickets (2,000) · messages (5,069)

The live streams, and the whole API on one page: Helpdesk API. Other worlds: fake e-commerce API, fake IoT API, fake banking API, fake social media API, fake flight booking API, fake user directory API.