Get the system-managed internal output config

GET

/api/v1/integrations/outputs/internal

Code sample: cURL

curl -X GET 'https://dashboard.justcrawl.io/api/v1/integrations/outputs/internal' \
  -H 'Authorization: Bearer $JUSTCRAWL_API_KEY'

• Production

Returns the per-org internal output_config row provisioned by the BI v3 Phase 0 0e backfill (V096). This config is the FK target every auto-migrated bigdata workflow node references; the workflow editor reads it to know which outputConfigId to set when inserting a new bigdata node (“Add Internal warehouse” remediation, 0h). Steady-state every org has one — 404 only fires on legacy orgs that predate the V096 backfill, which should not exist in production.

Hidden from GET /api/v1/integrations/outputs by design — surfacing it on the Integrations page would let org:manage users try to delete or edit it. DELETE /api/v1/integrations/outputs/{id} also refuses the internal config with 409.

Authorizations

• bearerAuth

Responses

200

The org’s internal output configuration.

Media type application/json

object

id

string format: uuid

name

string

outputType

string

Allowed values: s3 webhook

destination

string

isEnabled

boolean

lastDeliveredAt

string format: date-time

nullable

lastError

string

nullable

createdAt

string format: date-time

Example

{
  "outputType": "s3"
}

401

Missing or invalid authentication token

Media type application/json

object

error

string

Example

{
  "error": "Missing or invalid authentication token"
}

403

Insufficient permissions for this operation

Media type application/json

object

error

string

Example

{
  "error": "No organization. Complete onboarding first."
}

404

Resource not found

Media type application/json

object

error

string

Example

{
  "error": "Workflow not found"
}

500

Unexpected server error. Logs and PostHog $exception capture

Media type application/json

object

error

string

Example

{
  "error": "Something went wrong"
}