canonical: https://jentic.com/apis/sproutsocial.com/sproutsocial

# Sprout Social API

Sprout Social API provides access to social media management features including analytics, messaging, publishing, listening, and case management across multiple social networks. The API exposes 20 endpoints secured with bearer authentication.

## For AI agents

Programmatically retrieve customer ids and names accessible to user, list all social profiles with metadata for a customer. Covers 20 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Retrieve customer IDs and names accessible to user
- List all social profiles with metadata for a customer
- Integrate Sprout Social API into automated workflows
- Query and filter Sprout Social API records by parameters
- Monitor Sprout Social API operational status and events

## Use cases

### Analytics Operations

Use the Sprout Social API to perform analytics operations programmatically. The API provides 20 endpoints covering core functionality including retrieve customer ids and names accessible to user, list all social profiles with metadata for a customer, retrieve all tags (active and archived).

Example prompt: Call GET /v1/metadata/client to retrieve customer ids and names accessible to user

### Automated Analytics Management

Automate analytics operations by combining multiple Sprout Social API endpoints. Agents can list all social profiles with metadata for a customer and then retrieve all tags (active and archived) in a single workflow.

Example prompt: Call GET /v1/{customerId}/metadata/customer to list all social profiles with metadata for a customer, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sprout Social API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'retrieve customer ids and names accessible to user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/metadata/client | Retrieve customer IDs and names accessible to user |
| GET | /v1/{customerId}/metadata/customer | List all social profiles with metadata for a customer |
| GET | /v1/{customerId}/metadata/customer/tags | Retrieve all tags (active and archived) |
| GET | /v1/{customerId}/metadata/customer/groups | List customer groups |
| GET | /v1/{customerId}/metadata/customer/users | List active users |
| GET | /v1/{customerId}/metadata/customer/topics | List listening topics with theme groups |
| GET | /v1/{customerId}/metadata/customer/teams | List active teams |
| GET | /v1/{customerId}/metadata/customer/queues | List case queues |

## Key resources

- **Analytics** — Operations for analytics
- **Cases** — Operations for cases
- **Listening** — Operations for listening
- **Media** — Operations for media
- **Messages** — Operations for messages

## Why Jentic

- **Setup:** Wiring Sprout Social by hand means learning its bearer auth against api.sproutsocial.com and threading the customer id into every metadata path yourself. Through Jentic you install once, import the Sprout Social API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Sprout Social puts the customer id in the URL path (/v1/{customerId}/metadata/customer/...), so a rule can pin your agent to one customer profile. You choose the operations it may call, and since every endpoint here is a read such as listing tags, groups, or users, the agent only retrieves metadata unless you add more.
- **Credential handling:** Your Sprout Social bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list the customer profiles I can access' or 'get the tags for this customer', and Jentic returns the matching Sprout Social operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Sprout Social API use?

The Sprout Social API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I retrieve customer ids and names accessible to user with the Sprout Social API?

Yes. Use the GET /v1/metadata/client endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Sprout Social API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I retrieve customer ids and names accessible to user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve customer ids and names accessible to user'. Jentic returns the matching Sprout Social API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sprout Social API have?

The Sprout Social API exposes 20 endpoints covering analytics, cases, listening operations.

### Can I limit what my agent is allowed to do with the Sprout Social API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Sprout Social operations and credentials your agent may use. Since the customer id sits in the URL path (/v1/{customerId}/metadata/customer/...), a rule can pin the agent to a single customer profile, and you choose exactly which operations it can call. Every endpoint here is read-only, such as listing tags, groups, or users, so the agent only retrieves metadata unless you allow more.