Register an OAuth client in Medallia Experience Cloud and obtain a client_id and client_secret; all API access is authenticated via OAuth access tokens.
Request an access token by POSTing to the Medallia OAuth token endpoint with the client credentials grant, then include the resulting Bearer token in subsequent API request headers.
Identify the unit (reporting unit) and field names for the survey program you want to export using the Medallia Admin or the metadata API before constructing your data pull.
Use the data export API endpoint (consult current developer.medallia.com docs for the exact path) to request survey responses filtered by date range and reporting unit.
Handle paginated responses by following the next page token or offset pattern returned in each response envelope.
Transform the returned field values into your target schema; Medallia response fields use internal field names that must be mapped to human-readable labels using the program metadata.
Known gotchas
OAuth tokens have a limited TTL; implement token refresh logic rather than obtaining a new token per API call to avoid being rate-limited on the auth endpoint.
Medallia has two distinct API surfaces: the Medallia Experience Cloud API and the Medallia Agile Research (Stella Connect) API — they use separate base URLs and authentication methods; confirm which product your account uses.
Field-level access in the response is governed by role permissions assigned to the OAuth client's associated user; missing fields in the response often indicate an access control gap rather than a missing data issue.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp