limited · reviewed 2026-09-12
API keys, webhooks, and safe examples
You create an API token or webhook endpoint without inventing undocumented REST paths.
- Audience
- developer, tenant-admin
- Roles / plan
- reseller_admin for API tokens; partner onboarding for broader REST. Reseller grant.
- Menu
- Manage → Settings → API tokens / Webhooks, and /docs/api
The dashboard calls tenant-scoped HTTP APIs through api.luraflow.com. A public, versioned partner REST catalogue is still summarised at /docs/api. Early Access partners request access case by case.
- API tokens: Settings → API tokens. Treat tokens as secrets; never put them in Guides examples.
- Webhooks: Settings → Webhooks. Subscribe only to events the form lists.
- Auth: Bearer access tokens from login/MFA. Do not send passwords on query strings.
- Example (safe): Authorization: Bearer <access_token> on HTTPS to https://api.example.com/api/v1/... using only endpoints your token was granted.
Open this setting on luraflow.com — uses the safe login redirect. Never opens another tenant hostname.
Canonical: https://luraflow.com/docs/integrations/api-overview