Schedultary

HomeScheduling GuidesAssistants

A scheduling API an assistant can follow

A scheduling API is public at https://schedultary.com/openapi.json and at /api/v1/openapi. Both are the same document. Admin and Read Only are read from the person's account on every call. Send Authorization: Bearer with an API key from Settings or a signed-in session token. Employees can read their schedule, file their requests, and manage their swaps. Admins can run the roster, the rules, and a residency year. Named flows for the common jobs live in /agents.json: read the workplace, build a month, build a residency year, decide a request, and request time off.

Discover the server before you call a tool

MCP clients that speak OAuth find the protected-resource metadata from a 401 on /mcp. The registry card is at /.well-known/mcp/server.json. A human setup page is at /docs/agents. Machine summaries are at /llms.txt and /product.json.

Calls that matter first

getMe tells you who the key is. getWorkplace and listPeople describe the roster. getScheduleBuilder reports whether a month can be generated. generateSchedule with action generate fills a draft; set replace to true when a draft is already there. generateYear fills an unpublished academic year. decideRequest approves or denies a shop request. createMyRequest files the caller's own time off.

Questions

Why are there two OpenAPI URLs?

/openapi.json is the crawlable copy. /api/v1/openapi is the same document on the API. Crawlers are asked not to wander the rest of /api/.

Can a key change its own permissions?

No. Access is the person's access in the workplace. Revoke the key in Settings and it stops immediately.

Is there a demo token?

The API document describes a demo key route for local demo mode. A production workplace uses a key you create after you sign in.

Connect an AssistantCreate an AccountSupport