Roadie Entity Push API
Create, delete, and idempotently manage Roadie-owned catalog entities and entity sets.
Roadie Entity Push API is one of 6 APIs that Roadie publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Entity Push. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 5 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against a single base URL, https://api.roadie.so/api.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Roadie Entity Push API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Roadie API token (User Token or Service Token) created under Administration in the Roadie app. Passed as Authorization: Bearer YOURROADIEAPITOKEN.
Paths & Operations 5
Across 3 paths, the API surfaces 5 operations — 2 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Create, delete, and idempotently manage Roadie-owned catalog entities and entity sets.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Entity (5 properties), Error (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Roadie 5
Other APIs Roadie publishes across the network.