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

Retrieve terminal non-error output events from workflow calls.Outputs are events produced by successful terminal function steps — steps that completedwithout errors and did not spawn further downstream function calls. A single workflow callmay produce multiple outputs (e.g. from a split-then-transform pipeline).Outputs and errors from the same call are not mutually exclusive: a partially-completedworkflow may have both.Use `GET /v3/outputs` to list outputs across calls, or `GET /v3/outputs/{eventID}` toretrieve a specific output. To get outputs scoped to a single call, filter by `callIDs`.

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

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

This API exposes 2 operations across 2 paths, and defines 28 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 28 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 Outputs 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.

Outputs 2

Retrieve terminal non-error output events from workflow calls. Outputs are events produced by successful terminal function steps — steps that completed without errors and did not…

GET
/v3/outputs
List Outputs
v3-list-outputs 18 params → 200
GET
/v3/outputs/{eventID}
Get an Output
v3-get-output 1 param → 200

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are TransformEvent (32 properties), ExtractEvent (27 properties), ParseEvent (27 properties), AnalyzeEvent (22 properties). Each schema is shown below with its type and property counts.

OutputResponseV3
object
1 property 1 required
PayloadShapingEvent
object
Emitted by payloadshaping functions, which restructure JSON payloads using JMESPath expressions configured on the function. The shaped result is carried in tra…
16 properties 5 required
SendEvent
object
21 properties 6 required
AnyType
AnalyzeEvent
object
Emitted by functions of the legacy analyze type (the vision path predecessor of extract). Carries the extracted JSON along with per-field bounding-box metadata…
22 properties 6 required
SplitItemEvent
object
18 properties 5 required
SendEventS3Output
object
Metadata returned when a Send function delivers to an S3 bucket.
2 properties 2 required
EventInboundEmail
object
4 properties 3 required
JoinEventItem
object
4 properties 3 required
JoinEvent
object
22 properties 8 required
ParseEvent
object
Emitted when a parse function completes. Reuses the extract event shape on the wire — both wrap a Transformation and downstream consumers care about the same t…
27 properties 7 required
EvaluationEvent
object
Emitted when a function-accuracy evaluation completes for a transformation. Evaluations are scheduled by POST /v3/eval and run asynchronously; this event repor…
20 properties 8 required
collectionProcessingEvent
object
14 properties 7 required
TransformEvent
object
32 properties 7 required
SendDestinationType
string
Destination type for a Send function.
EventV3
object
V3 read-side event union. Superset of the shared Event union: it contains every shared variant verbatim (backward compatible) and adds the V3-only extract, par…
EnrichEvent
object
16 properties 5 required
ClassifyEvent
object
17 properties 5 required
SendEventWebhookOutput
object
Metadata returned when a Send function delivers to a webhook.
2 properties 2 required
SendDeliveryStatus
string
Outcome of a Send function's delivery attempt.
InputType
string
The input type of the content you're sending for transformation.
ErrorEvent
object
17 properties 5 required
SplitCollectionEvent
object
18 properties 7 required
RenderEvent
object
18 properties 7 required
ExtractEvent
object
V3 event variants that do not exist in the shared Event union. ExtractEvent and ClassifyEvent are emitted only by V3-era function types (extract and classify).…
27 properties 7 required
SendEventGoogleDriveOutput
object
Metadata returned when a Send function delivers to Google Drive.
2 properties 2 required
ListOutputsResponseV3
object
2 properties 2 required
RouteEvent
object
17 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bem-outputs-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 Errors API
Bem Feedback API
Bem File System API
Where this information came from

This is an independent, third-party profile of Bem Outputs 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.