Groove Tickets API

The Tickets API from Groove — 4 operation(s) for tickets.

Operations 5

GET /tickets List tickets #
POST /tickets Create a ticket #
GET /tickets/{number} Find a ticket #
PUT /tickets/{number}/state Update ticket state #
PUT /tickets/{number}/assignee Update ticket assignee #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/groove-tickets-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

groove-tickets-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Groove REST API v1 Agents Tickets API
  description: 'The Groove REST API v1 provides programmatic access to Groove help-desk

    resources including tickets, messages, customers, agents, groups,

    mailboxes, folders, attachments, webhooks, knowledge bases, and widgets.

    Note: v1 REST is no longer in active development; Groove recommends the

    new GraphQL API for richer features.

    '
  version: '1.0'
  contact:
    name: Groove Developers
    url: https://developer.groovehq.com
servers:
- url: https://api.groovehq.com/v1
  description: Groove REST API base URL
security:
- bearerAuth: []
- accessTokenQuery: []
tags:
- name: Tickets
paths:
  /tickets:
    get:
      summary: List tickets
      operationId: listTickets
      responses:
        '200':
          description: A list of tickets.
      tags:
      - Tickets
    post:
      summary: Create a ticket
      operationId: createTicket
      responses:
        '201':
          description: The created ticket.
      tags:
      - Tickets
  /tickets/{number}:
    parameters:
    - in: path
      name: number
      required: true
      schema:
        type: string
    get:
      summary: Find a ticket
      operationId: findTicket
      responses:
        '200':
          description: The requested ticket.
      tags:
      - Tickets
  /tickets/{number}/state:
    parameters:
    - in: path
      name: number
      required: true
      schema:
        type: string
    put:
      summary: Update ticket state
      operationId: updateTicketState
      responses:
        '200':
          description: The updated ticket.
      tags:
      - Tickets
  /tickets/{number}/assignee:
    parameters:
    - in: path
      name: number
      required: true
      schema:
        type: string
    put:
      summary: Update ticket assignee
      operationId: updateTicketAssignee
      responses:
        '200':
          description: The updated ticket.
      tags:
      - Tickets
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: OAuth 2.0 / personal access token via Authorization header.
    accessTokenQuery:
      type: apiKey
      in: query
      name: access_token
      description: Access token passed as a URL query parameter.