QELLVIS
← Back to Navigator

QELLVIS Connect

Connect integrates external APIs into the QELLVIS System Behavior Layer. The endpoint validates the user, checks plan limits, fetches your API, extracts structure and stores the system.

ENDPOINT
POST /api/connect
AUTHENTICATION

Connect requires a valid QELLVIS user access token:

Authorization: Bearer <USER_ACCESS_TOKEN>
REQUEST BODY
{
  "name": "My System",
  "url": "https://example.com/api",
  "auth": {
    "token": "optional-external-api-token"
  }
}

name — system name url — external API endpoint auth.token — optional Bearer token for the external API

EXTERNAL API REQUIREMENTS
  • • must accept POST
  • • must return valid JSON
  • • must allow CORS
  • • may require Bearer authentication
PAYLOAD STRUCTURE

The external API must return a structure compatible with:

{
  "nodes": [...],
  "dependencies": [...]
}

Alternative keys supported: payload, system, record, data, graph.

PLAN LIMITS
  • • free → 1 system
  • • plus → 3 systems
  • • premium → 999 systems
  • • enterprise → 999 systems
RESPONSE
{
  "ok": true,
  "system": {
    "id": "...",
    "name": "...",
    "nodes": [...],
    "dependencies": [...],
    "source_type": "api",
    "source_config": { "url": "...", "auth": {...} }
  }
}
ERRORS
  • • 400 — missing name or url
  • • 400 — external API unreachable
  • • 400 — external API error
  • • 400 — external API invalid JSON
  • • 401 — missing or invalid user token
  • • 403 — plan limit reached
  • • 500 — failed to create system