Connection check

• GET /health — no auth required, no rate limit. Used by uptime monitors and load balancers to verify the API is alive and the database responds.
• GET /me — bearer required (any scope, including the empty set). Used by Make / Zapier connectors as the “Test connection” step to surface the org name and the bearer’s permissions to end users.

​

GET /health

​

Request

curl https://panel.flowestate.app/api/v1/health

​

Response 200

{
  "ok": true,
  "ts": "2026-04-29T18:04:15.000Z"
}

​

Response 503

{ "ok": false }

​

Monitoring tips

• Use a keyword check on "ok":true rather than just status 200. That way a misconfigured edge cache that serves a stale {"ok":false} body doesn’t accidentally show as healthy.
• Don’t poll faster than every 60 seconds. It’s a DB ping; don’t turn it into a load test.
• It’s not authenticated. Don’t include any sensitive headers when probing it.

​

GET /me

​

Request

curl https://panel.flowestate.app/api/v1/me \
  -H "Authorization: Bearer fe_k_your_key_here"

​

Response 200

{
  "organization": {
    "id": "org_...",
    "name": "Acme Realty",
    "slug": "acme-realty"
  },
  "auth": {
    "type": "api_key",
    "scopes": ["leads:read", "leads:write"],
    "clientId": null,
    "userId": null
  }
}

​

Fields

​

Errors