Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Accept Businessservices API

The Businessservices API from Accept — 3 operation(s) for businessservices.

Accept Businessservices API is one of 23 APIs that Accept publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Businessservices. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and an AsyncAPI specification.

This API exposes 3 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 1.1.0-rc.1.

Requests are made against a single base URL, http://localhost:8080.

3 operations 3 paths 6 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.1.0-rc.1
Base URL
https://midas.accept.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Accept Businessservices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Static bearer token. Configured via MIDASAUTHTOKENS or midas.yaml auth.tokens. Not required when auth.mode=open (development only).

Paths & Operations 3

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

Businessservices 3
GET
/v1/businessservices
List all business services
listBusinessServices → 200401403501
GET
/v1/businessservices/{id}
Get a business service by ID
getBusinessServiceById 1 param → 200401403404501
GET
/v1/businessservices/{id}/relationships
List business-service relationships
listBusinessServiceRelationships 1 param → 200401403404500501

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are BusinessService (11 properties), BusinessServiceRelationship (8 properties), ExternalRef (5 properties), BusinessServiceRelationshipsResponse (3 properties). Each schema is shown below with its type and property counts.

BusinessServiceRelationshipsResponse
object
Top-level response shape for GET /v1/businessservices/{id}/relationships. Outgoing rows are those where the queried service is the source; incoming rows are th…
3 properties 3 required
ExternalRef
object
Structured reference to an entity in an external system (ServiceNow, LeanIX, GitHub, internal catalogues, custom). MIDAS records the reference but never valida…
5 properties 2 required
Error
object
1 property 1 required
BusinessServicesResponse
object
Envelope wrapping the GET /v1/businessservices list payload. The businessservices array is always present (never null); empty store returns []. The envelope sh…
1 property 1 required
BusinessService
object
A business service grouping for processes (V2 structural layer). Mirrors the businessServiceResponse wire format.
11 properties
BusinessServiceRelationship
object
A directed link between two BusinessServices (Epic 1, PR 1). The junction has no lifecycle of its own; description is the only mutable field.
8 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

accept-businessservices-api-openapi.yml Raw ↑

Other APIs Accept publishes across the network.

Accept Agents API
Accept Aisystems API
Accept Capabilities API
Accept Controlplane API
Accept Coverage API
Accept Decisions API
Accept Drift API
Accept Envelopes API
Accept Escalation Targets API
Accept Escalations API
Accept Evaluate API
Accept Evidence API