Bem Entity Bulk Seed API
Seed the knowledge graph with a batch of customer-authored canonicalentities in one request — their types, descriptions, synonyms, andper-entity attributes.- **`POST /v3/entities/bulk`** creates or merges each entity into a single bucket (the optional `bucket` reference, else the account+environment default). For each row the entity's `type` is resolved or created in your taxonomy, the entity is upserted on its normalized canonical, and any `synonyms` are attached as `customer_defined`. An entity that already exists is **merged** (`onConflict: "merge"`): synonyms are added additively, a longer `description` replaces the old one, and `attributes` are merged with new keys winning.- Small batches (fewer than 100 entities) process **synchronously** and return `200` with a per-row `results` array and a `summary`.- Larger batches process **asynchronously**: the call returns `202` with a `seedJobID` and a `statusURL`. Poll **`GET /v3/entities/seed/{id}`** until `status` is `completed` (or `failed`); the completed response includes the per-row `results`.Each row's outcome is one of `created`, `merged-with`, or `rejected` (witha `reason`, e.g. an attribute key not declared in the type's schema).
Bem Entity Bulk Seed 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 Bulk Seed. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 2 operations across 2 paths, and defines 7 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 Bulk Seed 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 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Seed the knowledge graph with a batch of customer-authored canonical entities in one request — their types, descriptions, synonyms, and per-entity attributes. - POST /v3/entities/…
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SeedJobStatusResponseV3 (8 properties), BulkSeedEntityInputV3 (5 properties), SeedRowResultV3 (4 properties), BulkSeedEntitiesRequestV3 (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 Bulk Seed 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.