How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bem Connectors API

Connectors are integrations that trigger a Bem workflow from an external system.A connector binds an inbound source — currently Box or a Paragon-managed integration such asGoogle Drive — to a specific workflow (by `workflowName` or `workflowID`). When the sourceobserves a new file, Bem invokes the bound workflow against that file.Use these endpoints to create, list, and remove connectors. The fields used at create timedepend on the connector `type`: Box connectors require Box credentials and a folder to watch,while Paragon connectors carry a `paragonIntegration` identifier and an integration-specific`paragonConfiguration` object (for example, `{ "folderId": "..." }` for Google Drive).

Bem Connectors API is one of 22 APIs that Bem publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Connectors. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.bem.ai, https://api.eu1.bem.ai.

3 operations 2 paths 4 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.bem.ai
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Bem Connectors API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (API Key). By default, every request must be authenticated.

  • API Key — Authenticate using API Key in request header

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Connectors 3

Connectors are integrations that trigger a Bem workflow from an external system. A connector binds an inbound source — currently Box or a Paragon-managed integration such as Googl…

POST
/v3/connectors
Create a Connector
v3-create-connector body → 200
GET
/v3/connectors
List Connectors
v3-list-connectors 2 params → 200
DELETE
/v3/connectors/{connectorID}
Delete a Connector
v3-delete-connector 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ConnectorV3 (12 properties), ConnectorCreateRequestV3 (10 properties), ConnectorListResponseV3 (1 property). Each schema is shown below with its type and property counts.

ConnectorCreateRequestV3
object
Request body to create a connector.
10 properties 2 required
ConnectorListResponseV3
object
Response body for listing connectors.
1 property 1 required
ConnectorV3
object
A Connector represents an integration that triggers a Bem workflow from an external system.
12 properties 12 required
ConnectorTypeV3
string
Connector type.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bem-connectors-api-openapi.yml Raw ↑

Other APIs Bem publishes across the network.

Bem Buckets API
Bem Calls API
Bem Collections API
Bem Entity Bulk Seed API
Bem Entity Curation API
Bem Entity Synonyms API
Bem Entity Type Reviewers API
Bem Entity Types API
Bem Errors API
Bem Feedback API
Bem File System API
Bem Function Accuracy API
Where this information came from

This is an independent, third-party profile of Bem Connectors API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.