Home
/
REST API Reference
/
Models
/
Ticket States

Intercom API (2.12)

The Intercom API reference.

Download OpenAPI description
api.intercom.io.json
api.intercom.io.yaml
Overview
URL https://developers.intercom.com
License MIT
Languages
Servers
The production API server
https://api.intercom.io/
The european API server
https://api.eu.intercom.io/
The australian API server
https://api.au.intercom.io/

Admins

Everything about your Admins

Operations

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.",

Operations

Articles

Everything about your Articles

Operations

Companies

Everything about your Companies

Operations

Contacts

Everything about your contacts

Operations

Conversations

Everything about your Conversations

Operations

Data Attributes

Everything about your Data Attributes

Operations

Data Events

Everything about your Data Events

Operations

Data Export

Everything about your Data Exports

Operations

Help Center

Everything about your Help Center

Operations

Messages

Everything about your messages

Operations

News

Everything about your News

Operations

Notes

Everything about your Notes

Operations

Segments

Everything about your Segments

Operations

Subscription Types

Everything about subscription types

Operations

Switch

Everything about Switch

Operations

Tags

Everything about tags

Operations

Teams

Everything about your Teams

Operations

Ticket States

Everything about your ticket states

Operations

Ticket Type Attributes

Everything about your ticket type attributes

Operations

Ticket Types

Everything about your ticket types

Operations

Tickets

Everything about your tickets

Operations

Visitors

Everything about your Visitors

Operations

Models

Ticket Attributes

The attributes set on the ticket. When setting the default title and description attributes, the attribute keys that should be used are _default_title_ and _default_description_. When setting ticket type attributes of the list attribute type, the key should be the attribute name and the value of the attribute should be the list item id, obtainable by listing the ticket type. For example, if the ticket type has an attribute called priority of type list, the key should be priority and the value of the attribute should be the guid of the list item (e.g. de1825a0-0164-4070-8ca6-13e22462fa7e).

property name*(string or null) or number or boolean or Array of arraysadditional property
Any of:
string or null
{
  "_default_title_": "Found a bug",
  "_default_description_": "The button is not working"
}

Ticket States

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

typestring

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

Example: "list"
dataArray of objects or null(Ticket State)

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

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

Ticket Type Attribute

Ticket type attribute, used to define each data field to be captured in a ticket.

typestring

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

Example: "ticket_type_attribute"
idstring

The id representing the ticket type attribute.

Example: "1"
workspace_idstring

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

Example: "ecahpwf5"
namestring

The name of the ticket type attribute

Example: "Title"
descriptionstring

The description of the ticket type attribute

Example: "Bug title."
data_typestring

The type of the data attribute (allowed values: "string list integer decimal boolean datetime files")

Example: "string"
input_optionsobject

Input options for the attribute

Example: "multiline: true"
orderinteger

The order of the attribute against other attributes

Example: 1
required_to_createboolean

Whether the attribute is required or not for teammates.

Default false
Example: false
required_to_create_for_contactsboolean

Whether the attribute is required or not for contacts.

Default false
Example: false
visible_on_createboolean

Whether the attribute is visible or not to teammates.

Default true
Example: false
visible_to_contactsboolean

Whether the attribute is visible or not to contacts.

Default true
Example: false
defaultboolean

Whether the attribute is built in or not.

Example: true
ticket_type_idinteger

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

Example: 42
archivedboolean

Whether the ticket type attribute is archived or not.

Example: false
created_atinteger(timestamp)

The date and time the ticket type attribute was created.

updated_atinteger(timestamp)

The date and time the ticket type attribute was last updated.

{
  "type": "ticket_type_attribute",
  "id": "1",
  "workspace_id": "ecahpwf5",
  "name": "Title",
  "description": "Bug title.",
  "data_type": "string",
  "input_options": "multiline: true",
  "order": 1,
  "required_to_create": false,
  "required_to_create_for_contacts": false,
  "visible_on_create": false,
  "visible_to_contacts": false,
  "default": true,
  "ticket_type_id": 42,
  "archived": false,
  "created_at": 0,
  "updated_at": 0
}