Skip to main content

Tickets API

Feature Request

Could we please have Tickets exposed in the API too, including creation.

Heaps of integrations / automations I’d love to create with this, but crucially this would allow us to generate tickets form 3rd party platforms (webhooks!), and ‘import’ tickets from other PSAs if desired.

It’s unlimited fun, let’s do this!

Status: Completed22 comments

Log in to comment and vote

Comments22

  • Mikel from Gorelo

    Team

    ✨ API - A new POST Ticket endpoint is now available

  • Purple Fries

    Ticket Migration API Gaps

    I’m migrating from Syncro MSP to Gorelo and have built tooling against the public API. Client/contact migration works great. For tickets, here's what I'd need:

    Endpoint NeededExists?What We Need It For

    POST /v1/tickets

    ✅ Yes

    Create tickets

    POST /v1/tickets/{id}/comments

    ❌ No

    Import ticket replies, internal notes, history

    POST /v1/tickets/{id}/attachments

    ❌ No

    Import files attached to tickets

    POST /v1/tickets/{id}/timeEntries

    ❌ No

    Import billable time entries

    PATCH /v1/tickets/{id}

    ❌ No

    Update ticket status/fields after creation

    GET /v1/tickets or GET /v1/tickets/{id}

    ❌ No

    Read back / verify imported tickets

    createdAt override on POST /v1/tickets

    ❌ No

    Preserve original ticket dates (not import date)

    The comments endpoint is the biggest blocker — without it, we can create ticket shells but lose all conversation history. The timestamp override is second — without it, every migrated ticket looks like it was created today.

    Happy to help test/validate any of these if they're on the roadmap.

    • Tan Duck

      Yep, second this - would be great if they could get this working, its the only thing stopping us moving over now.

    • Tan Duck

      @Mikel from Gorelo any update on this?

      • Tan Duck

        @Mikel from Gorelo - Any further update on this? - ticket devolopment seems to have dropped off?

        • Mikel from Gorelo

          Team

          A few key team members working on the AU migration will move back to the API once they're finished with their part in the coming weeks :)

  • Mikel from Gorelo

    Team

    Yep, we’re working towards this :)

    • Coffee Moss

      I saw the comment on the API so far release and don’t mean to pile on, couldn’t find an API ticket anywhere so thought I’d add it so it can be tracked separately.


      Keep up the fantastic work Mikel and team 🙏

  • Black Robin

    This would be fantastic. Especially if we could have webhooks from other platforms generate tickets automatically.

  • Purple Pumpkin

    🤞 hoping this will provide way to get / set time entries from tickets.

    • Emerald Sprout

      @Mikel from Gorelo , any update on this ? Is this part of the plan?

      • Mikel from Gorelo

        Team

        Yes to both get/post time entries

  • Mikel from Gorelo

    Team

    ✨ API - GET Ticket Statuses is now available (in preparation for Tickets)

    ✨ API - GET Ticket Tags is now available (in preparation for Tickets)

    ✨ API - GET Ticket Types is now available (in preparation for Tickets)

    • Coffee Moss

      😍

  • Mikel from Gorelo

    Team

    ✨ API - The GET Groups endpoint is now available (in preparation for Tickets)

    ✨ API - The GET Users endpoint is now available (in preparation for Tickets)

  • Mikel from Gorelo

    Team

    ✨ API - Ticket comments are now available in the public API. List and read comments, list conversations, create comments, and upload attachments

    ✨ API - GET /v1/tickets now supports query parameters: StatusIds, ClientIds, UpdatedSince, Keyword and more

  • Aqua Iguana

    I’m looking to build an MCP or CLI for AI Agents to use on top of the APIs. I’ve made some progress, but there’s not quite enough functionality to make it usable yet.

  • Mikel from Gorelo

    Team

    ✨ API - New DELETE endpoints for agent assets, custom assets, clients, contacts, tickets, and private comments. Blocked deletes return a 409 naming what's in the way, with guidance on how to clear it

    ✨ API - GET /v1/tickets now includes ChecklistSummary

    ✨ API - GET /v1/tickets/{id} has been introduced and returns a fuller ticket than the list: description, time and billing breakdown (actual vs adjusted hours, split by billable / not billable), products, shipments, linked assets, banner etc.