http://localhost:11345 (default)
Authentication
If enabled, authentication must be provided via one of the following methods:- Header:
x-api-key: your_keyorkey: your_key - Authorization Header:
Authorization: Bearer your_key - Request Body:
{"apiKey": "your_key"}or{"key": "your_key"}
List tasks (lightweight)
GET /api/tasks/list
Returns a lightweight list of all saved tasks with summary metadata (ID, name, description, mode, schedule, variables, createdAt, updatedAt) without version history or full action lists. Requires API-key authentication. Use this for dashboard overviews and lightweight integrations.
Response:
List tasks (full)
GET /api/tasks
Lists all saved tasks with full configuration (except version history). Prefer GET /api/tasks/list for lightweight listings.
Response:
Create or upsert a task
POST /api/tasks
Creates a new task or overwrites an existing task with the same id.
Include ?version=true in the query string to save a version snapshot before overwriting.
Query parameters:
Body:
Response: Returns the saved task object.
Partially update a task
PATCH /api/tasks/:id
Applies a partial update to an existing task. Only the fields you include in the body are changed. The id and versions fields are ignored if supplied. Figranium takes a version snapshot before applying the update, so you can restore the previous state from the version history.
Use this endpoint when you want to change a single attribute (for example, a schedule, a variable, or one action) without re-sending the full task definition.
Body (any subset of task fields):
Delete a task
DELETE /api/tasks/:id
Deletes a task by ID. Any in-process schedule registered for the task is also removed, so a scheduled run will not fire after deletion.
Response:
Trigger a task
POST /api/tasks/:id/api
Triggers an execution of a specific task. This is the primary endpoint most integrations use: send a POST to a task’s URL to run it on demand, optionally overriding variables or receiving a webhook callback when it finishes.
Body:
Response: Returns the execution result (JSON).
The request body is optional. If you send the request without a body or without a
Content-Type: application/json header, Figranium treats the body as {} and runs the task with its default variables. This lets tools that can’t set request headers (for example, Clay’s HTTP action) trigger a task with a bare POST to the endpoint URL.To pass variables, webhookUrl, statelessExecution, or sessionId, you must send Content-Type: application/json and a JSON body.Completion webhook
When you include awebhookUrl, Figranium sends a POST request to that URL after the task finishes. The webhook URL is validated against the same SSRF rules as all other outbound requests (see Security). If the URL points to a private network and ALLOW_PRIVATE_NETWORKS is false, the request returns 400 INVALID_WEBHOOK_URL.
The callback payload looks like this:
Version history
GET /api/tasks/:id/versions
Lists saved versions of a task.
Response:
GET /api/tasks/:id/versions/:versionId
Returns a specific version snapshot.
Response:
POST /api/tasks/:id/versions/clear
Clears a task’s version history.
Response:
POST /api/tasks/:id/rollback
Rolls a task back to a previous version.
Body:
Response: Returns the restored task object.
Capacity and timeout errors
Execution endpoints can return these errors when resource protection is active:Related pages
REST API Reference
Complete reference for endpoints, authentication, and examples.
API Key
Generate and authenticate with your API key.
API Scopes
Choose the right permissions for your integrations.