POST /api/v2/requests
Accepts a request object that sets one or more properties.
Allowed for
- End users
- Anonymous users (rate limit of 5 requests per hour for trial accounts)
Additional properties
In addition to the writable request properties in the JSON Format table above, you can set the following properties when creating a request.
| Name | Type | Mandatory | Comment |
|---|---|---|---|
| comment | object | yes | Describes the problem, incident, question, or task. See Request comments |
| collaborators | array | no | Adds collaborators (cc's) to the request. An email notification is sent to them when the ticket is created. See Setting collaborators |
| requester | object | yes* | *Required for anonymous requests. Specifies the requester of the anonymous request. See Creating anonymous requests |
Creating follow-up requests
Once a ticket is closed (as distinct from solved), it can't be reopened. However, you can create a new request that references the closed ticket. To create the follow-up request, include a via_followup_source_id property in the request object that specifies the closed ticket. The parameter only works with closed tickets. It has no effect with other tickets.
Servers
- https://{subdomain}.{domain}.com
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.