WorkMonitor.

WorkMonitor · Embedded & white-label

Make WorkMonitor part of your product.

Your customer should never meet our brand to check a record. A typed v1 REST API, embeddable verification widgets, white-label branding on your own domain, tenant provisioning for resellers.

Scoped keys, HMAC webhooks and an OpenAPI spec. Sandbox keys need no card.

Brand
W.Verified Work CertificateInvoice #1042, verified at verify.workmonitor.ai
Scoped API keys HMAC webhooks Custom domainsRendered from the API, not a mock: the badge is honest when a certificate is revoked.

Embedded

The API, the widgets, and your name on all of it

Pick one and the screen it lives on opens beside it, so you judge Embedded on what it puts in front of a manager rather than on a list of nouns.

  1. API keys
    Scoped keys, never master keys
    KEYSCOPESSOURCE IPSLAST USED
    • Client portalvk_live_a91c7d2e••••time:readprojects:read2 ranges4m ago
    • Warehouse syncvk_live_5f30b8c1••••analytics:readmembers:read1 range1h ago
    • Proof widget, stagingSandboxvk_test_2d6af053••••ledger:readcertificates:readAny IP12m ago
    • Zapiervk_live_c74e19ab••••time:readoutcomes:readAny IPYesterday
    • Invoice exportvk_live_8b12ee74••••projects:readwebhooks:read1 range26 Aug
    • Old billing scriptRevokedvk_live_ff4a0d19••••billing:readAny IP14 Jul
    New keyPick its scopes, its allowed ranges and an expiry. The secret is shown once and never again.
    A key can never do more than the scopes it was granted — there is no master key5 active · 1 revoked

The surface

Small enough to hold in your head.

6 routes: method, path, the scope a key must hold to call it, and what comes back. Read down the scope column to see how little a credential has to be able to do.

Every route, parameter and error at /v1/docs
The shipped v1 routes, the scope each requires, and what it returns
METHODPATHSCOPERETURNS
GET/v1/membersmembers:readList members with their consent status.
GET/v1/time-entriestime:readList time entries for members and teams.
GET/v1/timesheetstime:readList timesheets; submit and decide via POST.
GET/v1/projectsprojects:readList projects and their tasks.
GET/v1/analytics/dailyanalytics:readDaily focus, activity, and output rollups.
GET/v1/deliverablesoutcomes:readList shipped deliverables from the Proof Ledger.

Every collection is cursor-paginated, newest-updated first: ask for up to 200 rows with limit and follow nextCursor until it comes back null. Writes exist too — appending time, submitting and deciding a timesheet, creating a project — and each one requires an Idempotency-Key, so a retry replays the stored answer instead of booking the hours twice.

How it works

Putting WorkMonitor inside your own product

  1. 1

    Mint a scoped key

    Scoped API keys with an IP allow-list, so an integration gets exactly the surface it needs and nothing adjacent to it.

  2. 2

    Call the typed API

    A typed v1 REST API with an OpenAPI spec and a generated SDK, built against the final route surface rather than hand-maintained beside it. Your engineers read the spec, not our support queue.

  3. 3

    Drop in a widget

    Verification, badge, timeline and approver widgets, each token-scoped so a page shows one record without exposing the account behind it.

  4. 4

    Put your name on it

    White-label branding and custom domains. The verifier your customer opens sits on your domain, and nothing on it says ours.

Start free

An export and a webhook vs. a platform you can build on

workmonitor.vsA CSV export and a webhook

  1. The integration surface

    With WorkMonitor

    A typed v1 REST API with an OpenAPI spec, a generated SDK and HMAC-signed partner webhooks.

    A CSV export and a webhook

    A nightly CSV and one webhook shape, both undocumented.

  2. Credential scope

    With WorkMonitor

    Scoped keys with an IP allow-list, so a leaked credential costs you one integration. OAuth2 client-credentials in beta.

    A CSV export and a webhook

    One API key with access to everything.

  3. Showing data in your product

    With WorkMonitor

    Embeddable badge, timeline, approver and verification widgets, scoped by token.

    A CSV export and a webhook

    Rebuild the UI yourself against an undocumented payload.

  4. Whose brand the customer sees

    With WorkMonitor

    Yours: white-label branding and a custom domain.

    A CSV export and a webhook

    The vendor’s, on a portal you have to explain.

  5. Reselling it

    With WorkMonitor

    Multi-tenant and reseller provisioning, in beta, with isolation enforced at the schema rather than in a query somebody has to remember.

    A CSV export and a webhook

    Not supported; every customer signs with the vendor.

  6. Knowing what you are using

    With WorkMonitor

    API usage metering, in beta, against the same entitlement model the plans are gated by.

    A CSV export and a webhook

    A surprise on the invoice.

API keys
Scoped keys, never master keys
KEYSCOPESSOURCE IPSLAST USED
  • Client portalvk_live_a91c7d2e••••time:readprojects:read2 ranges4m ago
  • Warehouse syncvk_live_5f30b8c1••••analytics:readmembers:read1 range1h ago
  • Proof widget, stagingSandboxvk_test_2d6af053••••ledger:readcertificates:readAny IP12m ago
  • Zapiervk_live_c74e19ab••••time:readoutcomes:readAny IPYesterday
  • Invoice exportvk_live_8b12ee74••••projects:readwebhooks:read1 range26 Aug
  • Old billing scriptRevokedvk_live_ff4a0d19••••billing:readAny IP14 Jul
New keyPick its scopes, its allowed ranges and an expiry. The secret is shown once and never again.
A key can never do more than the scopes it was granted — there is no master key5 active · 1 revoked

Every capability in Embedded, and exactly where each one stands

  • Embeddable verification widgets
  • White-label branding
  • Custom domains

Ask AI

Ask AI about your integration

API usage, webhook deliveries and tenant state, in plain language. Your integration, queryable.

Which API keys are doing the most work?

Pick a question above and WorkMonitor AI will answer from your team's real numbers.

Use cases

What gets built with it

Each one opens on the page written for that job — the same capabilities, read from the work rather than from the product.

Straight answers

The questions we would ask in your position

Every answer here is the one you would get on a call. Open as many as you like; they stay open, so two can be held side by side.

5 questions
Ask us something else

Take these with you

The software is the easy part of a rollout

Here is what we would send a manager doing one for the first time: how to read a productivity number, what to say to a remote team before anything is installed, and a policy you can adopt as written.

Point it at one team for a week.

Create the account, put the agent on a handful of desks, and leave it alone. On Friday you read the week instead of reconstructing it: hours against their projects, focus and idle per person, and the timesheets already filled in.

Free for two seats. No card, and no sales call to sit through.