Agorapulse · Authentication Profile
Agorapulse Authentication
Authentication
Agorapulse runs two independent authentication models. The REST API is a single static API key in an X-API-KEY header, scoped to the individual user who minted it. The remote MCP server is a separate OAuth 2.0 protected resource with its own authorization server, dynamic client registration and PKCE. They do not share credentials.
Agorapulse secures its APIs with apiKey and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
Social Media ManagementSocial-MediaCRMAnalyticsPublishingInbox ManagementSocial Listening
Methods: apiKey, oauth2
Schemes: 3
OAuth flows: authorizationCode
API key in: header
Security Schemes
bearerAuth apiKey
HookSignature apiKey
MCP OAuth oauth2
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.