Skip to content
Davirix

What a connector is

Available

A connector binds Davirix to an external system: a CRM, an SMS provider, a payment gateway, your own ERP.

Two parts

Section titled “Two parts”
Part What Who writes it
Manifest (.json) Declarative: which operations exist, input/output shape, verification rule You
Adapter (code) The HTTP call and response normalisation You

What the manifest declares

Section titled “What the manifest declares”
{
  "id": "bitrix24",
  "version": "2.1.0",
  "category": "crm",
  "scope": "global",
  "auth":   { "type": "api_key", "credential_ref": "vault:connectors/bitrix24" },
  "config_schema": { },
  "operations": [ ]
}

⚠ A secret is never in the manifest — only a vault: reference. Inline secrets are rejected at the schema level.

An operation

Section titled “An operation”
{
  "name": "crm.create_deal",
  "direction": "write",
  "risk_level": "L2",
  "idempotent": false,
  "timeout_ms": 20000,
  "input_schema":  { },
  "output_schema": { },
  "verification":  { }
}
Field Required
name · direction · risk_level ✅
input_schema · output_schema ✅
idempotent · timeout_ms ✅
verification for writes — ⚡ the most important

direction: read · write · stream risk_level: L0 … L4 — informational only; the decision is the platform’s.

The route

Section titled “The route”
1. Write the manifest
2. Write the adapter
3. Verify locally           ← davirix connector verify
4. Submit
5. The system re-verifies   ← conformance suite C1–C12
6. You get a certificate    ← level L0–L4

Three rules — know them upfront

Section titled “Three rules — know them upfront”

Next

Section titled “Next”