Coresignal · OAuth Scopes
Coresignal OAuth Scopes
OAuth 2.0
probed
Coresignal publishes 4 OAuth 2.0 scopes via the authorizationCode, clientCredentials, and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Coresignal API on a user’s behalf.
Tokens are issued from https://dashboard.coresignal.com/api/auth/oauth2/token.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
Agentic SearchB2B DataCompaniesCompany DataData as a ServiceElasticsearchEmployee DataEmployeesEnrichmentFirmographicsJob PostingsJobLead GenerationPeople DataSales IntelligenceTalent IntelligenceWeb Data
Scopes: 4
Flows: authorizationCode, clientCredentials, refreshToken
Method: probed
OAuth endpoints
Authorization URL
https://dashboard.coresignal.com/api/auth/oauth2/authorize
https://dashboard.coresignal.com/api/auth/oauth2/authorize
Token URL
https://dashboard.coresignal.com/api/auth/oauth2/token
https://dashboard.coresignal.com/api/auth/oauth2/token
Flows
authorizationCodeclientCredentialsrefreshToken
authorizationCodeclientCredentialsrefreshToken
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| openid | Standard OIDC scope — request an ID token identifying the signed-in dashboard user. | authorizationCode |
| profile | Standard OIDC scope — name, given_name, family_name, picture claims for the dashboard user. | authorizationCode |
| Standard OIDC scope — email and email_verified claims for the dashboard user. | authorizationCode | |
| offline_access | Standard OIDC scope — issue a refresh token so the MCP client can keep the session alive without re-prompting the user in the browser. | authorizationCode |
📄 Provider scope reference: https://docs.coresignal.com/integrations/coresignal-mcp