RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developers.intercom.com/docs/references/rest-api/api.intercom.io/ticket-types below:

Intercom API (2.14) Copy Copy for LLM Copy page as Markdown for LLMs View as Markdown Open this page as Markdown Open in ChatGPT Get insights from ChatGPT Open in Claude Get insights from Claude

Intercom API (2.14)

The intercom API reference.

The production API server The european API server

https://api.eu.intercom.io/

The australian API server

https://api.au.intercom.io/

Admins

Everything about your Admins

AI Content

With the AI Content APIs, you can create and manage External Pages and Content Import Sources for your Fin Content Library.

External Pages are pages that you want Fin to be able to answer questions about. The API for External Pages is a great way to ingest into your Fin Content Library pages that are not publicly accessible and hence can't be crawled by Intercom.

Content Import Sources are the sources of those pages, and they are used to determine the default audience for the pages (configured via the UI). You should create a Content Import Source for each source of External Pages that you want to ingest into your Fin Content Library.

You can then iterate through the content from that source via its API and POST it to the External Pages endpoint. That endpoint has an external_id parameter which allows you to specify the identifier from the source. The endpoint will then either create a new External Page or update an existing one as appropriate.",

Articles

Everything about your Articles

Away Status Reasons

Everything about your Away Status Reasons

Companies

Everything about your Companies

Conversations

Everything about your Conversations

Custom Channel Events

With the "Custom Channel" integration, you can bring Fin and Intercom capabilities to your own platform via API, enabling powerful custom integrations.

Intercom treats your integration like any other Intercom channel, allowing your application and Intercom to exchange events seamlessly. This makes it possible, for example, for your users to interact with Fin directly within your own application’s UI.

Note: "Fin over API" is currently under managed availability. Please reach out to your accounts team to discuss access and tailored, hands-on support.

Custom Object Instances

Everything about your Custom Object instances.

Permission Requirements

From now on, to access this endpoint, you need additional permissions. Please head over to the Developer Hub app package authentication settings to configure the required permissions.

Data Attributes

Everything about your Data Attributes

Data Events

Everything about your Data Events

Data Export

Everything about your Data Exports

Help Center

Everything about your Help Center

Internal Articles

Everything about your Internal Articles

Messages

Everything about your messages

News

Everything about your News

Notes

Everything about your Notes

Reporting Data Export

Everything about Reporting Data Export

Segments

Everything about your Segments

Subscription Types

Everything about subscription types

Teams

Everything about your Teams

Ticket States

Everything about your ticket states

Ticket Type Attributes

Everything about your ticket type attributes

Ticket Types

Everything about your ticket types

Request

You can get a list of all ticket types for a workspace.

Headers Intercom-Versionstring(intercom_version)

Intercom API version.
By default, it's equal to the version set in the app package.

Default 2.14

Enum"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"

Example: 2.14

curl -i -X GET \
  https://api.intercom.io/ticket_types \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Intercom-Version: 2.14'

Bodyapplication/json

String representing the object's type. Always has the value list.

Example: "list"

dataArray of objects or null(Ticket Type)

A list of ticket_types associated with a given workspace.

{
  "type": "list",
  "data": [
    { … }
  ]
}

Request

You can create a new ticket type.

📘 Creating ticket types.

Every ticket type will be created with two default attributes: default_title and default_description. For the icon propery, use an emoji from Twemoji Cheatsheet

Headers Intercom-Versionstring(intercom_version)

Intercom API version.
By default, it's equal to the version set in the app package.

Default 2.14

Enum"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"

Example: 2.14

Bodyapplication/json

The name of the ticket type.

Example: "Bug"

The description of the ticket type.

Example: "Used for tracking bugs"

Category of the Ticket Type.

Enum"Customer""Back-office""Tracker"

Example: "Customer"

The icon of the ticket type.

Default "🎟️"

Example: "🐞"

Whether the tickets associated with this ticket type are intended for internal use only or will be shared with customers. This is currently a limited attribute.

Default false

Example: false

curl -i -X POST \
  https://api.intercom.io/ticket_types \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'Intercom-Version: 2.14' \
  -d '{
    "name": "Customer Issue",
    "description": "Customer Report Template",
    "icon": "🎟️",
    "category": "Customer"
  }'

Bodyapplication/json

String representing the object's type. Always has the value ticket_type.

Example: "ticket_type"

The id representing the ticket type.

Example: "1295"

Category of the Ticket Type.

Enum"Customer""Back-office""Tracker"

Example: "Customer"

The name of the ticket type

Example: "Bug"

The description of the ticket type

Example: "A bug that has been reported."

The icon of the ticket type

Example: "🐞"

The id of the workspace that the ticket type belongs to.

Example: "ecahpwf5"

ticket_type_attributesobject(Ticket Type Attributes)

A list of attributes associated with a given ticket type.

