The Tickets API is a proxy to an external service called finper-bot. Tickets represent expense receipts or items that have been captured externally (e.g. photographed via a Telegram bot) and are awaiting review. The API proxies all requests to the bot’s HTTP endpoint — there is no local data model or database table for tickets.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/soker90/finper/llms.txt
Use this file to discover all available pages before exploring further.
GET /api/tickets
Retrieve all tickets pending review from the finper-bot service.PATCH /api/tickets/:id
Mark a ticket as reviewed or update its metadata. The request body is forwarded to finper-bot as-is.Ticket ID as returned by finper-bot.
DELETE /api/tickets/:id
Delete a ticket from finper-bot.Ticket ID as returned by finper-bot.
Tickets have no local data model in Finper. All ticket data lives exclusively in finper-bot. Finper acts only as an authenticated gateway, adding the
token header validation and forwarding the request with the TICKET_BOT_API_KEY.