MailMoo
Open MailMoo
DocumentationAPI referenceMCP
EndpointsSocial

List a person's posts

Reads the posts a person has published, newest first. Use it to find a post worth pulling engagement from, then pass its URL to the post endpoints.

GET/social.getUserPosts

Authorization

bearerAuth
AuthorizationBearer <token>

Enter your MailMoo API key (format: sk_live_...)

In: header

Query Parameters

senderProfileId*string
identifier*string

Who to read. Accepts a profile URL, a public identifier, or a profile ID.

Length1 <= length
limit?integer

Maximum number of posts to return (max 100)

Range1 <= value <= 100
Default10
cursor?string

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/social.getUserPosts?senderProfileId=string&identifier=string&input=%7B%22senderProfileId%22%3A%22string%22%2C%22identifier%22%3A%22string%22%2C%22limit%22%3A10%2C%22cursor%22%3A%22string%22%7D"
{  "items": [    {      "text": "string",      "url": "string",      "createdAt": "string",      "author": "string",      "commentCount": 0    }  ],  "cursor": null}

Read a post's engagement POST

Reads both the comments and the reactions on a post, kept apart. Comments are fetched first: if the daily search budget runs out partway, `reactionsSkippedDueToDailyLimit` says so rather than the reactions coming back silently empty.

Read a post POST

Reads a single post by URL. Unlike the engagement endpoints, this costs nothing against the sender profile's daily search budget, so it is the cheap way to confirm a post exists and is visible before pulling people from it.