Teammates, API keys, webhooks

Run EDISQ as a team and as a platform: invite teammates with roles, read your account over the API with revocable keys, and register webhooks for what's next.

EDISQ starts as a one-person tool and grows into a team surface and a platform without changing plans.

Teammates

Invite colleagues from Settings — name, email, role — and they get their own login. Roles keep the warehouse able to work shipments without being able to touch billing. There's no per-seat charge; billing stays per document.

API keys

For direct integration, create an API key under Settings and call the EDISQ API with it (an X-Api-Key header authenticates each request). The API today is a read surface: list and fetch your documents, your partners, and your current usage — enough to feed a warehouse screen, a reconciliation job, or your own reporting without exporting from the dashboard. Keys are scoped to your account, individually revocable, and everything a key does is attributable to it — so a leaked key is one click from harmless.

Webhooks and document submission

Push — webhooks that call your endpoint when events happen, and submitting outbound documents over the API — is the next layer, and we build it in the order real integrations need it. Webhook subscriptions can already be registered under Settings so your endpoint is on file; if an integration is on your roadmap, tell us what you're connecting and you'll be in the first wave, with our engineers in the conversation.

Notifications

Email notification preferences live in Settings too — who hears about new orders, failures, and overdue acknowledgments. The practical setup for most teams: operational alerts to the person who ships, billing notices to the person who pays.