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

OneRail User API

The User API from OneRail — 17 operation(s) for user.

OneRail User API is one of 75 APIs that OneRail publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 24 operations across 17 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, /.

24 operations 17 paths 2 schemas 2 DELETE11 GET8 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://onerail-delivery-api-prod.azurewebsites.net
Authentication
API Key, API Key, API Key, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 5

OneRail User API declares 5 security schemes for authenticating requests. An API key is passed in the header as X-ONERAIL-API-KEY (ApiKey). An API key is passed in the header as X-ONERAIL-APP-ID (AppId). An API key is passed in the header as X-ONERAIL-API-KEY-AND-APP-ID (ApiKeyAndAppId). It accepts HTTP bearer tokens (bearer). It supports OAuth 2.0 (OAuth) using the authorizationCode flow.

  • bearer — Standard JWT bearer token used for authenticated OmniPoint users and internal service-to-service calls. Clients send Authorization: Bearer and the token is val…
  • OAuth — 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 ca…

Paths & Operations 24

Across 17 paths, the API surfaces 24 operations — 2 DELETE, 11 GET, 8 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

User 24
POST
/user/authenticate
Creates and returns an authentication token
authenticate body → 200401default
GET
/v1/organization/{organizationId}/user/status
Gets driver status
getUserStatus 3 params → 200default
POST
/v1/user
Creates a new User
createUser body → 200default
GET
/v1/user/{userId}
Get user's record
getUser 1 param → 200default
PUT
/v1/user/{userId}
Update user's record
updateUser 1 param body → 200default
DELETE
/v1/user/{userId}
Deletes User
removeUser 1 param → 200default
GET
/v1/user/{userId}/welcome-email
Resend welcome email
welcomeEmail 1 param → 200default
POST
/v1/user/{userId}/roles
Update user roles
updateRoles 1 param body → 200default
GET
/v1/user/{userId}/roles
Get all user's roles and permissions
getUserRoles 1 param → 200default
GET
/v1/user/{userId}/roles/api
Get all user's roles and permissions (API)
getUserRolesApi 1 param → 200default
GET
/v1/user/{userId}/permissions
Get All user's permissions across all roles. Only displays permissions to loggin user.
getPermissions 1 param → 200default
POST
/v1/user/fleet/{fleetId}/last-known-driver-location
Updates a user's last known geo location by fleet id
updateFleetLastKnownLocation 1 param body → 200default
POST
/v1/user/{userId}/user-view
Create user view filter
createUserView 1 param body → 200default
GET
/v1/user/{userId}/user-view/{userViewId}
Get user view filter
getUserView 2 params → 200default
PUT
/v1/user/{userId}/user-view/{userViewId}
Update User View filter
updateUserView 3 params body → 200default
DELETE
/v1/user/{userId}/user-view/{userViewId}
Delete User View filter
deleteUserView 2 params → 200default
GET
/v1/user/{userId}/user-views
Get all user views filter
getAllUserView 6 params → 200default
PUT
/v1/user/{userId}/user-views/cardinality
Bulk update user view order
bulkUpdateUserViewCardinality 1 param body → 200400404default
GET
/v1/user/policy-check
check if latest privacy policy accepted by User
checkPolicy → 200default
POST
/v1/user/policy-accept
Update policy accept
updatePolicyAccept body → 200default
POST
/v1/organization/{organizationId}/user/{userId}/roles
Update user roles
updateUserOrganizationRoles 2 params body → 200default
GET
/v1/organization/{organizationId}/user/{userId}/roles
Get all user's roles and permissions for the specified organization
getUserOrganizationRoles 2 params → 200default
POST
/v1/location/{locationId}/user/{userId}/roles
Update user roles
updateUserLocationRoles 2 params body → 200default
GET
/v1/location/{locationId}/user/{userId}/roles
Get all user's roles and permissions for the specified location
getUserLocationRoles 2 params → 200default

Schemas 2

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

UserCredentials
object
3 properties 2 required
Error
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onerail-user-api-openapi.yml Raw ↑

Other APIs OneRail publishes across the network.

OneRail Delivery API
OneRail Api Auth API
OneRail Assets API
OneRail Associated Location API
OneRail Authentication API
OneRail Blob Storage API API
OneRail Box API
OneRail Bulk Approve SLA Template API
OneRail Bulk Send SLA Template API
OneRail Bulk Uploads API
OneRail Cancellation Reason API
OneRail Carrier API
Where this information came from

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