Skip to main content

​
About Medallia Agent Connect

Medallia Agent Connect (formerly Stella Connect) is a real-time customer feedback and coaching platform for contact center agents. The Serval integration lets workflows call any Agent Connect API on demand - sending survey invites, managing users, or pulling feedback data - while Serval handles authentication behind the scenes. Agent Connect requires a freshly signed access token on every single request, and Serval creates one automatically each time; your workflows never see or handle the API key or secret. Authentication: API Key + API Secret (Serval signs a fresh token on every request) Data sync: On-demand only - no background sync, polling, or webhooks; nothing is mirrored into Serval

​
What the Medallia Agent Connect integration enables

Anything defined in the Medallia Agent Connect API can be accessed through Serval.

​
Get your credentials

No app registration is needed. You need the API key and API secret that Agent Connect issues for your tenant, plus your tenant’s API gateway host. Medallia’s authentication reference covers the underlying details.
1

Sign in to Agent Connect as an admin

Admin access is required to view the Integrations page.
2

Go to Settings > Integrations

The page lists your tenant’s test and production API keys, each with a corresponding API secret.
3

Copy the API key and API secret for one environment

Choose the pair for the environment this connection will target - test or production.
4

Identify your API gateway host

Your host is yoursubdomain.api.stellaconnect.net, where the subdomain matches your Agent Connect account. If you sign in at yoursubdomain.stellaconnect.net, your API host is yoursubdomain.api.stellaconnect.net.
Agent Connect issues separate test and production key pairs, and each Serval connection targets exactly one environment. To connect both environments, set up two separate installs. Test keys do not work against production, and vice versa.

​
Connect in Serval

1

Enter the API Key (required)

Paste your Agent Connect API key. The field is masked and the value is stored encrypted. Leaving it blank fails with “API Key is required”.
2

Enter the API Secret (required)

Paste the matching API secret. It is stored encrypted and is only ever used inside Serval to sign tokens. Leaving it blank during setup fails with “API Secret is required”.
3

Enter the API Host (required)

Enter your gateway host, for example yoursubdomain.api.stellaconnect.net. Pasting a full URL from your browser is fine - Serval strips a leading https:// or http://, surrounding whitespace, and trailing slashes automatically. A blank value fails with “API Host is required (e.g. subdomain.api.stellaconnect.net)”, and a host that does not end in api.stellaconnect.net fails with “API Host must end in api.stellaconnect.net (e.g. subdomain.api.stellaconnect.net)”.
4

Save the connection

Serval trims all values before saving, so stray whitespace from copy-paste cannot break authentication.
When editing an existing connection, the API Key and API Secret appear masked (dots plus the last four characters of the stored value). Leaving the API Secret masked or blank keeps the stored secret. The API Key works differently: Serval requires it on every save, so re-enter your API key (use the field’s edit control) before saving any change - a save with the API Key left masked or blank is rejected with “API Key is required”. The API Host is shown in clear text and must pass validation on every save.

​
Verifying the connection

The integration ships one health check: Test Medallia Agent Connect Connection - signs a fresh token with your stored API secret and makes a tiny query against the Data Return API (a one-second time window, so almost no data comes back). Because that API requires a valid token and API key, any successful response proves Agent Connect accepted both credentials and that the host is correct.
  • On success: “Successfully authenticated with Medallia Agent Connect and reached the API gateway.”
  • On failure: “Unable to connect to Medallia Agent Connect. Verify your API key, API secret, and API host are correct and that the key has not been revoked on the Agent Connect Integrations page.”
If the connection test is green but a specific workflow call fails, check that your API key has access to that Agent Connect API family, and - for Data Return queries - that date filters are formatted without a trailing “Z” (for example “2026-04-21T00:00:00.000”).

​
Gotchas and troubleshooting

Agent Connect issues independent test and production API key and secret pairs, and each Serval install targets exactly one environment. Test keys do not work against production and vice versa - mixing environments is a common cause of authentication failures. Make sure the key, secret, and the account you intend to reach all belong to the same environment.
Serval strips a leading https:// or http://, surrounding whitespace, and trailing slashes from the API Host before validating, so copy-pasting from the browser URL bar works. But the resulting host must end in api.stellaconnect.net - any other host is rejected at save time, and Serval independently refuses to attach your credentials to requests aimed at hosts outside Medallia’s Agent Connect gateway.
The connection test queries the Data Return API. If your API key does not have access to that part of Agent Connect, the health check fails even though the credentials may be valid for other endpoint families. Ask your Agent Connect administrator to enable Data Return access for the key.
When you edit an existing connection, the API Key and API Secret display as masked values (dots plus the last four characters). Leaving the API Secret masked or blank keeps the stored secret - the masked placeholder never overwrites the real value. The API Key does not behave the same way: a save with the API Key left masked or blank is rejected with “API Key is required”, so keep your API key on hand and re-enter it whenever you save changes to this connection. All values are trimmed before saving, so trailing whitespace cannot silently corrupt the signing key.
Agent Connect rejects access tokens that are not freshly issued, so a token cannot be created once and reused. Serval signs a brand-new token on every outbound request (each one expires after 60 seconds as an extra safeguard). The generic custom HTTP integration only supports static headers and cannot re-sign per request, which is exactly why this native integration exists - use it instead of a custom HTTP connection.
Per Medallia’s authentication documentation, Agent Connect expects the Authorization header to contain the bare signed token, not “Bearer” followed by the token. Serval handles this automatically; if you are comparing against your own manual API tests, do not add a Bearer prefix.
The Data Return API expects timestamps without the trailing “Z” (for example “2026-04-21T00:00:00.000”) and treats them as UTC, matching Medallia’s own sample calls. Workflows that filter Data Return queries by date should format their timestamps this way.
Need help? Contact support@serval.com for assistance with your Medallia Agent Connect integration.