OneRail Dynamic Routing Config API
The DynamicRoutingConfig API from OneRail — 1 operation(s) for dynamicroutingconfig.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/onerail-dynamicroutingconfig-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Onerail Dynamic Routing Config API
version: 1.0.0
license:
name: UNLICENSED
url: ''
description: 'Operations tagged DynamicRoutingConfig across 2 of this provider''s published API definitions: onerail-dynamicroutingconfig-api-openapi.yml, onerail-operations-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: /
description: Default relative server URL
security:
- bearer: []
tags:
- name: DynamicRoutingConfig
paths:
/v1/organization/{organizationId}/dynamic-routing-configs:
parameters:
- name: organizationId
in: path
required: true
description: organizationId
schema:
type: string
get:
x-exegesis-controller: DynamicRoutingConfig
summary: Get organization's Dynamic Routing Configs
operationId: getAll
tags:
- DynamicRoutingConfig
responses:
'200':
description: Dynamic Routing Configurations
content:
application/json:
schema:
type: array
items:
$ref: '#/paths/~1v1~1organization~1%7BorganizationId%7D~1dynamic-routing-configs/put/requestBody/content/application~1json/schema/items'
'400':
$ref: '#/paths/~1v1~1routes/get/responses/404'
'500':
$ref: '#/paths/~1v1~1routes/get/responses/404'
put:
x-exegesis-controller: DynamicRoutingConfig
summary: Update Dynamic Routing Configurations
operationId: updateAllDynamicRoutingConfigs
tags:
- DynamicRoutingConfig
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
type: object
properties:
id:
type: string
format: uuid
name:
type: string
description: Name of the dynamic routing config
locationId:
type: string
format: uuid
marketId:
type:
- string
- 'null'
format: uuid
radiusMiles:
type:
- number
- 'null'
description: Radius in miles
activeAt:
type:
- string
- 'null'
format: date-time
description: Date when the config becomes active
activeUntil:
type:
- string
- 'null'
format: date-time
description: Date when the config becomes inactive
serviceLevelIds:
type: array
items:
type: string
format: uuid
vehicles:
type: array
items:
type: object
required:
- userId
properties:
ownFleetVehicleId:
type: string
format: uuid
description: Own fleet vehicle ID
userId:
type:
- string
- 'null'
format: uuid
description: Driver user ID (optional, can be null)
createdAt:
type: string
format: date-time
updatedAt:
type: string
format: date-time
_deleted:
type:
- boolean
- 'null'
description: Whether the config is deleted
responses:
'200':
description: Dynamic Routing Configurations updated successfully
content:
application/json:
schema:
type: array
items:
$ref: '#/paths/~1v1~1organization~1%7BorganizationId%7D~1dynamic-routing-configs/put/requestBody/content/application~1json/schema/items'
'400':
$ref: '#/paths/~1v1~1routes/get/responses/404'
'500':
$ref: '#/paths/~1v1~1routes/get/responses/404'
servers:
- url: /
description: Default relative server URL
components:
securitySchemes:
bearer:
type: http
scheme: bearer
description: 'Standard JWT bearer token used for authenticated OmniPoint users
and internal service-to-service calls. Clients send `Authorization: Bearer <jwt>`
and the token is validated using the shared Core access token secret.
'
ApiKey:
type: apiKey
in: header
name: X-ONERAIL-API-KEY
description: 'Shared secret key used for machine-to-machine integrations. Must be sent
together with `X-ONERAIL-APP-ID` and is validated against the stored ApiAuth
record for that application.
'
AppId:
type: apiKey
in: header
name: X-ONERAIL-APP-ID
description: 'Application identifier (UUID) that pairs with `X-ONERAIL-API-KEY` for
machine-to-machine integrations. Both headers are required for ApiKey-based
authentication.
'
OAuth:
type: oauth2
description: 'OAuth 2.0 access token validated by the Operations service (e.g. Okta-backed
integrations). Clients obtain tokens from their own IdP outside of this API
and call endpoints with `Authorization: OAuth <access_token>`. The
`authorizationUrl` and `tokenUrl` values below are placeholders only to
satisfy the OpenAPI schema; this service does not call them directly and the
real IdP URLs are configured via environment and introspection logic in code.
'
flows:
authorizationCode:
authorizationUrl: https://dummy-unused-url.com
tokenUrl: https://dummy-unused-url.com
scopes: {}
x-refined-from:
- onerail-dynamicroutingconfig-api-openapi.yml
- onerail-operations-api-openapi.yml