PUT /ai/external_pages/{id}

You can update an existing external page (if it was created via the API).

Servers

Path parameters

Name Type Required Description
id String Yes

The unique identifier for the external page which is given by Intercom.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Intercom-Version String No

Possible values:

  • "1.1"
  • "2.0"
  • "1.0"
  • "2.9"
  • "Unstable"
  • "1.3"
  • "2.2"
  • "2.12"
  • "1.2"
  • "2.1"
  • "2.4"
  • "1.4"
  • "2.3"
  • "2.6"
  • "2.5"
  • "2.8"
  • "2.10"
  • "2.7"
  • "2.11"

Default value: "2.12"

Request body fields

Name Type Required Description
source_id Integer Yes

The unique identifier for the source of the external page which was given by Intercom. Every external page must be associated with a Content Import Source which represents the place it comes from and from which it inherits a default audience (configured in the UI). For a new source, make a POST request to the Content Import Source endpoint and an ID for the source will be returned in the response.

html String Yes

The body of the external page in HTML.

external_id String No

The identifier for the external page which was given by the source. Must be unique for the source.

url String Yes

The URL of the external page. This will be used by Fin to link end users to the page it based its answer on.

title String Yes

The title of the external page.

locale String Yes

Always en

Possible values:

  • "en"

Default value: "en"

fin_availability Boolean No

Whether the external page should be used to answer questions by Fin.

Default value: true

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.