The API Report CardAPI Index
HotSchedules

HotSchedules API

POS / Hospitality · hotschedules.com

Fourth/HotSchedules gates a patchwork of APIs behind partner enablement, with no self-serve signup; customers email a Fourth representative for each integration. The primary Schedules API uses HTTP Basic Auth and returns only published shifts. Docs sprawl across four portals.

Last verified: July 2026Restaurants & Food Service
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistencePOORA patchwork of Fourth APIs from modern REST to legacy SOAP v3, with no self-serve entry point.
AccessPOORCustomers must email a Fourth representative per integration; credentials are issued separately for each third party.
CoveragePOORThe Schedules API returns only assigned, published shifts; open shifts and historical edits are not surfaced.
AuthPOORThe primary Schedules API still uses HTTP Basic Auth in 2026; only newer APIs get OAuth 2.0.
Docs & DXPOORDocs sprawl across four overlapping portals with no canonical index; partners hit dead links and outdated SOAP pages.
StabilityMIXEDLegacy SOAP v3 still runs alongside newer REST APIs; rate limits are undocumented for most surfaces.
Supergood: HotSchedules has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

HotSchedules scores D on the API Report Card. Fourth/HotSchedules gates a patchwork of APIs behind partner enablement, with no self-serve signup; customers email a Fourth representative for each integration. The primary Schedules API uses HTTP Basic Auth and returns only published shifts. Docs sprawl across four portals.

Tried to integrate with HotSchedules?
SOURCES
No self-serve API access - customers must email a Fourth representative for each new third-party integration, and credentials are scoped per integration, slowing rollouts by weeks help.hotschedules.com
Schedules API only returns assigned/published shifts; open shifts and historical edits are not surfaced, forcing partners to work around the data model or fall back to file exports developer.fourth.com
Schedules API still uses HTTP Basic Auth in 2026 (other Fourth APIs use OAuth), which is a non-starter for many enterprise security reviews and SOC 2-bound partners developer.fourth.com
Multiple overlapping developer portals (developer.fourth.com, developer.bodhi.space, docs.hotschedules.io, learn.hotschedules.com PDFs) with no canonical index - partners regularly hit dead links and outdated SOAP docs docs.hotschedules.io
Long-standing Toast POS <-> Fourth/Adaco inventory integration complaints in the customer community, with customers asking for API exposure that Fourth has not delivered help.hotschedules.com
API access requires production HotSchedules account credentials and Fourth approval for the calling third party, blocking BI tools, EWA providers, and custom internal apps from connecting directly help.hotschedules.com
Timecards GET API v5 went through breaking enhancements in January 2025, forcing partner re-integration help.hotschedules.com
RME GET/Export APIs (inventory/recipe data) require a Fourth representative to enable per-customer; not exposed in customer admin UI help.hotschedules.com
Customer support response times have deteriorated badly post-Marlin/Fourth merger - users report 1-3 day waits across support groups and 6+ hour callback queues vs. historical 2-minute waits help.hotschedules.com
Mobile app reliability issues: defaults to wrong week when clocking in, requires manual date toggling; intermittent login failures and slow loads capterra.com
UI is dated and considered difficult for new managers and hourly employees to learn vs. modern competitors like 7shifts and Homebase fourth.com
Aggressive cancellation policy and difficulty cancelling subscriptions; reports of being billed after cancellation capterra.com
Considered terribly overpriced (especially in Canada) when used 'unintegrated' and without the bundled Fourth modules capterra.com.au
Slow pace of new features post-merger; product roadmap perceived as stagnant while Fourth focuses on enterprise upsell selectsoftwareeviews.com
Integrating with external tools (BI, payroll, EWA, third-party schedulers) is difficult and time-consuming, requires Fourth involvement fourth.com
Periodic system outages tracked on a dedicated status page; multi-region impact when the auth/SSO layer fails help.hotschedules.com