Skip to main content

Important API Update: Changes Required by October 14, 2026

How to update your SocialTalk Queries API integration to support the new authentication, endpoints, and response formats.

Written by Diogo Mouro

Effective date: October 14, 2026

We're introducing important changes to the SocialTalk Queries API to improve its structure, security, and capabilities.

These changes affect clients integrating directly with our API at:

https://api-customers-queries.socialtalk.io

Action required: If you're currently using the SocialTalk Queries API, you'll need to update your integration before October 14, 2026, to avoid service interruptions.

This article explains what's changing and how to prepare your integration.

1. Authentication: API keys must now be sent in the request header

Previously, your API access key was included directly in the URL.

With the new version, authentication is handled through the Authorization header using a Bearer token.

Previous authentication:

GET https://api-customers-queries.socialtalk.io/profiles/{apiAccessKey}

New authentication:

GET https://api-customers-queries.socialtalk.io/profiles/{profileId} 
Authorization: Bearer {your_api_key}

What you need to do:

  1. Remove the API access key from your request URLs.

  2. Add an Authorization header to every API request.

  3. Use the following format: Bearer {your_api_key}.

  4. Update any existing integration scripts or services that use the previous authentication method.

Important: All requests must use header-based authentication.

2. Search and list endpoints now use POST instead of GET

Endpoints used to search or retrieve lists of resources are changing from GET requests with URL query parameters to POST requests with a JSON request body.

This affects searches and listings of profiles, brands, projects, listeners, participants, and posts.

Previous request:

GET /profiles/{apiAccessKey}?search=nuno&pageIndex=0&sortField=KnownByName&sortDesc=false

New request:

POST /profiles/search Authorization: Bearer {your_api_key} Content-Type: application/json

Request body:

{   "keyword": "nuno",   "page": 0,   "sort": {     "field": "KnownByName",     "descending": false   } }

What you need to do:

  1. Identify any existing search or list requests using GET.

  2. Change them to POST where required.

  3. Move pagination, filtering, and sorting parameters from the URL into a JSON request body.

  4. Update parameter names according to the new API contract.

Affected endpoints

The following endpoints now use POST for search/list operations:

Endpoint

Method

/profiles/search

POST

/brands/search

POST

/brands/{brandId}/projects

POST

/projects/search

POST

/projects/{projectId}/participants

POST

/projects/{projectId}/posts

POST

/projects/{projectId}/{profileId}/posts

POST

/listening/search

POST

/listening/{listenerId}/profiles

POST

/listening/{listenerId}/posts

POST

/listening/{listenerId}/{profileId}/posts

POST

/profiles/{profileId}/projects

POST

/profiles/{profileId}/{socialAccountId}/posts

POST

Endpoints that retrieve an individual resource by ID, such as GET /profiles/{profileId} or GET /projects/{projectId}, continue using GET, but must also use the new authentication header.

3. Request parameter changes

Several request parameters have been renamed or reorganized.

Previous parameter

New parameter

search

keyword

pageIndex

page

sortField

sort.field

sortDesc

sort.descending

The new sorting field accepts a string rather than a fixed enumeration. Valid sorting values are documented for each endpoint.

Unrecognized sorting fields are ignored rather than rejected.

4. Response format changes

Some API responses are also changing. You may need to update how your application processes the returned data.

Post types and formats

The following boolean fields have been removed:

  • isReels

  • isStory

  • isIgtv

  • isVideo

They have been replaced with two fields:

type

Possible values: Post, Reels, Story, Short, Live.

format

Possible values: Image, Video, CarouselAlbum.

If your integration uses the previous boolean fields, update your logic to use type and format instead.

Profile metadata

Several fields now return more readable information:

  • Gender, ProfileType, and InfluencerType return text values instead of numeric codes.

  • Interests and SpeaksAbout return objects containing id and name instead of raw IDs.

  • Brands returns a list of brand names instead of IDs.

If your integration expects numeric values or specific data structures, make sure your data mapping and processing logic are updated.

5. Removed endpoints

The previous multi-project endpoints that accepted a comma-separated list of project IDs are no longer supported:

GET /projects/participants?projectIds=... GET /projects/posts?projectIds=...

Use the individual project endpoints instead:

POST /projects/{projectId}/participants POST /projects/{projectId}/posts

If your integration retrieves data from several projects, you'll need to adapt it to request each project individually.

6. New API capabilities

Alongside these changes, we're also expanding what you can do with the API.

Advanced profile search

Profile searches now support additional filters, including:

  • Country, gender, and email availability.

  • Follower ranges, interests, topics, lists, and tags.

  • Social account size, engagement rate, and estimated performance.

  • Audience demographics, credibility scores, and follower-quality information.

New reference endpoints

The API also introduces the following endpoints:

GET /data/countries GET /data/interests GET /data/lists GET /data/tags GET /data/actions-cost/{socialNetworkName}

These additions extend the available functionality and are not breaking changes.

7. Checklist: What should I do before October 14?

To avoid interruptions, make sure you've completed the following:

  • Move API authentication from the URL to the Authorization header.

  • Change affected search/list requests from GET to POST.

  • Move search, pagination, and sorting parameters into JSON request bodies.

  • Update renamed request fields.

  • Adapt your code to the new post type and format fields.

  • Update how profile metadata is processed.

  • Replace the removed multi-project endpoints.

  • Test your integration before the production update.

Deadline: Wednesday, October 14, 2026.

8. Need assistance?

We understand that API changes can require adjustments to your existing workflows.

If you have questions or need support updating your integration, please contact the SocialTalk support team through our chat.

We're happy to help you prepare for the transition and keep your integration running smoothly.

Did this answer your question?