POST /api/v2/ticket_content_pins
Creates a new content pin for a specific ticket. Content pins allow you to link to articles, community posts, or external content for easy reference.
Allowed For
- Admins
- Agents
Servers
- https://{subdomain}.{domain}.com
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
ticket_content_pin |
Object | No | |
ticket_content_pin.content_type |
String | Yes |
The type of content being pinned. |
ticket_content_pin.ticket_id |
String | Yes |
The id of the ticket to which the content pin will be added |
ticket_content_pin.content_id |
String | Yes |
The id of the content to pin |
ticket_content_pin.locale |
String | No |
The locale for the content pin. This is required only for articles. |
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.