Task History API
The Task History API allows you to query your users' usage of integration workflows and access data from historical workflow executions. Includes endpoints to list and inspect workflow executions, drill into step executions, and replay failed runs. Available on Enterprise plans; rate limited to 1,000 requests per 10 minutes.
Task History API is one of 10 APIs that Paragon publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Embedded Integrations, Task History, Workflows, and Integrations. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, a JSON-LD context, and 2 JSON Schemas.
This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against a single base URL, https://actionkit.useparagon.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Task History API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Paragon User Token. A signed JWT token used to authenticate a Connected User.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Query historical workflow executions and replay specific executions.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are WorkflowExecution (8 properties), WorkflowExecutionList (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Paragon 9
Other APIs Paragon publishes across the network.