API &amp; Webhooks

Trying to fetch articles but keep getting CORS

Hello, I am trying to fetch all articles and I keep getting CORS error no matter what I try. I tried to set the headers as mentioned here https://developers.intercom.com/docs/references/rest-api/api.intercom.io/Articles/listArticles/, adding also access allow control origin header but I can’t get the data. I get it in postman with no issue. What am I missing? Working with RTK Query.

4031

Rich HodgkinsConnector

API requests are returning 403

Hi, We’re using v1.4 of the API to query and update users in our (Google) cloud services. However all of a sudden the requests are return a 403 status code with a HTML body - also there are no other usual Intercom response headers (x-request-id, x-ratelimit-limit, etc.) present so I can’t even provide a request ID trace to debug with. <html><head><title>403 Forbidden</title></head><body><center><h1>403 Forbidden</h1></center></body></html> Headers: connection: keep-alivecontent-length: 118content-type: text/htmldate: Thu, 22 Jun 2023 15:54:21 GMTserver: awselb/2.0 It’s not an issue with the authentication or request as if I run curl with the same request it succeeds with a 200 status code. Has Intercom blocked our cloud services (Google Cloud Run) IP or something? A simple request such as the below fails when run in the cloud: curl -i -H 'accept: application/json' -H 'intercom-version: 1.4' -H 'authorization: Bearer <access-token>' 'https://api.intercom.io/users?user_id=X'

40598

Justin PhilbrookNew Participant

Inconsistent results from the API on Tickets

Context: I’m using the Intercom <=> Jira cloud integration to link my Intercom Conversations and Tickets to related Jiras. A limitation with this integration is that it doesn’t write the Jira ID to the Intercom data objects, it writes to a Jira field ‘linked_intercom_conversations.’ This means I can’t search or do any reporting in Intercom for Conversations/Tickets related to Jiras. To solve this, I wrote a tool to pull the Intercom IDs from the Jira fields, and update a data attribute in Intercom with the Jira ID that was linked. Here’s the problem: When the ‘linked_intercom_conversations’ is written to the Jira it always writes the url ID to the field. This means that all of the linked objects look like conversations. Because Intercom doesn’t share data attributes across conversations and ticket types, it takes a different API call to update a ticket vs a conversation. But I can’t tell from the ID on the Jira which type is is. I tried doing a call to api.intercom.io/conversations/CAS

1502

Gary CahillNew Participant

API operator logic is flawed/broken

I am tying to query conversations (via python) and my payload is as follows payload = { "query": { "operator": "AND", "value": [ { "field": "state", "operator": "=", "value": "open" }, { "field": "admin_assignee_id", "operator": "=", "value": "123456" }, { "field": "waiting_since", "operator": "<", "value": 1693564392 } ] }} The above logic should be, show me conversations where state = open AND admin_assignee_id = 123456 AND waiting since is less than 1693564392. The response however includes conversations that have a “state” = “closed” What am I doing wrong ? Your docs state AND operators can have upto 15 filters.

832

Tomer YonaNew Participant

Webhook events - reply on a closed conversation does not trigger the conversation.admin.opened topic

Hi,I am using webhooks and trying to identify an event of ‘conversation.admin.opened’ when a lead replies on a closed ticket but it doesn’t seem to trigger it. the odd thing is that it works on one workspace but not on the other.

1091

ShashwatNew Participant

reply to a ticket on behalf of a contact using Rest API doesn't work

According to the API documentation, something like this should work POST { "message_type": "comment", "type": "user", "body":"<h1>hello world</h1>", "intercom_user_id":"" } but instead I get a "user is an invalid value for type" error - even though the API explicitly says that it is. I do note that the page linked only has an admin note reply as an option in the dropdown. Does that mean that it is not possible to post a reply on behalf of a user? Would appreciate any help here.

932

Peter N12New Participant

Sending data to Custom Objects

Hi, New to IC and have set up a Custom Object. My thinking was first to push data to the Custom object from our Bubble app as soon as the data changes in the Bubble app. However, according to https://www.intercom.com/help/en/articles/6298280-setting-up-a-custom-objectthere's no API yet to use for pushing data from my Bubble app to IC, right? So, I guess I need to create a Custom Action that then can be used in a Bot to in real time retrieve the data need? Best, Peter

6593

AeronNew Participant

First seen field is populated when a creator is populated by API - nullable?

