The API Report CardAPI Index
Planday

Planday API

Workforce Management / Shift Scheduling · planday.com

Planday documents a public REST API across 11 modules (scheduling, punch clock, payroll, HR, absence, revenue) with OAuth 2.0 and published rate limits. Customers create API apps in Settings; partners need portal-admin involvement per client. No published SDKs, and webhook coverage is thin.

Last verified: August 2026HR & PayrollNO MCP
API GRADE
A+
VERIFIED AUG 2026

SCORECARD

ExistenceGOODPublic REST API at openapi.planday.com with OpenAPI specs across 11 modules.
AccessGOODCustomers create apps under Settings for client credentials; partners need an admin in each client portal.
CoverageGOODEleven modules span scheduling, punch clock, payroll, HR, absence, revenue, and reports.
AuthGOODOAuth 2.0 client credentials with rotating refresh tokens; no API-key fallback for read-only use.
Docs & DXGOODPublic OpenAPI specs and a demo portal on request; no published SDKs, and webhook coverage is thin, so partners poll.
StabilityGOOD
MCPNONENo official or maintained community MCP server was found for Planday. The only related GitHub repository is an inactive personal project with no registry listing. VERIFIED 2026-08
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Planday scores A+ on Supergood's API Report Card. Planday documents a public REST API across 11 modules (scheduling, punch clock, payroll, HR, absence, revenue) with OAuth 2.0 and published rate limits. Customers create API apps in Settings; partners need portal-admin involvement per client. No published SDKs, and webhook coverage is thin.

Tried to integrate with Planday?
SOURCES
Per-portal rate limits (20 req/sec, 750 req/min) are tight for enterprise multi-location backfills and force partners to throttle aggressively even when their client-ID budget would allow more openapi.planday.com
Limited webhook coverage across modules forces integrators to poll Reports/Schedule/Punchclock endpoints for change detection, burning rate-limit budget openapi.planday.com
OAuth 2.0 refresh-token rotation requires careful credential management; no API-key fallback for simple read-only integrations openapi.planday.com
Production access requires admin-level control of a customer's Planday portal to generate client credentials, complicating self-serve partner integrations and forcing customer-side IT involvement openapi.planday.com
API module separation (11 distinct modules) creates cross-module joins on the integrator side that would ideally be served by a single canonical employee/shift/pay endpoint openapi.planday.com
Region-locked integrations and feature flags mean an API endpoint can return 200 but with empty/partial data depending on the customer's market/subscription tier help.planday.com
Post-Xero acquisition, API roadmap prioritizes Xero ecosystem integrations over neutral partner needs blog.xero.com
Integration availability varies by region/market and subscription plan, blocking customers from using Planday + their local payroll/POS even when the integration technically exists help.planday.com
Frequent reports of pricing creep post-Xero acquisition with per-user-month plans pushing total cost well above headline starter rate, especially with 5-user minimum itqlick.com
Mobile app reliability issues (clock-in failures, push notifications not firing) commonly cited in app-store reviews g2.com
Reporting and analytics considered shallow compared to Quinyx and Deputy for multi-location enterprise operators selecthub.com
Customer support response times degraded post-Xero acquisition per multiple review-site comments trustradius.com
Shift template and schedule import flows considered clunky vs newer AI-first competitors softwareworld.co
Limited native HR depth (no full HCM, no formal performance management, light onboarding) forcing customers to bolt on Personio or BambooHR marketplace.personio.com