Stackroom

Integrations & API

Connect Stackroom to the rest of your stack

A documented REST API, API keys and event webhooks let you sync assets, automate workflows and plug Stackroom into the tools you already run.

How do you integrate with Stackroom?

Stackroom exposes a documented REST API with scoped API keys and 41 signed webhook events — checkouts, returns, warranty expiry, audits and more — delivered with retries and a delivery log. CSV and XLSX import and export cover finance and migration work without writing any code.

Build & connect

Open by design

REST API

Read and write assets, people and more programmatically.

API keys

Scoped keys for secure server-to-server access.

Webhooks

41 signed events — checkouts, returns, warranty expiry, audits — delivered with retries and a log.

Import & export

CSV/XLSX in and out for finance, audits and migrations.

Full reference, quickstart and the OpenAPI specification are on the developers page. More connectors (Slack/Teams, QuickBooks/Xero, Zapier) are on the roadmap.

API keys

Scoped keys, issued from the console

Keys are created per integration rather than per person, so revoking one does not break the others, and each carries its own scope.

Rate limits and the monthly quota are set by your plan and reported on every response, so a client can back off before it is throttled rather than after.

Screenshot to come

The API keys screen: keys with their scope, last-used date and the rate-limit and quota counters.

Read keys may call GET routes; write keys may also create and update. Every response carries its own rate-limit and quota headers.
Webhooks

41 events, signed and retried

Checkouts, returns, warranty expiry, audits, people, members, bookings, reminders and plan changes all fire events. Each delivery is signed with HMAC-SHA256 over the timestamp and the raw body, so a receiver can verify it and reject a replay.

Delivery is at-least-once with retries and a backoff. Every delivery carries a unique id — deduplicate on it and the guarantee is safe to rely on.

Screenshot to come

The webhook endpoints screen with the delivery log open, showing attempts, status codes and a replayed delivery.

Every attempt is recorded, so a brief outage is something you can see and replay rather than something you discover later.

FAQ

Questions about the API

Where is the Stackroom API documentation?

The reference and the OpenAPI (Swagger) specification are published at api.stackroom.io/api/v1/docs, with a quickstart on the developers page. You do not need an account to read either.

How are Stackroom webhooks secured?

Each delivery is signed with HMAC-SHA256 over the timestamp and the raw request body, so a receiver can verify authenticity and reject replayed requests. Every delivery also carries a unique id, which is what makes at-least-once delivery safe to deduplicate.

What happens if our endpoint is down?

Deliveries are retried with a backoff rather than dropped, and every attempt is recorded in a delivery log you can inspect, so a brief outage does not silently lose events.

Does Stackroom integrate with Slack, Zapier or accounting tools?

Not as prebuilt connectors today — those are on the roadmap. The API and webhooks cover the same ground in the meantime, and CSV or XLSX export handles finance and audit hand-offs.

Ready to know where every asset is?

Start free — tag your first 100 assets and run a real checkout in your first session. No credit card required.