diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index b072024b..2cb2b4da 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -3635,7 +3635,7 @@ paths: `https://api.intercom.io/articles`.\n\n> \U0001F4D8 How are the articles sorted and ordered?\n>\n> Articles will be returned in descending order on the `updated_at` attribute. This means if you need to iterate through results then we'll show - the most recently updated articles first.\n\nRequires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`.\n" + the most recently updated articles first.\n\nRequires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`.\n" responses: '200': description: successful @@ -3726,7 +3726,7 @@ paths: \U0001F4D8 Tags are managed separately\n>\n> Tags are returned in article responses but cannot be set in the request body. To add or remove an article's tags, use the `POST /articles/{article_id}/tags` and `DELETE /articles/{article_id}/tags/{id}` - endpoints.\n\nRequires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`.\n" + endpoints.\n\nRequires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`.\n" responses: '200': description: article created @@ -3946,7 +3946,7 @@ paths: description: | You can fetch the details of a single article by making a GET request to `https://api.intercom.io/articles/`. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Article found @@ -4047,7 +4047,7 @@ paths: request to `https://api.intercom.io/articles/`.\n\n> \U0001F4D8 Tags are managed separately\n>\n> Tags are returned in article responses but cannot be set in the request body. To add or remove an article's tags, use the `POST /articles/{article_id}/tags` and `DELETE /articles/{article_id}/tags/{id}` - endpoints.\n\nRequires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`.\n" + endpoints.\n\nRequires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`.\n" responses: '200': description: successful @@ -4334,7 +4334,7 @@ paths: has no staged draft. An article ID that doesn't exist returns a `404` with the standard error body. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Article draft found @@ -4423,7 +4423,7 @@ paths: `parent_id`, `folder_id`, `audience_ids`, the AI availability fields or the scheduling fields, is still validated but not applied, so the live article is left untouched. - Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Draft staged @@ -4541,7 +4541,7 @@ paths: `{ "errors": [{ "message": "...", "status": 422 }] }`, with no `type`, `request_id` or `code`. The other `422` errors use the standard error format. - Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Draft published @@ -4688,7 +4688,7 @@ paths: A `404` has an empty response body, whether the article or its content isn't found. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Versions found @@ -4789,7 +4789,7 @@ paths: A `404` has an empty response body, whether the article, its content or the version isn't found. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Version found @@ -4858,7 +4858,7 @@ paths: and the authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. requestBody: content: application/json: @@ -4977,7 +4977,7 @@ paths: The authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Tag removed @@ -5105,7 +5105,7 @@ paths: If no articles match the search, `data` is an empty array rather than an object. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Search successful @@ -7406,7 +7406,7 @@ paths: description: | You can fetch a list of all collections by making a GET request to `https://api.intercom.io/help_center/collections`. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Successful @@ -7497,7 +7497,7 @@ paths: description: | You can create a new collection by making a POST request to `https://api.intercom.io/help_center/collections`. - Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: collection created @@ -7597,7 +7597,7 @@ paths: description: | You can fetch the details of a single collection by making a GET request to `https://api.intercom.io/help_center/collections/`. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Collection found @@ -7670,7 +7670,7 @@ paths: `help_center_id` is checked but never applied. It must match the help center of the collection's articles and sub-collections, or the request returns a `400`. A collection with no content rejects any `help_center_id`, so leave it out. Moving a collection to another help center isn't supported. - Requires the `read_write_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: successful @@ -7846,7 +7846,7 @@ paths: description: | You can fetch the details of a single Help Center by making a GET request to `https://api.intercom.io/help_center/help_centers/`. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Help Center found @@ -7911,7 +7911,7 @@ paths: description: | You can list all Help Centers by making a GET request to `https://api.intercom.io/help_center/help_centers`. - Requires the `read_articles_scope` OAuth scope. Set `Intercom-Version: Preview`. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. Set `Intercom-Version: Preview`. responses: '200': description: Help Centers found diff --git a/descriptions/2.16/api.intercom.io.yaml b/descriptions/2.16/api.intercom.io.yaml index 1511e04d..4de276a0 100644 --- a/descriptions/2.16/api.intercom.io.yaml +++ b/descriptions/2.16/api.intercom.io.yaml @@ -2557,7 +2557,7 @@ paths: A draft exists only when a published article has unpublished changes staged on top of it. Returns `404` when the article has no staged draft. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Article draft found @@ -2619,7 +2619,7 @@ paths: Non-versioned fields like AI availability are ignored, leaving the live values untouched. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Draft staged @@ -2705,7 +2705,7 @@ paths: omitting it returns `422`. Returns `422` when there is no staged draft to publish, or when a requested locale has no pending changes. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Draft published @@ -2805,7 +2805,7 @@ paths: and the authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. requestBody: content: application/json: @@ -2917,7 +2917,7 @@ paths: The authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Tag removed @@ -3019,7 +3019,7 @@ paths: `GET /articles/{article_id}/versions/{id}` to retrieve a single version with its full content. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Versions found @@ -3117,7 +3117,7 @@ paths: `https://api.intercom.io/articles//versions/`. Returns the version's full content; the live article remains untouched. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Version found diff --git a/descriptions/2.17/api.intercom.io.yaml b/descriptions/2.17/api.intercom.io.yaml index 9786aee1..77362586 100644 --- a/descriptions/2.17/api.intercom.io.yaml +++ b/descriptions/2.17/api.intercom.io.yaml @@ -3816,7 +3816,7 @@ paths: `https://api.intercom.io/articles`.\n\n> \U0001F4D8 How are the articles sorted and ordered?\n>\n> Articles will be returned in descending order on the `updated_at` attribute. This means if you need to iterate through results then we'll show - the most recently updated articles first.\n\nRequires the `read_articles_scope` OAuth scope.\n" + the most recently updated articles first.\n\nRequires the `read_articles_scope` or `create_update_articles` OAuth scope.\n" responses: '200': description: successful @@ -3907,7 +3907,7 @@ paths: \U0001F4D8 Tags are managed separately\n>\n> Tags are returned in article responses but cannot be set in the request body. To add or remove an article's tags, use the `POST /articles/{article_id}/tags` and `DELETE /articles/{article_id}/tags/{id}` - endpoints.\n\nRequires the `read_write_articles_scope` OAuth scope.\n" + endpoints.\n\nRequires the `read_write_articles_scope` or `create_update_articles` OAuth scope.\n" responses: '200': description: article created @@ -4109,7 +4109,7 @@ paths: description: | You can fetch the details of a single article by making a GET request to `https://api.intercom.io/articles/`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Article found @@ -4210,7 +4210,7 @@ paths: request to `https://api.intercom.io/articles/`.\n\n> \U0001F4D8 Tags are managed separately\n>\n> Tags are returned in article responses but cannot be set in the request body. To add or remove an article's tags, use the `POST /articles/{article_id}/tags` and `DELETE /articles/{article_id}/tags/{id}` - endpoints.\n\nRequires the `read_write_articles_scope` OAuth scope.\n" + endpoints.\n\nRequires the `read_write_articles_scope` or `create_update_articles` OAuth scope.\n" responses: '200': description: successful @@ -4494,7 +4494,7 @@ paths: has no staged draft. An article ID that doesn't exist returns a `404` with the standard error body. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Article draft found @@ -4585,7 +4585,7 @@ paths: scheduling, state and placement notes on the request schema's other fields do not apply to this endpoint, because those fields are not applied. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Draft staged @@ -4703,7 +4703,7 @@ paths: `{ "errors": [{ "message": "...", "status": 422 }] }`, with no `type`, `request_id` or `code`. The other `422` errors use the standard error format. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Draft published @@ -4824,7 +4824,7 @@ paths: and the authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. requestBody: content: application/json: @@ -4943,7 +4943,7 @@ paths: The authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Tag removed @@ -5048,7 +5048,7 @@ paths: A `404` has an empty response body, whether the article or its content isn't found. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Versions found @@ -5149,7 +5149,7 @@ paths: A `404` has an empty response body, whether the article, its content or the version isn't found. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Version found @@ -5258,7 +5258,7 @@ paths: If no articles match the search, `data` is an empty array rather than an object. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Search successful @@ -8496,7 +8496,7 @@ paths: description: | You can fetch a list of all collections by making a GET request to `https://api.intercom.io/help_center/collections`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Successful @@ -8587,7 +8587,7 @@ paths: description: | You can create a new collection by making a POST request to `https://api.intercom.io/help_center/collections`. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: collection created @@ -8687,7 +8687,7 @@ paths: description: | You can fetch the details of a single collection by making a GET request to `https://api.intercom.io/help_center/collections/`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Collection found @@ -8760,7 +8760,7 @@ paths: `help_center_id` is checked but never applied. It must match the help center of the collection's articles and sub-collections, or the request returns a `400`. A collection with no content rejects any `help_center_id`, so leave it out. Moving a collection to another help center isn't supported. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: successful @@ -8936,7 +8936,7 @@ paths: description: | You can fetch the details of a single Help Center by making a GET request to `https://api.intercom.io/help_center/help_centers/`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Help Center found @@ -9001,7 +9001,7 @@ paths: description: | You can list all Help Centers by making a GET request to `https://api.intercom.io/help_center/help_centers`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Help Centers found diff --git a/descriptions/2.18/api.intercom.io.yaml b/descriptions/2.18/api.intercom.io.yaml index d725ea12..b5a5c82c 100644 --- a/descriptions/2.18/api.intercom.io.yaml +++ b/descriptions/2.18/api.intercom.io.yaml @@ -3816,7 +3816,7 @@ paths: `https://api.intercom.io/articles`.\n\n> \U0001F4D8 How are the articles sorted and ordered?\n>\n> Articles will be returned in descending order on the `updated_at` attribute. This means if you need to iterate through results then we'll show - the most recently updated articles first.\n\nRequires the `read_articles_scope` OAuth scope.\n" + the most recently updated articles first.\n\nRequires the `read_articles_scope` or `create_update_articles` OAuth scope.\n" responses: '200': description: successful @@ -3907,7 +3907,7 @@ paths: \U0001F4D8 Tags are managed separately\n>\n> Tags are returned in article responses but cannot be set in the request body. To add or remove an article's tags, use the `POST /articles/{article_id}/tags` and `DELETE /articles/{article_id}/tags/{id}` - endpoints.\n\nRequires the `read_write_articles_scope` OAuth scope.\n" + endpoints.\n\nRequires the `read_write_articles_scope` or `create_update_articles` OAuth scope.\n" responses: '200': description: article created @@ -4109,7 +4109,7 @@ paths: description: | You can fetch the details of a single article by making a GET request to `https://api.intercom.io/articles/`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Article found @@ -4210,7 +4210,7 @@ paths: request to `https://api.intercom.io/articles/`.\n\n> \U0001F4D8 Tags are managed separately\n>\n> Tags are returned in article responses but cannot be set in the request body. To add or remove an article's tags, use the `POST /articles/{article_id}/tags` and `DELETE /articles/{article_id}/tags/{id}` - endpoints.\n\nRequires the `read_write_articles_scope` OAuth scope.\n" + endpoints.\n\nRequires the `read_write_articles_scope` or `create_update_articles` OAuth scope.\n" responses: '200': description: successful @@ -4494,7 +4494,7 @@ paths: has no staged draft. An article ID that doesn't exist returns a `404` with the standard error body. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Article draft found @@ -4585,7 +4585,7 @@ paths: scheduling, state and placement notes on the request schema's other fields do not apply to this endpoint, because those fields are not applied. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Draft staged @@ -4703,7 +4703,7 @@ paths: `{ "errors": [{ "message": "...", "status": 422 }] }`, with no `type`, `request_id` or `code`. The other `422` errors use the standard error format. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Draft published @@ -4824,7 +4824,7 @@ paths: and the authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. requestBody: content: application/json: @@ -4943,7 +4943,7 @@ paths: The authenticating teammate must have the `manage_knowledge_base_content` permission. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Tag removed @@ -5048,7 +5048,7 @@ paths: A `404` has an empty response body, whether the article or its content isn't found. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Versions found @@ -5149,7 +5149,7 @@ paths: A `404` has an empty response body, whether the article, its content or the version isn't found. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Version found @@ -5258,7 +5258,7 @@ paths: If no articles match the search, `data` is an empty array rather than an object. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Search successful @@ -8509,7 +8509,7 @@ paths: description: | You can fetch a list of all collections by making a GET request to `https://api.intercom.io/help_center/collections`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Successful @@ -8600,7 +8600,7 @@ paths: description: | You can create a new collection by making a POST request to `https://api.intercom.io/help_center/collections`. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: collection created @@ -8700,7 +8700,7 @@ paths: description: | You can fetch the details of a single collection by making a GET request to `https://api.intercom.io/help_center/collections/`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Collection found @@ -8773,7 +8773,7 @@ paths: `help_center_id` is checked but never applied. It must match the help center of the collection's articles and sub-collections, or the request returns a `400`. A collection with no content rejects any `help_center_id`, so leave it out. Moving a collection to another help center isn't supported. - Requires the `read_write_articles_scope` OAuth scope. + Requires the `read_write_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: successful @@ -8949,7 +8949,7 @@ paths: description: | You can fetch the details of a single Help Center by making a GET request to `https://api.intercom.io/help_center/help_centers/`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Help Center found @@ -9014,7 +9014,7 @@ paths: description: | You can list all Help Centers by making a GET request to `https://api.intercom.io/help_center/help_centers`. - Requires the `read_articles_scope` OAuth scope. + Requires the `read_articles_scope` or `create_update_articles` OAuth scope. responses: '200': description: Help Centers found