Plexara
Sprout Social
- Catalog
- Sprout Social API v1
- Operations indexed
- 15
- Access
- Read
A knowledge page on the connection records how this organization reports those figures: which profiles belong together, which metrics the team actually uses, and the ways the API will return a successful-looking answer that is still the wrong number.
Endpoint surface
What the assistant can reach
| Area | Operations | Covers |
|---|---|---|
| Analytics | 2 | Owned-profile analytics by day and post-level analytics, with the metric set that belongs to each social network. |
| Listening | 2 | Messages and aggregated metrics for a Listening topic: volume, sentiment, network, language, and location. |
| Messages | 1 | Inbox messages across profiles, filtered by time, profile, type, and tag. |
| Cases | 1 | Customer care cases filtered by queue, status, priority, and assignee. |
| Publishing | 1 | A publishing post with its content, targets, and schedule. |
| Customer metadata | 8 | The account itself: profiles, profile groups, message tags, case queues, teams, users, and Listening topics. |
Example questions
Questions an assistant can answer
- How did impressions and engagement move across our Instagram profiles over the last 30 days?
- Which ten posts earned the most engagement this quarter, and on which network?
- Which profiles lost followers last month?
- How many open cases are sitting in each care queue right now?
- What is the daily volume and sentiment for our brand Listening topic this month?
- Which inbound messages carry the campaign tag we launched on Monday?
Knowledge pages
The knowledge on this connection
The profile analytics call will accept a monthly reporting period and still return a row per day. A knowledge page attached to the connection records that behavior, and every later session reads it before anyone reports a number.
1
A monthly request still comes back as daily rows
The call accepts a month as the reporting period and returns ordinary daily rows with no error. The page tells the assistant to read the dimensions in the response and add the days itself.
2
Some metrics arrive under a different name
A request for reach is answered under a unique-impressions key. Follower count arrives nested under a lifetime snapshot. A lookup against the name that was requested finds nothing. The page lists the remapped keys.
3
Daily unique reach does not add up to monthly reach
Summing thirty daily unique-reach values produces reach-days. The page tells the assistant to report daily reach as a daily figure, or to request one month-scoped value.
4
The last two days of any window are still settling
Follower growth comes back empty and some networks omit impressions until the data lands. The page tells the assistant to exclude or flag the trailing two days.
5
An empty profile is blank, never zero
A profile with nothing to report omits the metric or returns it empty. Averaging that in as zero understates the profiles that actually reported.
Combinations
Works with
A campaign, from spend to gift. Did the spring membership campaign work, and which channel carried it?
The full index of APIs in production is on the API connections page.
Plexara is not affiliated with or endorsed by Sprout Social. Sprout Social is a trademark of its owner.
Next
API connections
The APIs already in service, and the questions that use more than one of them in a single session.