Every Past Post, One API Call
The History API retrieves published and scheduled posts across 13+ social networks, including content posted directly on the platforms before you integrated. Your product starts with a brand's full track record, not a blank slate.
13+
networks, one call
30M+
API calls per day
200-500
past posts per profile
1,000
posts per request
13+
networks, one call
30M+
API calls per day
200-500
past posts per profile
1,000
posts per request
Two Kinds of History, One Integration
When a user connects their Instagram or LinkedIn account, their content history didn't start today. The History API covers both sides of a profile's record.
Everything sent through Ayrshare
Every post published or scheduled via the API: status, platforms, schedule dates, approval trail, and platform post IDs. Filter by network, status, date range, or post type.
Everything on the network itself
Posts published directly on the social network, with engagement attached to each one. Posts that never touched Ayrshare are included, and the record reaches back before the account was connected: typically 200 to 500 past posts per profile.
From Brand Voice Training to Audit Trails
Train AI on real brand voice
An AI content agent without history writes generic content from post one. Pull a profile's last 200 to 500 posts at onboarding and your model learns tone, topics, hashtag patterns, and what performed, before it generates anything. No cold-start problem, no "paste 10 examples of your writing" onboarding step.
Skip the empty state
New users connect their accounts and immediately see their existing content inside your product. Calendars, content libraries, and archives populate from day one instead of starting blank.
Close the feedback loop
Combine history with engagement metrics to power performance dashboards, surface top posts, or feed a reinforcement loop: what was posted, how it performed, what to do differently next time.
Keep a complete content record
Track every post's lifecycle: pending, processing, success, error, paused, or awaiting approval, with the approval trail included (who approved or rejected, and when). Multi-tenant platforms get an auditable record per user profile without building one.
One GET Request, Filtered Your Way
Filter a profile's history, page through it with cursors, and look posts up by either your ID or the network's.
• Filter by platform, date range (ISO 8601), post status, or immediate vs. scheduled
• Retrieve up to 1,000 posts per request, with cursor-based pagination on platform endpoints
• Look up a single post by Ayrshare post ID or by the social network's own post ID
• Track auto-repost series by ID
• Scope any call to a managed account with a Profile-Key
# Request — a profile's Instagram history with engagementcurl -H "Authorization: Bearer API_KEY" \ -H "Profile-Key: CLIENT_PROFILE_KEY" \ "https://api.ayrshare.com/api/history/instagram" # Response{ "status": "success", "posts": [{ "post": "The #Mandalorian is on tonight", "created": "2025-05-20T17:26:03Z", "likeCount": 214, "commentsCount": 18, "mediaType": "IMAGE", "postUrl": "https://www.instagram.com/p/B5OB..." }], "meta": { "pagination": { "hasMore": true } }}
The Learn Step of the Full Social Loop
Posting is one piece. Ayrshare gives your product the whole loop, and it starts with history.
One API
Learn
Act
Observe
Stay safe
Learn
This pagePull a brand's post history to match its voice from the first draft, and see what performed.
Act
Publish and schedule across 13+ networks in a single call.
Observe
Read back live analytics to see what worked, then feed it into the next post.
Stay safe
Validate every post against each platform's rules before anything goes live.
Every history call includes
Up to 1,000 posts per request
Cursor-based pagination
Per-post engagement data
Profile-Key scoping
FAQs About the History API
Yes. The platform history endpoints (/history/instagram, /history/linkedin, and so on) return posts published directly on the social network, including content posted before the account was connected to Ayrshare.
The /history endpoint returns up to 1,000 posts per request. Platform endpoints typically retrieve 200 to 500 past posts per profile, with cursor-based pagination to page through results.
Yes. Platform history returns per-post metrics native to each network, such as likes, comments, shares, impressions, reactions, and video watch data where the network provides it.
Bluesky, Facebook, Google Business Profile, Instagram, LinkedIn, Pinterest, Reddit, Snapchat, Telegram, Threads, TikTok, X/Twitter, and YouTube.
One API key plus an optional Profile-Key scopes any history call to a specific managed account, so a multi-tenant platform can pull each client's history separately under one integration.
The History API is available on the Premium, Launch, Business, and Enterprise plans.
Start with history, not a blank slate.
Give your product every user's full content record from the first API call.