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

Xceptor Workflow Steps API

Operations for managing the individual processing steps that compose a workflow, including step ordering and configuration.

Xceptor Workflow Steps API is one of 14 APIs that Xceptor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Workflow Steps. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 2 operations across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.xceptor.com/v1.

2 operations 1 paths 3 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.xceptor.com/v1
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Xceptor Workflow Steps API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth2 access token obtained via the client credentials flow. Include as a Bearer token in the Authorization header.

Paths & Operations 2

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

Workflow Steps 2

Operations for managing the individual processing steps that compose a workflow, including step ordering and configuration.

GET
/workflows/{workflowId}/steps
Xceptor List Workflow Steps
listWorkflowSteps 1 param → 200401404
POST
/workflows/{workflowId}/steps
Xceptor Add Workflow Step
addWorkflowStep 1 param body → 201400401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are WorkflowStep (6 properties), WorkflowStepCreate (5 properties), Error (3 properties). Each schema is shown below with its type and property counts.

Error
object
An error response from the Xceptor API
3 properties
WorkflowStepCreate
object
Request body for adding a new step to a workflow
5 properties 2 required
WorkflowStep
object
A single processing step within a workflow. Steps are executed in sequence and each performs a specific data processing operation.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xceptor-workflow-steps-api-openapi.yml Raw ↑

Other APIs Xceptor publishes across the network.

Xceptor Workflow API
Xceptor Document Upload API
Xceptor Data Export API
Xceptor Connector API
Xceptor Authentication API
Xceptor Data Sources API
Xceptor Documents API
Xceptor Extraction API
Xceptor Health API
Xceptor Jobs API
Xceptor Templates API
Xceptor Workflow Runs API
Where this information came from

This is an independent, third-party profile of Xceptor Workflow Steps 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.