Skip to content
Hypamoon

HR, payroll and shifts

Connect Skello to Hypamoon

Possible, with help from Skello. The API is documented, but you cannot just create a key: access goes through Skello first.

Possible

The check

Three questions about the API of Skello, answered from its own docs.

Public API docs
Yes. A public Swagger reference for a small Public API (KPIs) and an onboarding API. Read the docs
A key you create yourself
No. The API key and Skello ID come from your Skello representative. help.skello.io
Versions or a changelog
Yes. The APIs are numbered v1 in their paths. auth.skello.io
How it signs in
An API key from Skello in the X-API-Key header; some endpoints use a JWT bearer token.
Webhooks
Not confirmed.
Hosting
Cloud
Condition
API access through your Skello representative.

Your own staffing numbers from Skello, next to the rest of your business.

  • Planned and worked hours, payroll totals and sales figures from the Skello KPIs.
  • AI that spots weeks where labour cost runs ahead of sales.
  • A weekly email for the owner and a screen per location.

Ask your chat

Answers straight from your Skello data, in Claude or another chat with the full Hypamoon connection.

  • What share of sales went to labour cost last week, per location?
  • Which location planned the most overtime this month?

On a schedule

Skello has no webhooks we could confirm, so an agent checks every 15 minutes and decides what happens next.

  1. Every 15 minutes

    The weekly KPIs from Skello.

    AI decides

    AI compares labour cost with sales and picks out what stands out.

    Then

    The owner gets one short email per week.

A screen for your team or customers

An app on your own address, with sign-in, on top of the same Skello data.

  • For your team

    A screen per location with planned hours and labour cost for the week.

Skello stays the core: your chat builds the rest on its API, as an adapter plus an app and agents in your Hypamoon project. Reading starts after you click Allow in the portal. Every change an agent or a chat makes in Skello waits for your approval, one call at a time. How adapters work

Good to know

  • Your adapter uses a fixed key: you paste it once in the Hypamoon portal, never in the chat, and it only goes to the API host you allow.
  • The Public API is small: it returns KPIs, with 60 requests per minute shared across all endpoints.

Try it in your chat

First get access from Skello. Then fill in what to read and write, and send it.

Say this in your chat

Build the Hypamoon recipe build-an-adapter for Skello. API docs: https://auth.skello.io/public/v1/docs/index.html. Read: [what]. Write: [what, or nothing].

In Claude, or another chat with the full Hypamoon connection; adapters are not in ChatGPT yet. You paste the key in the portal, never in the chat. The full recipe

Sources

Checked on 7 November 2026.

Skello is a name of its owner, used here only to describe the software. This page is not an official integration and Hypamoon has no partnership with Skello. Found something that changed? Tell us at support.

Tool not listed? Ask the chat to check its API.

The same three checks work for any software. Your chat reads the vendor's own docs and tells you what it found.

Say this in your chat

Check if [software] has an open API that a Hypamoon adapter can use: public API docs, a key or token I can create myself without asking the vendor, and versions or a changelog. Link the pages you used.

Fill in the name of your software. Checking needs no connection to Hypamoon.

Ready to connect Skello?

Connect your chat once, then ask it to build the adapter.

Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT Add to Copilot