Automate the workspace around your stack.

Signed endpoints, webhooks and scheduled jobs let your existing systems raise work, push stock movements and pull operational data — without anyone re-keying it.

Get an API workspace Talk to engineering

HMAC signaturesWorkspace-scoped keysTyped JSONCron schedules

RequestPOST

curl -X POST \
  https://www.taskspro.ai/api/public/hooks/weekly-digest \
  -H "Content-Type: application/json" \
  -H "X-TasksPro-Key: $TASKSPRO_KEY" \
  -d '{"week":"2026-08-24"}'

Response200 OK

{
  "ok": true,
  "workspace": "acme-business",
  "week": "2026-08-24",
  "digest": {
    "jobs_completed": 128,
    "hours_logged": 1462.5,
    "invoices_raised": 34,
    "outstanding_value": 84250.00
  }
}

What you can build on

A small, dependable surface area — designed so integrations stay working when the product moves forward.

Webhooks

Signed callbacks the moment a job changes status, stock crosses a reorder point or an invoice is paid. Retries are automatic with exponential backoff.

HMAC signedAuto retryReplay

Public endpoints

Workspace-scoped HTTP endpoints for intake forms, integrations and partner systems. Every call is verified before a single query runs.

RESTJSONVerified

Scheduled jobs

Cron-driven routines — weekly business digests, overdue invoice sweeps, reorder checks — executed server-side against your tenant only.

CronPer-tenantIdempotent

Scoped keys

Keys belong to one workspace and one role. They never grant cross-tenant reads, and rotation takes effect immediately.

RotatableRole boundAudited

Typed payloads

Predictable JSON shapes for every module record, validated on the way in and the way out so integrations fail loudly, not silently.

Schema validatedStable fields

Exports

CSV and PDF exports of operational reports, invoices and receipts for warehouses, accounting systems and BI tooling.

CSVPDFScheduled

Events you can subscribe to

Each delivery carries a signature header, a delivery id and the full record shape. Failed deliveries retry on a backoff schedule and can be replayed from the dashboard.

Stable field names, additive changes only

Retries for 24 hours, then a delivery alert

Rejected before any query when a signature fails

job_card.status_changedFires on every transition, with the previous and new stage.

timesheet.submittedApprover, hours and the linked project or job card.

inventory.reorder_reachedItem, depot, current level and configured reorder point.

invoice.paidPayment provider, amount, receipt number and client record.

incident.loggedSeverity, site, reporter and the linked job where relevant.

booking.confirmedResource, assignee, window and the client it belongs to.

Guarantees the integration inherits

The same isolation and auditing that protects the product protects anything you build against it.

Tenant isolation by default

Every request resolves to exactly one workspace at the database layer. There is no shared-read path, even for platform staff.

Secrets stay server-side

Keys are never shipped to a browser bundle. Signing and verification happen entirely inside the server runtime.

Every call is auditable

Endpoint, actor, payload shape and outcome are recorded, so an integration change is traceable months later.

Live in four steps

1
Create a workspace key
Generate a scoped key from workspace settings and store it in your secret manager.
2
Register a webhook
Point an HTTPS URL at the events you care about and capture the signing secret.
3
Verify signatures
Check the signature header before parsing. Reject anything that does not match.
4
Ship and monitor
Watch deliveries, replay failures and roll keys without downtime.