The API Report CardAPI Index
Sling

Sling API

POS / Hospitality · getsling.com

Sling ships a documented public REST API at api.getsling.com with a Swagger UI, self-serve for any admin account. The OAuth2 refresh-token flow is openly broken, forcing full re-login when hourly access tokens expire. No webhooks and no published rate limits, so integrations poll.

Last verified: July 2026HR & Payroll
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA documented public REST API at api.getsling.com with a Swagger UI and example scripts on GitHub.
AccessMIXEDSelf-serve for any Sling admin account, but there is no formal partner program or ISV listing.
CoverageMIXEDShifts, timesheets, time off, availability, and messaging are covered; with no webhooks, everything is polled.
AuthPOOROAuth refresh flow is broken, forcing a full re-login when tokens expire, and the legacy token arrives only in a response header.
Docs & DXMIXEDThe Swagger UI lists endpoints but schemas and error codes run thin; the GitHub docs repo is marked as a WIP migration.
StabilityMIXEDNo published rate limits; integrators discover throttling through 429s with no documented backoff guidance.
Supergood: Sling has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Sling scores C on the API Report Card. Sling ships a documented public REST API at api.getsling.com with a Swagger UI, self-serve for any admin account. The OAuth2 refresh-token flow is openly broken, forcing full re-login when hourly access tokens expire. No webhooks and no published rate limits, so integrations poll.

Tried to integrate with Sling?
SOURCES
OAuth refresh-token flow is broken - after the access token expires (~3600s) there is no working endpoint to exchange the refresh_token for a new access token, forcing integrators to re-run the full login flow github.com
Public getsling-api-docs GitHub repo is explicitly marked 'WIP / currently being migrated' with 7 open issues, suggesting documentation is stale and incomplete github.com
Swagger UI at api.getsling.com is sparse - endpoints are listed but request/response schemas, error codes, and pagination semantics are thinly documented compared to peers like 7shifts api.getsling.com
No public webhooks - integrators must poll the API for shift, timesheet, and time-off changes, which is expensive at scale and causes change-detection lag github.com
No published rate-limit documentation - integrators discover limits empirically via 429s, with no documented backoff guidance api.getsling.com
Authorization token is returned only in the response header of /account/login (not the body), tripping up integrators who follow standard REST-client patterns and only inspect response bodies help.paxflow.io
Post-Toast acquisition, third-party integrators report uncertainty about long-term API stability and roadmap, as Toast prioritizes its own POS/Payroll bundle community.n8n.io
Mobile app sync delays - schedule changes don't always push to the app immediately and shifts can display differently on phone vs desktop capterra.com
Mobile app feels slow or glitchy at times, with occasional crashes and stale data g2.com
2024 product change restricted shift-swap visibility to managers only, removing peer-to-peer swap transparency that employees and ops leads relied on capterra.com
30-user hard cap on the Free plan forces small businesses to upgrade as they grow, even before they need Premium features turnozo.com
Limited reporting on lower tiers - advanced labor analytics and budget reporting are gated behind the Business plan capterra.com
Time-clock geofencing accuracy issues - some users report clock-in/out failing or registering outside the geofence in dense urban environments g2.com
Customer support response times degraded post-Toast acquisition; tickets routed through Toast support tiers add friction capterra.com
Lacks deeper HR functionality (performance management, formal onboarding workflows, document storage) compared to full HCM suites connecteam.com