Bem Entity Curation API
Curate the knowledge graph by transitioning entities through their reviewlifecycle and editing their metadata.- **`PATCH /v3/entities/{id}`** updates a single entity. Every field is optional but at least one is required: - `status` transitions curation state to `approved` or `rejected` (only from `extracted`/`proposed`; any other transition is `409 Conflict`). Approving emits an `entity_validated` webhook; rejecting emits `entity_rejected`. - `assignedTypeID` sets (or, with the empty string, clears) the customer-assigned type that overrides the bem-inferred type. - `canonical` replaces the canonical surface form. - `addSynonyms` / `removeSynonymIDs` attach `customer_defined` synonyms or soft-delete existing ones (an `extracted` synonym cannot be removed — `409 Conflict`). A merged-away entity id transparently resolves to its surviving canonical entity.- **`POST /v3/entities/bulk-validate`** transitions a batch of entities to `approved` or `rejected` in one request. Each row reports `validated`, `skipped` (not found / not authorized), or `rejected-row` (an illegal transition such as an already-terminal entity), alongside a summary.On the dashboard (JWT) surface these actions additionally require theacting user to be an assigned reviewer for the entity's effective type, orto hold the `admin` role (or higher). On the API-key surface admin-keyauthorization applies and no per-user reviewer check is made.
Bem Entity Curation API is one of 22 APIs that Bem publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Entity Curation. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 2 operations across 2 paths, and defines 6 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Bem Entity Curation 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 2
Across 2 paths, the API surfaces 2 operations — 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Curate the knowledge graph by transitioning entities through their review lifecycle and editing their metadata. - PATCH /v3/entities/{id} updates a single entity. Every field is o…
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are EntityResponseV3 (12 properties), UpdateEntityRequestV3 (6 properties), BulkValidateSummaryV3 (3 properties), BulkValidateRowResultV3 (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Bem 12
Other APIs Bem publishes across the network.
This is an independent, third-party profile of Bem Entity Curation 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.