Skip to main content
Alongside the Scheduling API — which plays the Slot Aggregator role — haau3 also operates a small Slot Publisher: its own SMART Scheduling Links $bulk-publish feed of provider availability.

​
A reference feed, not a product

The Slot Publisher is primarily a contribution to the open SMART Scheduling Links standard — a real, conformant reference feed that publishers, clients, and tooling can validate against. It is not a billed platform API and is not part of the B2B product surface. The product is the aggregator (the Scheduling API). Because an SSL feed is meant to be openly fetchable, the publisher requires no API key — unlike the /v1/scheduling/* aggregator endpoints, which are key-authenticated.

​
Why it’s hosted on the platform

Hosting the feed at api.haau3.com lets any organization evaluating the haau3 Scheduling API test a direct connection to a real Slot Publisher with zero setup — point your own client, ingestion worker, or public SSL tooling at a single URL instead of standing up a feed or integrating a third party. It’s the simplest way to see the publisher → aggregator → client flow end to end. Our own aggregator ingests this same feed, so what you fetch directly here is exactly what flows into GET /v1/scheduling/slots under the haau3 publisher slug. You can compare the two sides: the raw publisher feed, and the normalized, unified result the aggregator serves.

​
Endpoints

Both are public (no API key) and serve non-PHI synthetic data.
  • GET https://api.haau3.com/scheduling/$bulk-publish — the $bulk-publish manifest (transactionTime + an output[] array of absolute NDJSON file URLs).
  • GET https://api.haau3.com/scheduling/{Resource}.ndjson — one newline-delimited JSON file per resource type (Location, Practitioner, PractitionerRole, Schedule, Slot), served as application/fhir+ndjson.
# Read the manifest, then fetch the slots it lists — no key required.
curl https://api.haau3.com/scheduling/\$bulk-publish
curl https://api.haau3.com/scheduling/Slot.ndjson

​
What’s in the feed

A small, curated dataset built to exercise representative SSL scenarios so you can see how each maps through the aggregator:
  • Virtual vs in-person appointments (Location.physicalType).
  • Accepting-patients states: new patients, existing patients only, existing patients and families, and a not-accepting example (the aggregator stores it but never serves it).
  • Multiple service types and provider specialties (HL7 service-type and NUCC codes).
  • Booking deep links and phone numbers (SSL booking extensions).
The data conforms to the SSL profiles — it passes the same base-FHIR and profile validation the aggregator applies on ingest — so it’s a safe, predictable target for testing a Slot Discovery Client or your own aggregator. Slot times fall within the current demo window; the dataset is synthetic reference data, not live availability.

​
How it relates to the aggregator

Slot Publisher (this feed)Scheduling API (aggregator)
RolePublishes one provider’s availabilityCombines many publishers into unified search
Endpoint/scheduling/$bulk-publish (+ NDJSON)/v1/scheduling/slots (+ publishers, service-types)
AuthPublic, no keyAPI key required
FormatRaw FHIR NDJSONDenormalized Slot JSON
PurposeOpen-standard reference / direct-connection testingThe haau3 B2B product
To consume the aggregator instead, start with the Quickstart and the SMART Scheduling Links overview.