Salesflare
BUSINESS · CRM & SUPPORT
Accounts, contacts, opportunities, and tasks with that person’s own access.
Connecting Salesflare in practice
Salesflare has exactly one credential type — a bearer API key minted in Settings, with no scopes and no OAuth flow in the published spec — so a read-only reporting agent holds the same reach over accounts, contacts, opportunities and workflows as a writing one. Default page sizes are inconsistent across collections: /accounts returns 10, /contacts and /tasks return 20, and /opportunities and /users document no default at all.
Scopes that draw scrutiny
Authorization: Bearer APIKEYThe only credential in the spec. It is created under Settings → API keys and carries no scope list, so it reaches all 46 documented endpoints, including /settings/ai and workflow audience membership.
Rate limits
- 429 Too Many Requests is documented as a possible response, but the published OpenAPI spec gives no request-per-interval figure to design against.
Worth knowing
- The spec requires TLS 1.2 or higher explicitly and says older TLS and any SSL version will not work, which bites on older runtimes rather than on the API.
- There are no webhooks in the spec, so change detection means polling /contacts with modification_after and /accounts with creation_after.
- Pass the page size explicitly everywhere: because each collection defaults differently, code that omits limit silently reads 10 accounts and 20 contacts.
- Sort keys are not enumerated in the spec — order_by on /tasks is documented as discoverable through "a discover mode call", so valid keys have to be read back from the API rather than from the docs.
Checked against Salesflare API reference (2026-09-29), Salesflare OpenAPI spec (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Salesflare behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.