Talkwalker User Management API Guide

Auth method: API key (passed as query parameter access_token or request header)

Setup steps

1. Log in to Talkwalker and navigate to Account Settings.
2. Generate an API token from the API access section.
3. Include the token as access_token=<token> query parameter or in the Authorization header on each request.

User object field mapping is not yet verified for this app.

Endpoint coverage is not yet verified for this app.

• Rate limits: Rate limits are not publicly documented in official Talkwalker developer docs.

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: No official rate-limit documentation found. Contact Talkwalker support for plan-specific limits.

• Pagination method: none

• Default page size: 0

• Max page size: 0

• Pagination pointer: Not documented

• Webhooks available: No

• Webhook notes: No webhook or event-notification system for user-management events is documented in official Talkwalker sources.

• Alternative event strategy: Polling the Talkwalker API for data changes is the only documented approach; no user-event webhooks confirmed.

• SCIM available: No
• SCIM version: Not documented
• Plan required: N/A
• Endpoint: Not documented

Limitations:

• No native SCIM 2.0 provisioning endpoint documented by Talkwalker.
• No IdP connector (Okta, Entra ID, Google Workspace, OneLogin) for automated user provisioning confirmed in official docs.

Three scenarios are relevant for identity graph completeness.

First, authenticating against the data API: retrieve a token from Account Settings, pass it as access_token=<token> on GET requests to /api/v2/search, and parse JSON results

noting that the token is bound to the generating user account and breaks if that account is deactivated.

Second, inviting a new user: no REST endpoint exists;

this is UI-only via Account Settings > Users.

Third, offboarding: also UI-only, with a mandatory manual step to revoke or rotate any API tokens associated with the departing user, since no automated deprovisioning path is confirmed.

Manually invite a new user

1. Log in to Talkwalker as an admin.
2. Navigate to Account Settings > Users.
3. Use the UI to invite the user by email and assign a role.
4. No API endpoint exists to automate this step.

Watch out for: There is no documented REST endpoint for creating or inviting users programmatically.

Authenticate and call the data API

1. Retrieve your API token from Account Settings.
2. Make a GET request to https://api.talkwalker.com/api/v2/search with access_token=<token> as a query parameter.
3. Parse the JSON response for social listening results.

Watch out for: The API token is tied to the generating user account; if that user is deactivated, the token stops working. No service-account token model is documented.

Offboard a user

1. Log in to Talkwalker as an admin.
2. Navigate to Account Settings > Users.
3. Locate the user and remove or deactivate them via the UI.
4. Manually revoke or rotate any API tokens associated with that user.

Watch out for: No automated deprovisioning via API or SCIM; offboarding is entirely manual.

The primary integration trap is assuming the Talkwalker API can support identity graph synchronization - it cannot. There are no user-object endpoints, no SCIM operations, no webhook or event-notification system for user-management events, and no documented rate-limit headers to build reliable polling logic against. Rate limits are entirely undocumented publicly;

contact Talkwalker support for plan-specific thresholds. Any identity graph integration must treat Talkwalker as a manual-only node with no programmatic provisioning surface.