Enable or disable an output config
curl -X PATCH 'https://api.justcrawl.io/api/v1/integrations/outputs/oc_01ABC/toggle' \ -H 'Authorization: Bearer $JUSTCRAWL_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"isEnabled":false}'Soft pause / resume on an output destination — flips isEnabled
without deleting the config or wiping its credentials. Workflow nodes
referencing a disabled output skip the delivery without erroring out
the run; useful for incident-mode pause when a downstream is misbehaving
(rotating webhook secret, S3 bucket maintenance, billing investigation)
without forcing a full re-provision afterwards.
The internal system-managed config can be toggled — the BI Phase 0
invariant is on identity / FK presence, not on enabled state — but
doing so will silently drop bigdata-node writes. Use with care.
Requires the org:manage permission.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Output config ID.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Examplegenerated
{ "isEnabled": true}Responses
Section titled “Responses”New isEnabled state.
object
Examplegenerated
{ "id": "example", "isEnabled": true}Validation failed — request body or query is missing/invalid
object
Example
{ "error": "Missing or invalid \"url\" field"}Missing or invalid authentication token
object
Example
{ "error": "Missing or invalid authentication token"}Insufficient permissions for this operation
object
Example
{ "error": "No organization. Complete onboarding first."}Resource not found
object
Example
{ "error": "Workflow not found"}Unexpected server error. Logs and PostHog $exception capture
object
Example
{ "error": "Something went wrong"}