Inspector
Replay Workflow
Schedule a workflow replay from an optional history entry.
The inspector API is subject to change without notice. Do not build production integrations on it.
POST https://rivet.example.com/gateway/{actor}/inspector/workflow/replay
Examples
curl -X POST "https://rivet.example.com/gateway/$ACTOR_ID/inspector/workflow/replay" \
-H "Authorization: Bearer $INSPECTOR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"entryId": "entry-123"
}'
const endpoint = "https://api.rivet.dev";
const response = await fetch(
`${endpoint}/gateway/${process.env.ACTOR_ID}/inspector/workflow/replay`,
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.INSPECTOR_TOKEN}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ entryId: "entry-123" }),
},
);
console.log(await response.json());
export {};
Authentication
Inspector endpoints do not accept namespace tokens. Send the actor’s inspector token as a bearer token in the Authorization header.
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
actor | string | Yes | Actor ID, actor ID with an inline token ({actor_id}@{token}), or actor name combined with the rvt-* query parameters. |
Headers
| Name | Type | Required | Description |
|---|---|---|---|
Authorization | string | No | Bearer token for inspector authentication. Required in production, optional in development. |
Actor Selector
{actor} accepts an actor ID, an actor ID with an inline routing token ({actor_id}@{token}), or an actor name combined with the rvt-* query parameters below. See Actor Routing for the full rules.
Request Body
Content type: application/json (optional).
| Field | Type | Required | Description |
|---|---|---|---|
entryId | string | No |
Responses
200
Workflow history after scheduling the replay.
| Field | Type | Description |
|---|---|---|
history | any | |
isWorkflowEnabled | boolean |
{
"history": "<history>",
"isWorkflowEnabled": false
}
401
The inspector token is missing or invalid.