Create and resolve issues (defects) via the Fleetio API
domain: developer.fleetio.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a new issue with POST /issues, describing the one-time problem or repair (e.g., a leak, breakdown, or failed inspection item) and associating it with a vehicle.
List issues with GET /issues to review open or unresolved defects, and retrieve a single one with GET /issues/:id.
Update issue details, such as description or priority, with PUT or PATCH /issues/:id as more information becomes available.
Resolve an issue with PUT /issues/:id/resolve once the underlying problem has been fixed.
Alternatively close an issue with PUT /issues/:id/close, or reopen a previously closed or resolved issue with PUT /issues/:id/reopen.
Known gotchas
Resolve, close, and reopen are distinct state-transition actions, not plain field updates — the issue must already be in an appropriate state for the transition to succeed, or the API returns a 422.
Issue Priorities are a separate reference resource; assigning a priority means referencing an existing Issue Priority record rather than passing free-text.
Deleting an Issue is a separate, permanent action from resolving or closing it — resolving preserves the record while deleting removes it entirely.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?