API, webhooks and spreadsheets

Connect Qyasy to the systems you already use. API keys and webhooks are available on plans that include the API. Owners and admins manage them in Settings, Developer API.

Spreadsheet sync

Pull a KPI's values from a sheet every hour instead of typing them.

  1. Open the KPI, go to its Data tab, and choose Connect a sheet.
  2. Paste the Sheet link:
    • Google Sheets, public: File, Share, Publish to web, then the sheet as comma-separated values.
    • Google Sheets, private: share the sheet as Viewer with the email address Qyasy shows, then paste its normal link.
    • Excel Online (OneDrive or SharePoint): Share, Anyone with the link can view, Copy link.
  3. Choose the Date column and the Value column, and whom the values belong to.
  4. Save. Use Sync now to run it straight away. Disconnect stops syncing; values already saved stay.

API keys

  1. In Developer API, create an API key and choose its access: Read, or Write values as well.
  2. Copy the key straight away. It is not shown again.

A key acts with the permissions of the person who created it. Send it in the Authorization header:

Authorization: Bearer qk_your_key

The base address is https://bk.qyasy.com/api/v1/t/<company-domain>/external.

  • GET /kpis lists KPIs.
  • GET /kpis/{id}/values reads a KPI's values.
  • POST /kpis/{id}/values sends values (needs Write values).
  • GET /objectives lists objectives.

Example: send two values.

POST /kpis/12/values
Content-Type: application/json

{ "values": [
  { "date": "2026-10-01", "actual": 1520 },
  { "date": "2026-11-01", "actual": 1610 }
] }

You can send up to 500 values in one request. The answer says which were saved and why any were not. Keys are limited to 120 requests a minute.

Webhooks

Qyasy sends a signed POST to your HTTPS address when these events happen:

  • entry.saved: a value is saved.
  • kpi.off_track: a KPI turns red.
  • period.approved: a period is approved.
  • action.assigned: an action is assigned.

Each request carries X-Qyasy-Event with the event name and X-Qyasy-Signature with sha256= followed by the HMAC-SHA256 of the raw body, made with your webhook secret. Check the signature before you trust the request, for example in Node.js:

const crypto = require("crypto");
const expected = "sha256=" + crypto.createHmac("sha256", secret).update(rawBody).digest("hex");
const ok = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signatureHeader));

Webhook addresses must be public HTTPS addresses.

Ready to make performance clear to everyone?

Start free trial