An open companion standard to the APDS 4.1 API. APX adds what APDS deliberately leaves out — real-time delivery, operational control, alerting, discovery, and the business domains built on them — without redefining a single APDS entity.
Every domain APX defines, grouped the way the reference groups them. Each links to its section of the API reference and to the part of the written standard that governs it. Generated from the specification on every build, so this list is never out of date.
Where every integration starts. A partner needs exactly one thing to begin: a hostname.
Push instead of poll. A superset-compatible profile of the APDS 4.1 /webhooks endpoint: stock APDS subscription bodies work here unmodified.
Doing things in the real world. APDS inventories devices and marks access-controlled places but defines no actuation. This is it.
Knowing something is wrong. A net-new domain: APDS has no alert, event, or notification class.
A location, described by APX alone. Before a call, an agent or a system should be able to learn what a site has without data from any other system: which hardware is on each lane and what each piece does, what it is, what runs on it, where the cameras are and what they see, how a parker reaches help from each lane or door, and who to escalate to.
The vendor's own screen, without breaking the record. Most actions in a call centre still happen in a vendor's portal in another window, and the two systems never agree afterwards. A vendor will take years to implement every APX module, but it already has good screens.
Money. Account and balance lookup, taking a payment, refunds, voids and captures, accounting write-back, and payment history.
Booking ahead, expressed as conventions over native APDS routes rather than a parallel booking system.
Pooled permits: issuing from a finite allocation, over the APDS right-specification and right-pool model.
Plates. A camera read is an APDS Observation, so ingest is the standard data route every integration already uses. No bespoke ingestion API.
The card, the fob, the tag, the phone. The lifecycle of anything presented at a lane: issue, activate, suspend, resume, report lost, revoke, replace, plus access-event history.
Custody. A net-new domain: APDS has no valet entity, only a restriction flag.
Enforcement, from camera to citation to appeal. A net-new domain, and the one with the most legal exposure.
When a customer presses the intercom. The agent, human or AI, should not have to log into another system, find the facility, find the lane, find the transaction, and reconstruct what happened.
What happened on the last call. Support-interaction history for a resolution context: who spoke to the customer, through which channel, about what, and what was done.
apx-v1.yamlFull standard · OpenAPI 3.1 · YAML
apx-v1.jsonFull standard · OpenAPI 3.1 · JSON
apx-parcs.jsonPARCS starter profile · JSON
registries/Code-list registries · Part 11
apx-standard.mdThe written standard · one document
specification/The six specification documents · HTML and PDF
edition.jsonWhat this edition pins, by checksum
These are the bundled, normative artifacts, regenerated from source on
every push to main. Import one into Postman, Insomnia, or
your own code generator.
git clone https://github.com/rneubauer/apx.git
cd apx && npm install
npm test # the full gate: vendor, registries, lint, bundle, examples, scenarios
npm run mock # Prism mock server on :4010, generated from the spec
npm run docs:build # rebuild this site into site/The mock server answers every documented route with schema-valid responses, so a client integration can be written and tested before any real implementation exists. Send any bearer token.