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 Errors API

Retrieve terminal error events from workflow calls.Errors are events produced by function steps that failed during processing. A single workflowcall may produce multiple error events if several steps fail independently.Errors and outputs from the same call are not mutually exclusive: a partially-completedworkflow may have both.Use `GET /v3/errors` to list errors across calls, or `GET /v3/errors/{eventID}` to retrievea specific error. To get errors scoped to a single call, filter by `callIDs`.

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

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

This API exposes 2 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.

2 operations 2 paths 4 schemas 2 GET

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 Errors 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 — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Errors 2

Retrieve terminal error events from workflow calls. Errors are events produced by function steps that failed during processing. A single workflow call may produce multiple error e…

GET
/v3/errors
List Errors
v3-list-errors 11 params → 200
GET
/v3/errors/{eventID}
Get an Error
v3-get-error 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ErrorEvent (17 properties), EventInboundEmail (4 properties), ListErrorsResponseV3 (2 properties), ErrorEventResponseV3 (1 property). Each schema is shown below with its type and property counts.

ListErrorsResponseV3
object
2 properties 2 required
ErrorEvent
object
17 properties 5 required
ErrorEventResponseV3
object
1 property 1 required
EventInboundEmail
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bem-errors-api-openapi.yml Raw ↑

Other APIs Bem publishes across the network.

Bem Buckets API
Bem Calls API
Bem Collections API
Bem Connectors API
Bem Entity Bulk Seed API
Bem Entity Curation API
Bem Entity Synonyms API
Bem Entity Type Reviewers API
Bem Entity Types 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 Errors 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.