# AppyWay

> AppyWay maps and prices UK kerbside space. Its APIs answer where a vehicle can park or
> load, for how long, at what cost, and under which local-authority regulation — plus
> bulk GIS extracts of an authority's traffic restrictions. The public surface is
> read-only, key-gated, and served from api.appyway.com.

Generated by API Evangelist on 2026-09-04 from AppyWay's own published contracts and
documentation. AppyWay does not serve an llms.txt of its own — /llms.txt returns 404 on
appyway.com, docs.appyway.com, api.appyway.com and every application host.

## Access

Authentication is a single API key sent in the `API-KEY` request header. There is no
self-serve signup, no OAuth for the API, and no test key: keys are issued by AppyWay on
request to apisupport@appyway.com. A missing or invalid key returns 401; a valid key
without entitlement to the requested local authority returns 403.

Base URL pattern: `https://api.appyway.com/{version}/{section}/{endpoint}` (v1 only).

- Authentication guide: https://docs.appyway.com/docs/public-docs/50055c042f423-authentication
- Getting started: https://docs.appyway.com/docs/public-docs/6465709b0f811-getting-started
- Rate limiting: https://docs.appyway.com/docs/public-docs/319adf4695d05-rate-limiting

## The four APIs

- Explorer — https://api.appyway.com/v1/explorer — 18 operations. Search parking rules
  and prices by map viewport or by entity id, for a specific vehicle operator context.
  Reference: https://docs.appyway.com/docs/public-docs/c655badabdcf0-explorer-api
- Reference — https://api.appyway.com/v1/reference — 26 operations. The controlled
  vocabularies every id field points into: vehicle types, fuel types, permit types,
  restriction types, payment methods, countries, regions and 16 more.
  Reference: https://docs.appyway.com/docs/public-docs/f19a03a1ac8f5-reference
- Traffic Data — https://api.appyway.com/v1/traffic-data — 9 operations. Bulk fetch of
  an authority's on-street restrictions, plus GeoJSON and DXF exports and an OGC Web
  Feature Service query route.
- Availability RealTime — https://api.appyway.com/v1/availability-realtime — 2
  operations. Live occupancy for a list of known entity ids.
  Reference: https://docs.appyway.com/docs/public-docs/dc52a602db4c8-availability-real-time

## Machine-readable contracts

AppyWay publishes OpenAPI 3.0.1 for all four APIs, in JSON and YAML, alongside first-party
Postman collections, in its own public repository:
https://github.com/YellowLineParking/Public-Api-Specs

Each platform deployment republishes them; the most recent contract change was 2026-08-24.

## What an agent should know before calling

- Every published operation is a READ. There is no create, update or delete anywhere in
  the four contracts, so nothing an agent calls here can be wrong in a way that needs
  undoing. Idempotency, dry-run and reversibility are all not-applicable rather than missing.
- POST is a query transport, not a mutation signal. `fetchAllCountries` and
  `findParkingQuotesByViewport` are POSTs that read.
- Responses are wrapped: `{"success": true, "result": {...}}`. Errors are
  `{"success": false, "message": "...", "errors": [{"property","code","message"}]}`.
  This is not RFC 9457 problem+json.
- Dates are ISO 8601, always returned in UTC. Durations are strings shaped
  `[-][d.]hh:mm:ss[.fffffff]`.
- There is no pagination anywhere. Bound a read by id list or by map viewport instead.
- The 25 Reference API reads support conditional requests (304 Not Modified); the other
  three APIs do not.
- Rate limits are real but unpublished, differ per endpoint, and surface as 429 with no
  RateLimit-* or Retry-After headers. Back off exponentially with jitter.
- Coverage is not uniform. A 404 on a by-id read may mean the kerbside was never mapped,
  not that it was removed. Explorer viewport searches return a `generalOnStreetPolicy`
  field — Restricted, LikelyRestricted, LikelyUnrestricted or Unknown — as an explicit
  low-confidence signal for unmapped kerb. Do not present it to an end user as a rule.
  https://docs.appyway.com/docs/public-docs/b4b7059341a23-how-to-interpret-gaps-in-parking-data

## Embeddable applications

Three hosted single-page applications embed by iframe rather than by SDK:
Explorer (https://hub.appyway.com/explorer, query-string configurable),
Streets (https://streets.appyway.com/{authority}) and
Public Consultation (https://consultation.appyway.com/{authority}).

## What AppyWay does not publish

- No client SDK in any language. The 14 first-party NuGet packages under
  github.com/YellowLineParking are .NET infrastructure libraries, not API clients.
- No MCP server, no A2A agent card, no AsyncAPI, no webhooks, no gRPC, no WSDL.
- No public pricing. Commercial terms are arranged directly with AppyWay.
- No status page, no SLA, no deprecation policy and no changelog page. Contract change is
  observable only by diffing the GitHub spec repository.
- No security.txt, no vulnerability-disclosure programme and no trust centre.

## Company

- Website: https://appyway.com
- Blog: https://appyway.com/blog/
- Case studies: https://appyway.com/case-studies/
- Integrations: https://appyway.com/integrations
- GitHub: https://github.com/YellowLineParking
- Support: apisupport@appyway.com