The intercom API reference.
Home//
REST API Reference
/- Open Conversation Request
Activity Log
Paginated Response
Activity Log Metadata
Addressable List
Admins
Admin Priority Level
Admin Reply
Admin Reply on ticket
Admin
App
Article Content
Articles
Article Statistics
Article Translated Content
Assign Conversation Request
Assign Conversation Request
Close Conversation Request
Collections
Company Attached Contacts
Company Attached Segments
Companies
Company Scroll
Contact Archived
Contact Attached Companies
Contact companies
Company Data
Contact Deleted
Contact List
Contact Location
Contact notes
Contact Reference
Contact Reply Base Object
Contact Reply
Email
Intercom User ID
Email
Intercom User ID
Contact Reply on ticket
User ID
User ID
Segments
Social Profile
Contact Subscription Types
Contact Tags
Contact Unarchived
Conversation attachment files
Contacts
First contact reply
Conversation List
Conversation Part
Conversation part author
Conversation Parts
Conversation Rating
Conversation source
Conversation statistics
Conversation teammates
Convert Ticket Request Payload
Convert Visitor Request Payload
Create Article Request Payload
Create Collection Request Payload
Create Contact Request Payload
Create Conversation Request Payload
Create Data Attribute Request
Create Data Event Request
Create Data Event Summaries Request
Create Data Export Request
Create Message Request Payload
Create Or Update Company Request Payload
Create or Update Tag Request Payload
Create Phone Switch Request Payload
Create Ticket Reply Request Payload
Create Ticket Request Payload
Create Ticket Type Attribute Request Payload
Create Ticket Type Request Payload
Cursor based pages
Custom Attributes
customer_request
Data Attribute List
Data Event List
Data Event Summary
Data Event Summary Item
Data Export CSV
Deleted Article Object
Deleted Collection Object
Deleted Company Object
Deleted Object
detach_contact_from_conversation_request
Error
File
Group Content
Group Translated Content
intercom_version
Linked Object
Linked Objects
Merge contact data
Multiple Filter Search Request
Create News Item Request
Paginated Response
Pagination Object
Paginated Response
Part attachment
Phone Switch
redact_conversation_request
Reference
reply_conversation_request
Search data
Segment List
Single Filter Search Request
Applied SLA
Snooze Conversation Request
Social Profile
Pagination: Starting After
Subscription Types
Tag Company Request Payload
Tags
Tag Users Request Payload
Tags
Team List
Team Priority Level
Ticket Attributes
Ticket List
Ticket part author
Ticket Parts
A Ticket Part representing a note, comment, or quick_reply on a ticket
Ticket Attributes
Ticket Type Attribute
Ticket Type Attributes
Ticket Types
Translation
Untag Company Request Payload
Update Article Request Payload
Update Collection Request Payload
Update Contact Request Payload
Update Conversation Request
Update Data Attribute Request
Update Ticket Request Payload
Update Ticket Type Attribute Request Payload
Update Ticket Type Request Payload
Update Visitor Request Payload
Visitor
Visitor Deleted Object
Open Conversation Request
Intercom API (2.10)
Download OpenAPI description
Overview
URL
License
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/
Paginated Response
A paginated list of notes associated with a contact.
Cursor-based pagination is a technique used in the Intercom API to navigate through large amounts of data. A "cursor" or pointer is used to keep track of the current position in the result set, allowing the API to return the data in small chunks or "pages" as needed.
{ "type": "list", "data": [ { … } ], "total_count": 1, "pages": { "type": "pages", "page": 1, "next": { … }, "per_page": 2, "total_pages": 13 } }
Pagination Object
The majority of list resources in the API are paginated to allow clients to traverse data over multiple requests.
Their responses are likely to contain a pages object that hosts pagination links which a client can use to paginate through the data without having to construct a query. The link relations for the pages field are as follows.
A link to the next page of results. A response that does not contain a next link does not have further data to fetch.
{ "type": "pages", "page": 1, "next": "http://example.com", "per_page": 50, "total_pages": 1 }