Photo of a laptop on a wooden desk showing a dashboard with bar charts and a table, next to a coffee cup, a desk calendar, a notebook and a pen.
Launching 2027

An attendance API and signed webhooks.

Zentaro Pulse has a public attendance API. Each account gets its own API keys. Webhooks send events to your own systems and are signed with HMAC-SHA256, so you can check that a message is really from Pulse. A delivery log shows each send. There is no client library yet.

  • A public API
  • API keys for each account
  • Signed webhooks
  • Delivery log

Without it

  • Someone downloads a file and uploads it to another system.
  • Your own software never learns when a punch happens.
  • Nobody can tell whether an event arrived.

What it does.

A public API

Read and write attendance data from your own systems through the API.

API keys for each account

Each account creates its own keys. Revoke one without affecting the rest.

Signed webhooks

Each webhook is signed with HMAC-SHA256, so your server can verify it.

Delivery log

See each webhook send and whether it arrived. Subscribe to only the events you need.

How it works.

  1. Step 1

    Create an API key

    A developer creates a key in the console.

  2. Step 2

    Call the API

    Read or send attendance data using the key.

  3. Step 3

    Add a webhook

    Give a web address and choose the events to send.

  4. Step 4

    Verify and watch

    Check the signature on your server, and use the delivery log to see sends.

Photo of a laptop on a desk showing a table and a bar chart, with a coffee cup, a notebook and a pen beside it.

The problem you know

What goes wrong without it.

  • Manual transfers. Moving data by file every day wastes time.
  • Shared keys. One key for everything is a risk. Each account should have its own.
  • Events you cannot verify. Your server needs to know a message really came from Pulse.

What it is not

  • It does not come with a client library. The API is documented with Swagger.
  • It is not a direct link to named payroll software. You connect by file or by API.

Who it is for.

Who it is for

  • Teams with their own software
  • Developers who build a payroll or HR link
  • IT managers who want events sent to them

Want to see how it fits your team? Talk to us

Questions people ask.

Does Zentaro Pulse have an API?

Yes. There is a public attendance API with per-account API keys. Zentaro Pulse launches in 2027.

What is a signed webhook?

It is a message sent to your server with a signature. Your server checks the signature to be sure the message is from Pulse.

Which signature is used?

HMAC-SHA256.

Is there a client library?

No. You call the API directly.

Does it plug into named HR or payroll tools?

We do not list any named tool as connected. Use the API and webhooks to build your own link.

Be first to hear when Zentaro Pulse launches

Zentaro Pulse is launching in 2027. Join early access and we will tell you first. Or ask us a question now.

Last updated: