Skip to main content
Every request must carry a bearer token in the Authorization header:
FlowEstate accepts two bearer types:

API keys

API keys are created in the FlowEstate dashboard under Settings → API Keys. The raw key is shown once at creation; FlowEstate stores only a SHA-256 hash. If you lose the key, revoke it and create a new one. Each key carries:
  • A set of scopes that limits what it can do (see Scopes).
  • An organization binding — every read and write is automatically restricted to that organization.
  • An optional expiration date.
  • An active flag — disable a key without deleting it to revoke access immediately.
There is no organizationId parameter to pass on any endpoint. The token is the source of truth.

Personal credentials

A member can create a personal credential after an owner/admin enables Acceso API de members. That key is bound to the member’s current membership. Reads and writes apply only to their lead portfolio (assigned, not disabled). The secret is shown once. Promotion to admin does not widen it; leaving and rejoining does not revive it. See Personal API access for the operational profile, endpoints, and errors.

OAuth access tokens

If you’re an end user connecting FlowEstate through the official Zapier or Make app, your bearer is an OAuth access token issued by FlowEstate’s identity provider. You don’t usually see this token directly — the connector handles it for you. OAuth tokens behave the same as API keys from the API’s perspective: same scopes, same organization scoping, same rate limits. The differences are operational:
  • They’re tied to a specific user, not the organization at large.
  • They expire and refresh automatically.
  • They can be revoked from Settings → Connected Apps.
A member OAuth grant uses the same portfolio and operational profile as a personal API key. Extra requested scopes are clipped when the token is issued. Re-authorize after a membership change.

Authentication errors

When troubleshooting, hit GET /api/v1/me with the same bearer — if that returns 200, your authentication is fine and the issue is downstream (scopes, plan limits, validation). If /me itself fails, fix authentication first.

Best practices

  • One key per integration, named after the integration (make-lead-ingest, zapier-pipeline-sync). Easier to audit and revoke.
  • Minimum scopes. Don’t grant leads:write to a key that only reads.
  • Rotate periodically — at minimum, when an employee leaves or a third-party platform is replaced.
  • Never commit keys to source control. Treat them like passwords.
  • Set expirations for short-lived integrations (one-off backfills, contractor work).