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

U.S. Department of Transportation Safety Issues API

Recalls, Investigations, Complaints, and Manufacturer Communications

U.S. Department of Transportation Safety Issues API is one of 41 APIs that U.S. Department of Transportation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 4 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.6.0.

Requests are made against a single base URL, https://mobile.fmcsa.dot.gov/qc/services.

4 operations 4 paths 13 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.6.0
Base URL
https://catalog.data.faa.gov/api/3
Resource Areas
1

Paths & Operations 4

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

safetyIssues 4

Recalls, Investigations, Complaints, and Manufacturer Communications

GET
/safetyIssues
Get safety issues
getSafetyIssues 2 params → 200400500
GET
/safetyIssues/byDate
Get safety issues by date
getSafetyIssuesByDate 5 params → 200400500
GET
/safetyIssues/byKeywords
Get safety issues by keywords
getSafetyIssuesByKeywords 10 params → 200400500
GET
/safetyIssues/byNhtsaId
Get safety issues by nhtsa id
getSafetyIssuesByNhtsaId 3 params → 200400500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ComplaintAggregate (12 properties), RecallAggregate (11 properties), Pagination (9 properties), InvestigationAggregate (8 properties). Each schema is shown below with its type and property counts.

Meta
object
3 properties
Message
object
4 properties
Investigations
object
2 properties
SafetyIssue
object
7 properties
SafetyIssueAggregateWrapped
object
2 properties
Components
object
1 property
MFRCommunicationAggregate
object
6 properties
Pagination
object
9 properties
Recalls
object
2 properties
ComplaintAggregate
object
12 properties
SafetyIssueAggregate
object
4 properties
RecallAggregate
object
11 properties
InvestigationAggregate
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

us-dot-safetyissues-api-openapi.yml Raw ↑

Other APIs U.S. Department of Transportation publishes across the network.

FAA Data Catalog (CKAN Action API v3)
DOT Data Hub Open Data API
Bureau of Transportation Statistics Open Data API
NHTSA vPIC (Vehicle Product Information Catalog) API
NHTSA Safety API (recalls, complaints, safety ratings)
FRA Safety Data Web Services
FMCSA QCMobile API
U.S. Department of Transportation Air Carrier API
U.S. Department of Transportation Axhsubmitdiscrepancies API
U.S. Department of Transportation Coded Instrument Flight Procedures (CIFP) API
U.S. Department of Transportation Daily Digital Obstacle File (DDOF) API
U.S. Department of Transportation Digital Enroute Charts US (DDECUS) API
Where this information came from

This is an independent, third-party profile of U.S. Department of Transportation Safety Issues 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.