Skip to content

Company & tickets

GET /company returns the company the API key belongs to:

  • name and legal_name, and the registration_number for its country (SIREN in France, CRN in the UK, EIN in the US).
  • country of the head office and its currency: use that currency for catalog pricing and carts.
  • acquisition_mode: LEASING or BUY, the mode carts are priced in. See Carts & orders.
  • hrms_integration: the connected HR software, or null.

Tickets are support requests to Fleet.

  • GET /tickets lists the company’s tickets, newest first. Filter with status (WAITING_CLIENT means Fleet is waiting for your answer), requester_id, category, or reference.
  • GET /tickets/:ticket_id returns one ticket with its messages, the replies after the opening request, oldest first. from_fleet is true for Fleet support’s replies; content_type html_body means the content is HTML.
  • POST /tickets opens one and requires WRITE. Send the requester_id (an employee or admin Fleet support answers), a subject, the content, and optionally a category and the order_id or device_id it is about.
  • PATCH /tickets/:ticket_id with status: "SOLVED" closes a ticket and requires WRITE.
  • POST /tickets/:ticket_id/messages replies and requires WRITE. Send the author_id (an employee or admin of the company) and the content. The ticket moves to WAITING_FLEET, reopening it if it was solved.

The response’s reference is the one Fleet support quotes in its replies.

TICKET_CREATION_FAILED (502) means Fleet support could not receive the ticket and nothing was created: retry later. TICKET_SYNC_FAILED (502) means Fleet support could not receive the close or the reply and nothing changed: retry later. A reply to a ticket whose reference starts with hub- gets it too, until Fleet support has received the ticket.

  • API reference — Company and Tickets tags.