Previously, User contacts were only created in Intercom when they first logged into our platform. Because of this, we could treat the First Seen field as a reliable indicator of the first time a user actually logged in. Knowing the time between “signed_up_at” (i.e. user provisioning) and “First Seen”(i.e. user login) is very useful. We are making some changes which means we will pre-create users in Intercom via API when their accounts are provisioned. Users created via API have First Seen automatically populated as the time they are created in Intercom. Is there a way to null this field, or otherwise reset/overwrite/etc? I guessed at “first_seen_at” as the field name since it’s not listed in the docs. Anyone else have this issue or solved it a different way?

1211

Edusson DevNew Participant

Disable the message sound when hide_default_launcher: true

Hello! I hide my Intercom widget on some pages of the app using Intercom('update', {hide_default_launcher: true}); . The problem is that the user still hears messages sound even when the chat is hidden. Is there any way to mute the chat? Or any other methods to hide chat completely, including the sound?

1392

ValterNew Participant

Error "Query body must contain a query hash" when searching conversations

Hi, I’m trying to use a snippet code i got from your developer party, to search conversations between two epochs. The codes runs without a problem on your platform, but when I use it in google scripts I get the response: {"code":"invalid_query","message":"Query body must contain a query hash"} I guess it is related to the JSON payload, though the string seems to be ok. I was able to work with the API without any problem, when I don’t send a body, but I always get the error whenever I include a body. Any clue? const str = JSON.stringify({ query: { value: [ {field: 'created_at', operator: '>', value: '1690081199'}, {field: 'created_at', operator: '<', value: '1690167601'} ], operator: 'AND' } }); const options = { method: 'POST', headers: { accept: 'application/json', 'content-type': 'application/json', authorization: 'Bearer XXXXXXXXXXXXXXXXXXXXXX' }, body: str }; const response = UrlFetchApp.fetch('https://api.intercom.io/conversations/search', options );

1243

ssyam011New Participant

Canvas Kt Initiate Screen Issue

We’re trying out the canvas app. When we pass the header and text components, the Canvas is loading correctly in the Inbox.This is the request body: { "canvas": { "content": { "components": [{ "type": "text", "text": "Create Case in SF", "style": "header", "label": "sf create case", "align": "center" }, { "type": "text", "text": "his is a text component." }] } }} But, when we try to add a button as well, along with the text components, it is showing an error.{ "canvas": { "content": { "components": [{ "type": "text", "text": "Create Case in SF", "style": "header", "label": "sf create case", "align": "center" }, { "type": "text", "text": "his is a text component." }, { "type": "button", "style": "primary", "label": "Click", "component_id": "url_button", "action": { "type": "submit" } }] } }} Need to know what’s wrong in our second request?

543

Alexander LeenaersNew Participant

Anyone else getting errors using the REST API?

Getting more and more timing out or internal server errors. Anyone else has the same issue?

281

Gideon JeffreyNew Participant

Question about inconsistencies in "Models" documentation for API v2.9

Hi! I have a question about which to rely on in the API v2.9 Models documentation: the example JSON object, or the documented fields / field datatypes. In some cases the inconsistencies can be significant. For example, in looking at https://developers.intercom.com/intercom-api-reference/reference/the-contact-model I can see the following differences: Documentation does not include the external_id field from the example JSON. Documentation lists avatar as having type object but in the example object it has type string. Documentation does not include the opted_out_subscription_types field from the example JSON. Documentation does not include the opted_in_subscription_types field from the example JSON. Documentation does not include the utm_campaign field from the example JSON. Documentation does not include the utm_content field from the example JSON. Documentation does not include the utm_medium field from the example JSON. Documentation does not include the utm_source field from the ex

962

karol tNew Participant

Cannot send message as Operator

Hey! I try to build an auto respond integration but I have a problem with sending a message to the Customer using an API. I’m using https://github.com/intercom/intercom-node as a library for communication with intercom API. When I try to reply to the conversation using the adminID and I’ll provide operator user ID everything seems fine at the first glance so: api doesn’t return any error, message is added to the conversation in the inbox, But unfortunately email never arrives to the user. When I use different adminID everything works fine. I tried to search in the docs but I didn’t see if there are some limits related to sending a message as an operator. So my questions are: Is it possible to reply to the conversation using an Operator from the API? If it is possible do I need to add some extra configuration for the Operator in order to send messages to the user.

1541

samuel.enerfloNew Participant

Can I run multiple intercoms on the same application?

Our platform uses our own Intercom instance for chat support, but a recent integration provided us with a second Intercom instance to also include in our application for customers to reach out to their support as needed. I have been looking for documentation about the feasibility of this, but have been unable to locate any across the site. For our instance, we use the Intercom JavaScript library loaded by Segment. Our instance uses the identify verification functionality, but the new instance to be included does not. Thanks for any insight into the feasibility of this, as well as any supporting documentation.