ticket_statesobject(Ticket States)

A list of ticket states associated with a given ticket type.

Whether the ticket type is archived or not.

Example: false

created_atinteger(timestamp)

The date and time the ticket type was created.

updated_atinteger(timestamp)

The date and time the ticket type was last updated.

{ "type": "ticket_type", "id": "70", "name": "Customer Issue", "description": "Customer Report Template", "icon": "🎟️", "workspace_id": "this_is_an_id652_that_should_be_at_least_", "archived": false, "created_at": 1734537869, "updated_at": 1734537869, "is_internal": false, "ticket_type_attributes": { "type": "list", "data": [ … ] }, "category": "Customer", "ticket_states": { "type": "list", "data": [ … ] } }

Request

You can fetch the details of a single ticket type.

Path

The unique identifier for the ticket type which is given by Intercom.

Headers Intercom-Versionstring(intercom_version)

Intercom API version.
By default, it's equal to the version set in the app package.

Default 2.14

Enum"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"

Example: 2.14

curl -i -X GET \
  'https://api.intercom.io/ticket_types/{id}' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Intercom-Version: 2.14'

Bodyapplication/json

String representing the object's type. Always has the value ticket_type.

Example: "ticket_type"

The id representing the ticket type.

Example: "1295"

Category of the Ticket Type.

Enum"Customer""Back-office""Tracker"

Example: "Customer"

The name of the ticket type

Example: "Bug"

The description of the ticket type

Example: "A bug that has been reported."

The icon of the ticket type

Example: "🐞"

The id of the workspace that the ticket type belongs to.

Example: "ecahpwf5"

ticket_type_attributesobject(Ticket Type Attributes)

A list of attributes associated with a given ticket type.

ticket_statesobject(Ticket States)

A list of ticket states associated with a given ticket type.

Whether the ticket type is archived or not.

Example: false

created_atinteger(timestamp)

The date and time the ticket type was created.

updated_atinteger(timestamp)

The date and time the ticket type was last updated.

{ "type": "ticket_type", "id": "72", "name": "Bug Report", "description": "Bug Report Template", "icon": "🎟️", "workspace_id": "this_is_an_id656_that_should_be_at_least_", "archived": false, "created_at": 1734537870, "updated_at": 1734537870, "is_internal": false, "ticket_type_attributes": { "type": "list", "data": [ … ] }, "category": "Customer", "ticket_states": { "type": "list", "data": [ … ] } }

Request

You can update a ticket type.

📘 Updating a ticket type.

For the icon propery, use an emoji from Twemoji Cheatsheet

Path

The unique identifier for the ticket type which is given by Intercom.

Headers Intercom-Versionstring(intercom_version)

Intercom API version.
By default, it's equal to the version set in the app package.

Default 2.14

Enum"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"

Example: 2.14

Bodyapplication/json

The name of the ticket type.

Example: "Bug"

The description of the ticket type.

Example: "A bug has been occured"

Category of the Ticket Type.

Enum"Customer""Back-office""Tracker"

Example: "Customer"

The icon of the ticket type.

Default "🎟️"

Example: "🐞"

The archived status of the ticket type.

Example: false

Whether the tickets associated with this ticket type are intended for internal use only or will be shared with customers. This is currently a limited attribute.

Default false

Example: false

curl -i -X PUT \
  'https://api.intercom.io/ticket_types/{id}' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'Intercom-Version: 2.14' \
  -d '{
    "name": "Bug Report 2"
  }'

Bodyapplication/json

String representing the object's type. Always has the value ticket_type.

Example: "ticket_type"

The id representing the ticket type.

Example: "1295"

Category of the Ticket Type.

Enum"Customer""Back-office""Tracker"

Example: "Customer"

The name of the ticket type

Example: "Bug"

The description of the ticket type

Example: "A bug that has been reported."

The icon of the ticket type

Example: "🐞"

The id of the workspace that the ticket type belongs to.

Example: "ecahpwf5"

ticket_type_attributesobject(Ticket Type Attributes)

A list of attributes associated with a given ticket type.

ticket_statesobject(Ticket States)

A list of ticket states associated with a given ticket type.

Whether the ticket type is archived or not.

Example: false

created_atinteger(timestamp)

The date and time the ticket type was created.

updated_atinteger(timestamp)

The date and time the ticket type was last updated.

{ "type": "ticket_type", "id": "74", "name": "Bug Report 2", "description": "Bug Report Template", "icon": "🎟️", "workspace_id": "this_is_an_id660_that_should_be_at_least_", "archived": false, "created_at": 1734537873, "updated_at": 1734537874, "is_internal": false, "ticket_type_attributes": { "type": "list", "data": [ … ] }, "category": "Customer", "ticket_states": { "type": "list", "data": [ … ] } }

Tickets

Everything about your tickets

Visitors

Everything about your Visitors

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4