Start building on the Skedulo Pulse Platform

Get a tenant, authenticate, make your first API call, and pick the path that matches what you're building, all in your first hour.

Skedulo is a scheduling platform for deskless work: jobs, resources, availability, and the logic that matches them. You can extend it with full code (APIs, functions, custom components), low code (page builder, mobile forms), or no code (webhooks and triggered actions). This guide gets you from nothing to your first working call, then points you at the right quickstart for what you want to build.

1. Get a tenant

Everything you build runs inside a Skedulo tenant (your team). You need:

A tenant you can sign in to. If your organization already uses Skedulo, ask for a login on a dev or UAT tenant rather than production.
Administrator access, so you can create API tokens and deploy artifacts.

Don't have a tenant? Talk to Skedulo about getting set up.

2. Get an API token

In the Skedulo web app, go to Settings > Developer tools > API tokens and create a token. Treat it like a password and store it securely. Every API request carries it in an Authorization header.

Verify it works:

curl -X GET https://api.skedulo.com/auth/whoami \
  -H "Authorization: Bearer $API_TOKEN"

A JSON response describing your user and tenant means you're authenticated.

3. Make your first API call

The platform's data (jobs, resources, availability, and your custom objects) is exposed through a GraphQL API. Queries are POSTed as JSON to the GraphQL endpoint:

curl -X POST https://api.skedulo.com/graphql/graphql \
  -H "Authorization: Bearer $API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query": "query { jobs { edges { node { UID Name JobStatus } } } }"}'

Prefer clicking around first? Paste your token into the GraphQL explorer to introspect your tenant's schema and run queries in the browser, or browse the REST surface in the API explorer.

4. Install the CLI

The Skedulo CLI (sked) scaffolds, develops, and deploys every artifact type: functions, pages, web and mobile extensions, webhooks, and custom objects. Install it from the CLI quickstart, then authenticate:

sked tenant login web -a my-tenant

You'll want it for every path below except pure API integration.

5. Choose your path

Each quickstart ends with something working in your tenant:

Integrate via API: query and change jobs, resources, and availability with GraphQL.
Customize the platform: build custom pages for the web app with Horizon components.
Build for mobile: put custom forms in the Skedulo Plus app for workers in the field.
Automate workflows: call your own systems the moment a record changes.

Building with an AI assistant?

The docs are agent-ready: installable agent skills, markdown mirrors of every page, and an llms-full.txt index. See build with your AI assistant to set it up.

Keep going

Developer quickstarts: the full quickstart index, tooling, and example repositories.
Developer guides: the complete documentation, covering the data model, authentication, scheduling, optimization, and access control.
Blog and changelog: tutorials, deep dives, and what's new for developers.