Specific
MARKETING · MARKETING
Surveys, conversations, contacts, companies, and custom fields in the workspace they connected.
Connect Specific with Fabriq Developer
Your user pastes their Specific credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Specific in practice
Specific’s public API is GraphQL and nothing else — a single endpoint at https://public-api.specific.app/graphql with introspection enabled — so there is no REST surface to point a generic HTTP tool at. The credential is a personal API key sent as the bare value of the `Authorization` header, with no Bearer prefix and no scopes.
Scopes that draw scrutiny
Authorization: PERSONAL_API_KEYA personal key generated in the workspace under Preferences → API, sent as the raw header value. It carries the creating user’s workspace access, and the same key that reads survey conversations can run deleteUser and deleteCompany.
Worth knowing
- Introspection is on, so the whole schema is discoverable from the endpoint — useful for an agent, and also the fastest way to find the destructive mutations.
- Webhooks are created and removed through `subscribeWebhook` and `unsubscribeWebhook` mutations rather than in the UI, so an integration can subscribe itself.
- Specific ships no client library: "We do not offer our own library for making queries (read) or mutations (write) to the API." You bring your own GraphQL client.
- Attribute deletion is its own mutation pair — `deleteUserAttributes` and `deleteCompanyAttributes` — separate from deleting the record, so partial data loss is a single call.
Checked against Specific GraphQL API reference (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 Specific behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.