Fivexer

Fivexer Capacity API

The capacity API from Fivexer — 40 operation(s) for capacity.

GitHub OpenAPI

Operations 45

GET /v1/capacity/alerts List capacity alerts, soonest act-by first #
POST /v1/capacity/alerts/{id}/ack Acknowledge a capacity alert #
POST /v1/capacity/alerts/{id}/action Record what was done about a capacity alert #
POST /v1/capacity/alerts/{id}/standby Ask people to stand by for an alert’s shift — not a shift yet #
GET /v1/capacity/radar The next 72 hours of published shifts, judged #
GET /v1/capacity/today Where each routing lane is heading over the next 8 hours #
GET /v1/capacity/precision How often each alert tier was followed by a short shift, and shortages avoided #
GET /v1/capacity/settings Capacity radar settings #
PUT /v1/capacity/settings Change capacity radar settings #
GET /v1/capacity/events List capacity events #
POST /v1/capacity/events Record a known busy or closed period #
PATCH /v1/capacity/events/{id} Change a capacity event (an applied one returns to draft) #
DELETE /v1/capacity/events/{id} Withdraw and archive a capacity event #
GET /v1/capacity/events/{id}/preview What accepting a capacity event would change #
POST /v1/capacity/events/{id}/accept Apply a capacity event to the shift templates it touches #
POST /v1/capacity/events/{id}/withdraw Take a capacity event off its templates #
POST /v1/capacity/events/{id}/occurrences/{date}/skip Skip one day of a busy period (an applied one stays applied) #
POST /v1/capacity/events/{id}/occurrences/{date}/unskip Bring back a skipped day of a busy period #
POST /v1/capacity/events/{id}/occurrences/{date}/move Move one day of a busy period to another day, as a period of its own #
POST /v1/capacity/events/{id}/occurrences/{date}/move-back Put a moved day of a busy period back on the day it came from #
POST /v1/capacity/events/{id}/series/move Move every day of a busy period by a few days (every Friday to Saturday) #
GET /v1/capacity/forecast The workspace forecast: series, accuracy and staffing groups #
GET /v1/capacity/forecast/series/{series} One series, hour by hour (nowcast re-applied) and week by week #
GET /v1/capacity/forecast/staffing/{group} People a staffing group needs each hour, against what is rostered #
GET /v1/capacity/forecast/weeks Week by week for six months: volume, the people-hours it takes, and what is… #
GET /v1/capacity/spikes Days the forecast could not explain #
POST /v1/capacity/spikes/{id}/name Name a spike: it becomes a past event the forecast learns from #
POST /v1/capacity/spikes/{id}/dismiss Nothing to name: hide a spike #
GET /v1/capacity/coming-up Busy or quiet days the platform noticed coming #
POST /v1/capacity/coming-up/accept Record a suggestion as a draft event (never applied without its own accept) #
POST /v1/capacity/coming-up/dismiss Stop suggesting this #
POST /v1/capacity/events/suggest Fill in an event from its name and dates: kind, size, and which work moves #
GET /v1/capacity/tag-shifts Which shifts work each tag, and suggestions #
PUT /v1/capacity/tag-shifts/{tag} Confirm which shifts work a tag (an empty list unmaps it) #
GET /v1/capacity/forecast/proposals Raises the forecast proposes, or (status=accepted) the ones still to come that… #
POST /v1/capacity/forecast/proposals/{id}/accept Accept a proposal: one labelled override on its shift #
POST /v1/capacity/forecast/proposals/{id}/withdraw Take an accepted raise back: its override comes off the shift and the rotas #
POST /v1/capacity/forecast/proposals/{id}/dismiss Not this time #
POST /v1/capacity/import Import volumes from a CSV: date, hour?, series, value, unit #
GET /v1/capacity/import/series Imported series and their unit #
GET /v1/capacity/import/sources Files fetched on a schedule #
POST /v1/capacity/import/sources Fetch a file on a schedule (its link and header are stored sealed) #
PATCH /v1/capacity/import/sources/{id} Change a scheduled file #
DELETE /v1/capacity/import/sources/{id} Stop fetching a file #
POST /v1/capacity/import/sources/{id}/run Fetch a scheduled file now #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/5xer-com/openapi/5xer-com-capacity-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/5xer-com:5xer-com-capacity-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

5xer-com-capacity-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Fivexer Platform Capacity API
  description: 'Routing-as-a-service: create workers and tasks, the platform matches continuously. `/v1` authenticates with a workspace API key (`Authorization: Bearer sk_...`); `/console` with a session token from `/auth`; `/admin` with the operator token.'
  version: 0.1.0
servers:
- url: https://5xer.com
  description: This deployment
tags:


# --- truncated at 32 KB (39 KB total) ---
# Full source: https://artifacts.apis.io/5xer-com/openapi/5xer-com-capacity-api-openapi.yml