gnt.ai Intercom API

The intercom API from gnt.ai — 2 operation(s) for intercom.

GitHub OpenAPI

Operations 4

GET /v1/settings/intercom Get Intercom Connection #
POST /v1/settings/intercom Connect Intercom #
DELETE /v1/settings/intercom Disconnect Intercom #
GET /v1/settings/intercom/sync-status Intercom Sync Status #

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/gntai-dev:gntai-dev-intercom-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

gntai-dev-intercom-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: AI GNT Intercom API
  version: 0.1.0
servers:
- url: https://api.gntai.dev
  description: Production
tags:
- name: intercom
paths:
  /v1/settings/intercom:
    get:
      tags:
      - intercom
      summary: Get Intercom Connection
      operationId: get_intercom_connection_v1_settings_intercom_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      security:
      - HTTPBearer: []
    post:
      tags:
      - intercom
      summary: Connect Intercom
      description: 'Live-validates the access token with one real read

        (verify_credentials) before anything is persisted -- same discipline

        routers/zendesk.py''s connect_zendesk applies to its own token via

        verify_credentials, so a typo''d or revoked token fails immediately

        with a clear error instead of silently saving a connection the

        nightly sync will only discover is broken hours later. Unlike

        connect_zendesk, there''s no subdomain/agent_email to collect --

        Intercom''s access token alone identifies the workspace (see

        gnt/intercom/client.py''s module docstring).'
      operationId: connect_intercom_v1_settings_intercom_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ConnectIntercomRequest'
        required: true
      responses:
        '201':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
      - HTTPBearer: []
    delete:
      tags:
      - intercom
      summary: Disconnect Intercom
      operationId: disconnect_intercom_v1_settings_intercom_delete
      responses:
        '204':
          description: Successful Response
      security:
      - HTTPBearer: []
  /v1/settings/intercom/sync-status:
    get:
      tags:
      - intercom
      summary: Intercom Sync Status
      description: 'Sync-status health surface -- last

        successful sync, last error, and this run''s item/candidate counts.

        Same role as routers/zendesk.py''s own /sync-status endpoint -- a

        plain GET a future `gnt status` addition or the web dashboard can

        poll rather than anything pushed. Returns the same "never synced yet"

        zero-value shape regardless of whether Intercom is even connected --

        callers that care should check GET /v1/settings/intercom''s

        `connected` field first.'
      operationId: intercom_sync_status_v1_settings_intercom_sync_status_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      security:
      - HTTPBearer: []
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ConnectIntercomRequest:
      properties:
        access_token:
          type: string
          format: password
          title: Access Token
          writeOnly: true
      type: object
      required:
      - access_token
      title: ConnectIntercomRequest
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer