Get Post Reactions
/get-post-reactionsRetrieve the list of people who reacted to a specific post, with reaction types. Useful for building engagement audiences, identifying interested prospects from competitor content, and measuring content reach.
Call it over REST
Authenticate with a bearer token against https://api.agntdata.dev. Swap the placeholders for your key and parameter values.
curl -s -X POST "https://api.agntdata.dev/get-post-reactions" \
-H "Authorization: Bearer <YOUR_AGNTDATA_API_KEY>" \
-H "Content-Type: application/json" \
-d '{ "url": "<string>", "page": 0 }'Copy-paste prompt
Paste this into a coding agent. It connects the superagnt MCP server, finds the tool data_linkedin_get_post_reactions, and runs a first call — with the REST fallback if MCP is unavailable.
You are wiring up the agntdata "LinkedIn" API to use this endpoint: Get Post Reactions.
1. CONNECT over MCP (preferred). Add the superagnt MCP server, then let the client
run OAuth on first tool call — no token to paste:
claude mcp add --scope user --transport http superagnt https://mcp.superagnt.com/mcp
claude mcp login superagnt
MCP endpoint: https://mcp.superagnt.com/mcp
After connecting, the tool you want is named exactly:
data_linkedin_get_post_reactions
Call agnt_tools_search or agnt_tools_list_enabled to confirm it is available.
2. REST fallback (if you are not using MCP):
POST https://api.agntdata.dev/get-post-reactions
Header: Authorization: Bearer <YOUR_AGNTDATA_API_KEY>
Required parameters:
- (none)
Optional parameters:
- url (string, optional)
- page (integer, optional)
- reactionType (string, optional)
3. COST & KEY. This endpoint is priced per call in credits, and each successful response reports its own cost in its meta.costCents field. Only successful calls are charged.
Get an agntdata API key at https://app.agntdata.dev.
4. TEST. Connect the server (or set the key), discover the tool
(data_linkedin_get_post_reactions), run one minimal call with just the required parameters,
and report back the shape of the JSON response (top-level fields).
Reference (machine-readable variant): https://superagnt.com/docs/apis/social/linkedin/endpoints/Get_Post_Reactions.md{
"name": "get_post_reactions",
"description": "Get profiles that reacted to the post",
"parameters": {
"type": "object",
"properties": {
"url": {
"type": "string"
},
"page": {
"type": "integer"
},
"reactionType": {
"type": "string"
}
},
"required": []
}
}| Name | In | Type | Required | Description |
|---|---|---|---|---|
url | body | string | optional | |
page | body | integer | optional | |
reactionType | body | string | optional |
200
{
"type": "object",
"properties": {
"success": {
"type": "boolean"
},
"message": {
"type": "string"
},
"data": {
"type": "object",
"properties": {
"currentPage": {
"type": "integer"
},
"items": {
"type": "array",
"items": {
"type": "object"
}
},
"total": {
"type": "integer"
},
"totalPages": {
"type": "integer"
}
}
}
}
}This endpoint is priced per call and deducted from your agntdata balance; only a successful call is billed. Every billable response reports its own cost in meta.costCents.
Get a key at app.agntdata.dev.
start calling
Point your client at https://mcp.superagnt.com/mcp and your agent has this endpoint, plus every other source on one balance.