Home
/
REST API Reference
/
Models
/
Create Data Export Request

Intercom API (2.9)

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

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 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

Create Data Event Summaries Request

You can send a list of event summaries for a user. Each event summary should contain the event name, the time the event occurred, and the number of times the event occurred. The event name should be a past tense "verb-noun" combination, to improve readability, for example updated-plan.

user_idstring

Your identifier for the user.

Example: "314159"
event_summariesobject

A list of event summaries for the user. Each event summary should contain the event name, the time the event occurred, and the number of times the event occurred. The event name should be a past tense 'verb-noun' combination, to improve readability, for example updated-plan.

{
  "user_id": "314159",
  "event_summaries": {
    "event_name": "invited-friend",
    "count": 1,
    "first": 1671028894,
    "last": 1671028894
  }
}

Create Data Export Request

Request for creating a data export

created_at_afterintegerrequired

The start date that you request data for. It must be formatted as a unix timestamp.

Example: 1527811200
created_at_beforeintegerrequired

The end date that you request data for. It must be formatted as a unix timestamp.

Example: 1527811200
{
  "created_at_after": 1527811200,
  "created_at_before": 1527811200
}

Create Message Request Payload

You can create a message

Any of:

You can create a message

message_typestringrequired

The kind of message being created. Values: in_app or email.

Enum"in_app""email"
Example: "in_app"
subjectstringrequired

The title of the email.

Example: "Thanks for everything"
bodystringrequired

The content of the message. HTML and plaintext are supported.

Example: "Hello there"
templatestringrequired

The style of the outgoing message. Possible values plain or personal.

Example: "plain"
fromobjectrequired

The sender of the message. If not provided, the default sender will be used.

from.​typestringrequired

Always admin.

Value"admin"
Example: "admin"
from.​idintegerrequired

The identifier for the admin which is given by Intercom.

Example: 394051
toobjectrequired

The sender of the message. If not provided, the default sender will be used.

to.​typestringrequired

The role associated to the contact - user or lead.

Enum"user""lead"
Example: "user"
to.​idstringrequired

The identifier for the contact which is given by Intercom.

Example: "536e564f316c83104c000020"
create_conversation_without_contact_replyboolean

Whether a conversation should be opened in the inbox for the message without the contact replying. Defaults to false if not provided.

Default false
Example: true
{
  "message_type": "in_app",
  "subject": "Thanks for everything",
  "body": "Hello there",
  "template": "plain",
  "from": {
    "type": "admin",
    "id": 394051
  },
  "to": {
    "type": "user",
    "id": "536e564f316c83104c000020"
  },
  "create_conversation_without_contact_reply": true
}