GET /v1/tickets/{ticket_id}/notes

A ticket’s internal notes, oldest first.

A ticket’s internal notes, oldest first: what the team wrote for each other. Notes are never sent to the customer.

Needs the tickets:read scope.

Path parameters

Field	Type	Required	Notes
ticket_id	string	Yes	The ticket’s id.

Request

cURL

curl "https://api.fireflo.au/v1/tickets/b84f2c10-5e7a-4c3d-9a61-0f2d7e9c4a18/notes" \
  -H "Authorization: Bearer $OMNI_API_KEY"

Response

200 OK — every note, in one answer. author is the team member who wrote it, or API · and the key’s name.

{
  "data": [
    {
      "id": 311,
      "body": "Courier says the parcel is at the Andheri hub. Rebooking delivery for tomorrow.",
      "author": "Priya Nair",
      "created_at": "2026-10-06T09:40:11+05:30"
    },
    {
      "id": 318,
      "body": "Refund of ₹1,200 held until delivery is confirmed.",
      "author": "API · Order sync",
      "created_at": "2026-10-06T10:15:03+05:30"
    }
  ]
}

Errors

Every refusal is {"error": {"code", "message", "field"}}; field is there when one input is at fault.

Status	Error code	When
404	not_found	No ticket has that id on this account.
404	module_off	The account’s plan doesn’t include Tickets.
403	scope_missing	The key doesn’t have the tickets:read scope.

Any request can also be refused for its key, its account or its rate (key_required, invalid_key, account_suspended, plan_excludes_api, address_not_allowed, rate_limited); see the overview.