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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cedarai

Cedarai Equipment History API

The Equipment History API from Cedarai — 1 operation(s) for equipment history.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cedarai Equipment History API is one of 9 APIs that Cedarai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Equipment History. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 51 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api-lg.arms.cedarai.com, https://api-lg.arms.cedarai.se.

1 operations 1 paths 51 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api-lg.arms.cedarai.com
Authentication
API Key, API Key
License
Proprietary
Resource Areas
1

Authentication & Security 2

Cedarai Equipment History API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-arms-api-key (ApiKeyAuth). An API key is passed in the header as x-arms-assume-user (AssumeUser). By default, every request must be authenticated.

  • ApiKeyAuth — Your ARMS API key
  • AssumeUser — Email of a user assigned to the appropriate user group

Paths & Operations 1

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

Equipment History 1
POST
/equipment-history/
List railcar history
listEquipmentHistory 2 params body → 200400401500default

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are Waybill (68 properties), UmlerCommon (67 properties), EquipmentDetails (26 properties), EquipmentHistoryItem (21 properties). Each schema is shown below with its type and property counts.

WagonDamage
object
6 properties
ListEquipmentHistoryInput
object
17 properties 1 required
EquipmentHistoryItem
object
21 properties
BillingInformation
object
4 properties
HazmatShippingNameInformation
object
4 properties
Party
object
18 properties
InterchangeMoveAuthority
object
Interchange move authority on equipment (X12 IMA).
5 properties
AttributesBase
object
Base attribute payload for grouping resources.
RouteEntry
object
6 properties
Release
object
3 properties
IntermodalUnitResource
object
3 properties
HazardousCertification
object
1 property
EmptyCarDisposition
object
9 properties
AdministrativeContact
object
4 properties
Measurement
object
12 properties
HazardousInformation
object
21 properties
EquipmentDetails
object
26 properties
HistoryGroupingNameFilter
object
2 properties 2 required
WaybillSearchFilterCore
object
8 properties
CrossReferenceEquipment
object
10 properties
PriceAuthority
object
13 properties
Umler
Station
object
6 properties
HistoryMoveType
string
Error
object
1 property
LineItemQuantity
object
11 properties
CommunicationNumber
object
2 properties
EquipmentLineItem
object
Per-commodity line on equipment shipment information (X12 417 N1 loop). Used for Carta Porte on cross-border waybills; quantity is a flat number, not the neste…
13 properties
HazardousClassificationInformation
object
13 properties
Equipment
object
18 properties
LineItem
object
5 properties
ProtectiveService
object
13 properties
Grouping
object
12 properties 7 required
EquipmentParentGrouping
object
8 properties
IntermodalStatusDetails
object
2 properties
ExtendedReferenceInformation
object
Extended reference information from the waybill. Production notes are entries where referenceIdQualifier is "ZZ" and description is "TrpNotes"; the note text i…
5 properties
ListEquipmentHistoryOutput
object
3 properties 1 required
GroupingRule
object
Optional grouping rule configuration.
Terminal
object
Port or terminal location on equipment (X12 R4).
4 properties
Waybill
object
68 properties
HazmatReferenceNumber
object
3 properties
EquipmentShipmentInformation
object
Per-equipment customs and tariff block (Carta Porte). Required on cross-border US–Mexico waybills; attach under waybill.equipmentDetails[], not waybill.lineIte…
5 properties
CanadianDangerousRequirements
object
15 properties
UmlerCommon
object
Shared UMLER attributes for equipment records.
67 properties
WorkOrderResource
object
8 properties
ReferenceInfo
object
3 properties
RelaxedEquipment
HazmatFreeFormInformation
object
8 properties
TransborderHazardousRequirements
object
3 properties
EPARequiredData
object
4 properties
LineItemDescription
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cedarai-equipment-history-api-openapi.yml Raw ↑

Other APIs Cedarai publishes across the network.

Cedarai ChargeService API
AE Profile APIs.io
Cedarai Ims API
AE Profile APIs.io
Cedarai InvoicesService API
AE Profile APIs.io
Cedarai LindaService API
AE Profile APIs.io
Cedarai NetworkStructureService API
AE Profile APIs.io
Cedarai QuotesService API
AE Profile APIs.io
Cedarai TruckLoadTenderService API
AE Profile APIs.io
Cedarai WorkOrderService API
AE Profile APIs.io
#Equipment History
← Back to C APIs
API Details
ID
cedarai:cedarai-equipment-history-api
Base URL
https://api-lg.arms.cedarai.com
Docs
https://docs.cedarai.com/user-docs/api-reference/introduction
Provider
Cedarai
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cedarai-equipment-history-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cedarai-equipment-history-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cedarai Equipment History 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.