8022

Agente BMNew Participant

Sending Images Directly via the Intercom API on WhatsApp

Good morning, currently we are using the Intercom API with WhatsApp (inbound) and replying via the API. However, we are unable to find in the documentation how to respond to a conversation via API with an image. We would like to send an image directly, not just a URL.

3301

ClouseNew Participant

Static Page Metadata In API Response

Hi, I am making requests against the “Search Conversations” endpoint https://developers.intercom.com/intercom-api-reference/reference/searchconversations and paginating (using incremented pages) until the “total_pages” number returned in the response. However, I noticed that each response always shows page “1” with the same next page number of “2” along with an identical starting_after token each time under the “pages” object. Why is this the case -- can a support member help me get this addressed? Thanks, Clouse

511

User700New Participant

Articles API by tab

You would think the Articles API needs to accept TAGs as a param for it to work efficiently….other wise you cal call only by single IDs…... Any one else agree?

1012

Ted MartinezNew Participant

Query for null or not null

url = "https://api.intercom.io/conversations/search" headers = { 'Accept': 'application/json', 'Authorization': 'Bearer auth-token', "Intercom-Version": "2.9", "Content-Type": "application/json" } params = { "query": { "operator": "AND", "value": [ { "field": "team_assignee_id", "operator": "!=", "value": None}]} } response = requests.post(url, headers=headers, json=params) I want to get all assigned conversation and I have only one conversation and it’s team_assignee_id value is null. This query should return an empty list, but it is returning that conversation. What is the correct setup to get only assigned conversations? Also, for whatever reason, the equal(“=”) operator returns the same result. "query": {"field": "team_assignee_id","operator": "=","value": None} This query using equals and not equals return an empty list.

3251

Seth AlexanderNew Participant

Conversation reply failing with 403

Through our monitoring systems we’ve identified that sometimes API calls to https://api.intercom.io/conversations/{id}/reply are failing with a 403 response. The documentation is not clear on why this would happen. We’re seeing this ~3% of the time.

2952

Sujeevan NagarajahNew Participant

Protecting custom app webhook URLs

Hi, I’m building a custom intercom app. I have two APIs created for both Initialize flow webhook URL and Submit flow webhook URL and they work as I expected. The question is, It looks like these two API can’t be protected using API key or other authentication mechanism. Is there a way to confirm the requests come to these APIs are actually from Intercom, not from some malicious actors. Any help on this appreciated.

1204

Max De Burnay-BastosNew Participant

How to best manage multiple API calls?

Hi there, I am looking for advice on how to best manage API calls for our business application. It appears that using the API, multiple calls will be necessary to be able to perform given actions. For example, if a user has signed into our application and wishes to start a conversation, from what I understand they will have to: - Fetch their id with their email using the /contacts/search endpoint- Create a conversation with their id using the /conversations endpoint- If successful, we want to refresh our device to display the new message and created conversation, meaning we must hit the /conversations/id endpoint For this flow, this is 3 calls per action, which could add up quite substantially if multiple users are operating simultaneously. Is there a better way to do this? Perhaps I am not using the API as efficiently as I could be. Thanks!

2012

Max De Burnay-BastosNew Participant

Best Way To Manage Mutliple API Calls?

I have an which gets customer conversations and displays them in a Whatsapp-esque UI. The problem is that in order to do this, I have to: - Hit an endpoint that will get the contact information using their email- Hit an endpoint using their contact id to create a conversation- If this conversation creation is successful, hit the endpoint to fetch the conversation to display the latest message to the user. This seems very inefficient at present. Is there a better way to use the API? Thanks

252

ariodNew Participant

Valid values for the "region" field

In the /me endpoint, what are the valid values for the app.region property? In my test account, I get back the string “US”, but what are the values for the EU and Australian regions? (Or any other that are supported.)

2242

chrisbr0New Participant

API: GET: Conversation: Pagination not working

Hello, I try to modify my json configurator to extract all conversions. However pagination does not work. Can someone assist please? The json I have is as following: { "parameters": { "api": { "baseUrl": "https://api.intercom.io/" }, "pagination": { "method": "cursor", "perPageParam": "per_page", "perPage": 150, "startingAfterParam": "starting_after", "startingAfter": "" }, "config": { "outputBucket": "ge-tutorial", "debug": true, "jobs": [ { "endpoint": "conversations", "params": { "per_page": "{{perPage}}", "starting_after": "{{startingAfter}}" }, "headers": { "Intercom-Version": "2.9", "accept": "application/json", "authorization": "Bearer -----" } } ] }, "incrementalOutput": true }}

1821