API reference
List search results
The rows of a succeeded search, in delivery order, kept 30 days. A person row of linkedin_engagement, own_engagement, social_listening or events is a person as LinkedIn shows them next to a post: no profile is read and no AI judged them.
Recipes says how to read one.
Authentication
Send Authorization: Bearer gtk_…. Create the key under Connect assistant → API keys. A missing, invalid or revoked key is 401. A valid key while this API is not enabled for your organization answers 403 api_not_enabled, with what the key can do instead. Every response includes mySDR-Api-Version, mySDR-Request-Id and Cache-Control: no-store, and a response to an accepted key also X-RateLimit-* (so not a 401, a 405, an OPTIONS or a 404 for an unknown path).
Path parameters
search_idstring· required — A search id (srch_…).
Query parameters
objectstring— Only rows of this kind. One of:company,person,event.limitinteger— How many rows to return, from 1 to 100. Defaults to 25.cursorstring— Thenext_cursorof the previous page, sent back unchanged.
Response
objectstring· required — Alwayslist. One of:list.dataobject[]· required — Rows. A company row carries the signal (round, technology) andnext.leads, the URL of POST /leads for that company. A person row carriespersonandsignals: the new role, or for the LinkedIn signals up to 3 things the person did (reaction,comment,mention,post,event_post), each withpost_url,post_snippet,post_authorand, for a comment,text. On a LinkedIn rowtitle,companyandlocationare null: the headline is all there is.next.enrichreads the profile.next_cursorstring | null· required — The next page, or null.
Credits
Free. The search already charged the rows.
Errors
- 400
invalid_request— An unknownobject, alimitoutside 1 to 100, or a cursor that was changed. - 409
search_not_ready— The search has not succeeded yet. The error includes its status. - 404
not_found— No search with this id exists for your organization. - 401
authentication_error— The Authorization header is missing, or the key is unknown or revoked. - 403
permission_error— API access is not part of your plan, or your account is suspended. - 403
api_not_enabled— The key is valid, but the Signals API or the Company API is not enabled for your organization yet. The error says what this key can do. - 429
rate_limit_error— More than 60 requests per minute, or more than 3 at the same time, on one key. Wait for the Retry-After header. - 500
internal_error— Something went wrong on our side.
Example
cURL
curl "https://mysdr.app/api/v1/searches/srch_01J9Z6P8C8V0K3W6T2N8R5M1XA/results?limit=25" \
-H "Authorization: Bearer $MYSDR_API_KEY"
JavaScript
const response = await fetch('https://mysdr.app/api/v1/searches/srch_01J9Z6P8C8V0K3W6T2N8R5M1XA/results?limit=25', {
method: 'GET',
headers: {
Authorization: `Bearer ${process.env.MYSDR_API_KEY}`
}
});
const body = await response.json();
Python
import json
import os
import urllib.request
request = urllib.request.Request(
"https://mysdr.app/api/v1/searches/srch_01J9Z6P8C8V0K3W6T2N8R5M1XA/results?limit=25",
headers={
"Authorization": f"Bearer {os.environ['MYSDR_API_KEY']}"
},
method="GET",
)
with urllib.request.urlopen(request) as response:
body = json.load(response)
Example response
{
"object": "list",
"data": [
{
"id": "cmp_01J9Z6P8C8V0K3W6T2N8R5M1XB",
"object": "company",
"signal_type": "funding_raised",
"credits_charged": 1,
"company": {
"name": "Acme Analytics",
"linkedin_url": "https://www.linkedin.com/company/acme-analytics"
}
},
{
"id": "per_01J9Z6P8C8V0K3W6T2N8R5M1XC",
"object": "person",
"signal_type": "linkedin_engagement",
"observed_at": "2026-10-23T09:00:00Z",
"person": {
"full_name": "Jane Example",
"first_name": "Jane",
"last_name": "Example",
"headline": "CFO at Example Retail",
"title": null,
"company": null,
"location": {
"text": null,
"country_code": null
},
"linkedin_url": "https://www.linkedin.com/in/jane-example",
"picture_url": null
},
"signals": [
{
"kind": "comment",
"occurred_at": "2026-10-21T08:12:00Z",
"reaction_type": null,
"text": "We are looking at this for Q1.",
"post_url": "https://www.linkedin.com/posts/acme-analytics_launch",
"post_published_at": "2026-10-20T07:00:00Z",
"post_snippet": "Today we launch our forecasting module…",
"post_author": {
"name": "Acme Analytics",
"linkedin_url": "https://www.linkedin.com/company/acme-analytics",
"is_company": true
},
"source": "linkedin",
"source_url": "https://www.linkedin.com/posts/acme-analytics_launch"
}
],
"next": {
"enrich": "https://mysdr.app/api/v1/person/enrich"
},
"credits_charged": 1
}
],
"next_cursor": null
}