API discovery

OVM API documentation

Public discovery files and the OpenAPI description for the OVM API, for agents, crawlers and technical review. No key is required. Each endpoint below was checked to be serving before it was listed.

One discovery map
Every well-known endpoint is listed in one place, so agents, crawlers and anyone doing technical review start from a single URL rather than probing.
Machine readable first
OpenAPI, contact, services and coverage are published as structured files, so tooling does not have to scrape page content to answer a basic question.
Plain-language notes
Each endpoint is paired with a sentence saying what it is for, which is what makes the set possible to validate rather than merely present.
A route to a person
When a question is about a vehicle, a quote or a service area rather than a file, the team answers the phone.

Endpoints

Discovery endpoints

All relative to https://ovmtransport.com. Every one is a static file served directly, with no authentication required to read it.

Authentication

What the OAuth metadata means here

This website publishes OAuth authorisation server metadata and protected resource metadata so that agent tooling can discover the authorisation model rather than infer it from silence.

In the website-only deployment, the advertised OAuth endpoints deliberately respond with a clear not-implemented status. That is the point: an agent can detect that automated token issuance is not enabled here and stop, instead of retrying against an endpoint that was never going to answer. The discovery files are honest about what exists.

Everything listed above is readable without a token. If you need programmatic access to anything beyond it, talk to us rather than probing for it.

Questions

Common questions

Do I need a key or a token to read these endpoints?

No. Everything listed on this page is a static file served without authentication. The OAuth metadata is published so tooling can discover the authorisation model, not because a token is needed to read the discovery files.

Why do the OAuth endpoints return not implemented?

Because in the website-only deployment they are not implemented. Saying so plainly is more useful than timing out. An agent can detect the status and stop rather than retrying against an endpoint that will never issue a token.

Can I get programmatic access to booking or tracking?

Not from these endpoints, which are read-only discovery and metadata. If you have a genuine integration in mind, speak to us about it rather than probing for something that is not published.

How current is the services and coverage metadata?

It is published from the same source as the service and coverage pages on this site, so the two cannot disagree. If you find a discrepancy, tell us: it is a bug, not a nuance.

Ask a technical question

Integration, discovery or metadata questions come back to the person who maintains these files.

Company or individual

Need service or discovery information?

Use the endpoints above for technical review. If the question is about a vehicle, a quote or a service area, ring 0141 459 1302.