Webhooks
Receive real-time HTTP POST callbacks from Segmind when a PixelFlow run changes state, so you can react to node and graph events without polling.
Introduction
Webhooks are a powerful feature that allows users or applications to receive real-time updates from the Segmind platform. They enable seamless integration by sending HTTP POST requests to a specified URL whenever certain events occur. This allows developers to automate workflows and respond to events in real-time without polling the API for updates.
Scope. Webhooks cover PixelFlow runs (and legacy fine-tuning jobs)
only. They are not sent for individual /v1 or /v2 model requests — those
are polling-only (see async inference).
To get a callback for a single model, wrap it in a one-node PixelFlow,
publish it as an API, and register a
GRAPH_RUN webhook.
PixelFlow events
Updates on the execution of API nodes inside PixelFlow workflows, with outputs delivered as URLs. Two events are supported:
NODE_RUN— sent whenever an API node runs.GRAPH_RUN— sent once a workflow API has finished all processing.
Registering a webhook
Go to Webhooks in the console, under Developer, and register the URL you want called.
You can also manage registrations from the Python SDK or the JavaScript SDK without opening the console:
import segmind
segmind.webhooks.get() # list your registrations
segmind.webhooks.add(webhook_url, event_types)
segmind.webhooks.update(webhook_id, webhook_url) # point it at a new URL
segmind.webhooks.delete(webhook_id) # deactivate it
segmind.webhooks.logs(webhook_id) # delivery history for one registrationupdate changes the URL only: to change a registration's event types, delete
it and add a new one. Use Python SDK 1.3.1 or JavaScript SDK 0.2.4 or
later. Earlier versions registered a second webhook on update and deactivated
nothing on delete.
logs() is the one to reach for when a webhook is not arriving — it shows what
was attempted for that registration, which distinguishes "never sent" from
"sent and your endpoint rejected it".
Fine-tuning events
Fine-tuning webhooks — DATA_PROCESSING, TRAINING_INITIATED,
TRAINING_COMPLETED, DEPLOYING and AVAILABLE — relate to the fine-tuning
service, which no longer accepts new training jobs. They are listed here for
existing integrations only. See the
fine-tuning overview.