API Documentation

Connecting and Working with the Shifton API

The Shifton API gives you access to all key features of the platform — from schedule management to integrations with external HR, payroll, and analytics systems.
By using the API, you can automate processes and connect Shifton with your company’s internal services.

API Documentation

We support two versions of our documentation:

• 📄 Old Documentation — the previous version of the API reference (still supported for existing integrations):
  👉 https://api2.shifton.com/docs/?_gl=1*1p5sxoh*_gcl_au*NTAxMjY4NzA0LjE3NTcwNzUzMjAuMTI5NjMwODcwMS4xNzU4MjcxOTkzLjE3NTgyNzE5OTI.*_ga*NTE5MDI0OTM2LjE3NTcwNzUzMjA.*_ga_1M7TJQ7HY8*czE3NTg2MjA4MDUkbzU1JGcxJHQxNzU4NjIwOTE5JGo2MCRsMCRoNjU1OTcyMjMw#/en/v1/

• 🚀 New Documentation — the current version of the API with an updated structure and the latest methods:
  👉 https://api2.shifton.com/openapi/?_gl=1*1p5sxoh*_gcl_au*NTAxMjY4NzA0LjE3NTcwNzUzMjAuMTI5NjMwODcwMS4xNzU4MjcxOTkzLjE3NTgyNzE5OTI.*_ga*NTE5MDI0OTM2LjE3NTcwNzUzMjA.*_ga_1M7TJQ7HY8*czE3NTg2MjA4MDUkbzU1JGcxJHQxNzU4NjIwOTE5JGo2MCRsMCRoNjU1OTcyMjMw#/

Getting Started

Obtain an API Key

In your company settings on the Shifton platform, generate an API key.
Authorization is done via the header:

Make Your First Request

For example, to retrieve a list of employees:

Example response:

Integrate the API into Your Workflows

• Automatically create and modify shifts

• Manage vacation and sick leave requests

• Export data to payroll systems

• Build custom dashboards and reports

Core API Capabilities

• Employees – add, edit, and manage roles

• Schedules – create, adjust shifts, plan work

• Time Off & Absences – manage vacation and sick leave requests

• Reporting – export time, payroll, and attendance data

Error Codes

Shifton API uses standard HTTP status codes:

• 200 — Successful request

• 201 — Object successfully created

• 400 — Invalid parameters

• 401 — Authorization error (invalid API key)

• 403 — Access denied

• 404 — Resource not found

• 500 — Server error

Usage Tips

• Always use the new API version for new integrations

• Use Postman or curl for testing

• Respect rate limits to avoid being blocked

• Update integrations that still rely on the old documentation