Glossary¶
A comprehensive list of terms used throughout the DIBOP platform and this documentation.
A¶
Alert¶
An automated notification that fires when a monitored metric crosses a defined threshold. Alerts can be sent via email, webhook, or Slack. See Setting Up Alerts.
Alert Rule¶
A configuration that defines when and how an alert should fire. Includes the metric to monitor, the threshold, and the notification channels. See Alert Rules.
API Call¶
A single HTTP request made by DIBOP to an external system through a connector. Every API call is logged and visible in the API Call Log.
API Call Log¶
A record of every HTTP request DIBOP makes to external systems, including method, endpoint, status code, duration, and request/response payloads. See API Call Log.
Assumed Mapping¶
A field mapping suggested by AI that has not yet been confirmed by a human. Assumed mappings should be verified before use in production. See Field Mapping.
B¶
Base URL¶
The root URL of an external system's API (e.g., https://api.example.com). All connector operations append their paths to the base URL.
Bearer Token¶
An authentication method where a static token is sent in the Authorization header as Bearer <token>.
C¶
Canonical Data Model (CDM)¶
DIBOP's universal data schema that normalises fields across all connected systems. Each connector maps its native fields to and from the CDM. See What is the CDM?.
Canonical Explorer¶
An interactive tool in the DIBOP UI for browsing CDM domains, fields, PII classifications, and mapping coverage. See Canonical Explorer.
Circuit Breaker¶
A resilience pattern that stops sending requests to a system after a series of consecutive failures. After a recovery period, a single test request is allowed. If it succeeds, normal traffic resumes. Protects both DIBOP and the external system.
Connection¶
An instance of a connector configured with a specific enterprise's credentials. A connection represents a live link between DIBOP and an external system. See Connecting a System.
Connector¶
A pre-built adapter for an external system. Connectors define how to authenticate, which API operations are available, and how to map fields to the CDM. See Available Connectors.
Connector Builder¶
The UI tool for creating and editing connector templates. Supports manual configuration, AI import from documentation, and OpenAPI import. See Connector Builder.
Connector SDK¶
The set of tools for building, testing, and publishing custom connectors. See Connector SDK Overview.
Cooldown¶
The minimum time between repeated alert notifications for the same rule. Prevents alert fatigue.
D¶
Dead Letter Queue (DLQ)¶
A holding area for messages or records that failed processing after all retry attempts. Items in the DLQ can be manually reviewed, retried, or dismissed.
Domain¶
A business entity in the CDM (e.g., Vehicle, Customer, Order). Each domain has a defined set of fields with types and PII classifications. See Available Domains.
Draft¶
A state for connectors or orchestrations that are still being developed. Draft items cannot be used in production.
E¶
Enterprise¶
An organisation using DIBOP. Each enterprise has its own isolated data, users, connections, and orchestrations. Also called a "tenant."
Enterprise Admin¶
A role in DIBOP that can manage connections, orchestrations, users, and settings within their enterprise. Also called "Tenant Admin." See Roles & Permissions.
Execution¶
A single run of an orchestration, with a unique ID and a full trace of every step's inputs, outputs, and timing. See Execution Log.
Execution Trace¶
A detailed, step-by-step view of a single orchestration execution, showing inputs, outputs, timing, and errors for each step. See Execution Trace.
F¶
Field Mapping¶
The configuration that translates between a connector's native field names and CDM field names. See Field Mapping.
G¶
Gateway Product¶
An API access tier that defines which APIs an enterprise can use, along with quotas and rate limits. See Gateway Products.
H¶
Health Check¶
A periodic ping to a connected system to verify it is reachable and authenticated. Results are displayed as system health indicators on the dashboard.
I¶
Inbound Mapping¶
The translation of data from an external system's native format to CDM format (system to CDM).
J¶
JSONPath¶
A query language for navigating JSON data structures. Used in parameter mapping to reference specific fields within step outputs (e.g., ${step.response.items[0].name}).
JWT (JSON Web Token)¶
A compact token format used for API authentication. DIBOP uses JWTs for user session management and API access.
M¶
Multi-Tenant¶
An architecture where multiple enterprises share the same platform infrastructure while maintaining strict data isolation. Each enterprise's data is completely separate.
N¶
N-to-N Problem¶
The challenge of connecting N systems where each pair requires a unique integration. The CDM solves this by reducing N x (N-1) mappings to 2N. See What is the CDM?.
O¶
OAuth2¶
An authentication framework that uses short-lived tokens instead of long-lived credentials. DIBOP supports the client_credentials and authorization_code grant types.
Operation¶
A single API endpoint defined within a connector (e.g., "Search Vehicles", "Get Customer by ID"). Each operation has a method, path, parameters, and response schema.
Orchestration¶
A multi-step workflow that moves data between connected systems, applies transformations, and handles errors. See What is an Orchestration?.
Outbound Mapping¶
The translation of data from CDM format to an external system's native format (CDM to system).
P¶
Parameter Mapping¶
The mechanism by which data flows between steps in an orchestration. Outputs from one step are referenced as inputs to subsequent steps using ${step_name.field} syntax. See Parameter Mapping.
PII (Personally Identifiable Information)¶
Data that can identify an individual person. CDM fields are classified as None, PII, or Sensitive PII. PII fields are masked in logs and redacted in exports.
Platform Admin¶
A role that manages the shared DIBOP infrastructure: connector catalogue, quotas, gateway products, and enterprise provisioning. See Platform vs Tenant Admin.
Published¶
A state for connectors that are available for use in the catalogue. Published connectors can be used to create connections.
Q¶
Quota¶
A limit on the number of API calls or orchestration executions an enterprise can make within a billing period. See Quotas & Rate Limits.
R¶
Rate Limit¶
A restriction on the number of API requests per second or per minute. Protects external systems and ensures fair usage. See Quotas & Rate Limits.
Retention Policy¶
A configuration that determines how long DIBOP keeps operational data (execution logs, API call logs, etc.) before permanently deleting it. See Retention Policies.
S¶
SLA (Service Level Agreement)¶
A target for service quality, typically expressed as a success rate percentage (e.g., "99% of orchestrations succeed") and a latency threshold (e.g., "average response time under 2000ms").
Slug¶
A URL-safe identifier for a connector or system (e.g., mercedes-benz-oneapi). Slugs are lowercase, use hyphens instead of spaces, and cannot be changed after publication.
SSO (Single Sign-On)¶
An authentication method where users sign in with their corporate identity provider credentials instead of a separate DIBOP username/password. See SSO / Identity.
Step¶
A single action within an orchestration: API Call, Data Transform, Conditional, or Error Handler. See Step Types.
Stub Connector¶
A connector that returns mock/simulated data instead of calling a real external API. Used for development and testing. Visually indicated with a dashed border and STUB badge.
T¶
Tenant¶
An enterprise using DIBOP. Each tenant has isolated data, users, and configurations. See "Enterprise."
Test Runner¶
A tool for testing connections by executing a series of test cases (connectivity, authentication, API operations, response validation). See Testing Connections.
Token¶
In the context of AI, a unit of text processing (roughly 4 characters or 0.75 words). In the context of authentication, a credential used for API access (e.g., OAuth2 access token, JWT).
V¶
Verified Mapping¶
A field mapping that has been manually confirmed by a human as correct. Verified mappings are marked with a green checkmark. See Field Mapping.
VIN (Vehicle Identification Number)¶
A unique 17-character identifier assigned to every vehicle. The VIN is the primary key in the CDM Vehicle domain.
Visual Builder¶
A drag-and-drop interface for designing orchestrations. See Visual Builder.
W¶
Webhook¶
An HTTP callback that delivers data to a specified URL when an event occurs. DIBOP uses webhooks for alert notifications and can receive webhooks as orchestration triggers.