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

# RSS Ground API

RSS Ground API enables management of personal feeds, posting campaigns, and webhook notifications. All interactions require OAuth 2.0 authentication. The API exposes 7 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get user info, list personal feeds. Covers 7 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Get User Info
- List Personal Feeds
- Create Feed Item
- Subscribe to Webhook
- Unsubscribe from Webhook

## Use cases

### Communications Operations

Use the RSS Ground API to perform communications operations programmatically. The API provides 7 endpoints covering core functionality including get user info, list personal feeds, list campaigns.

Example prompt: Call GET /me to get user info

### Automated campaign Management

Automate campaign operations by combining multiple RSS Ground API endpoints. Agents can list personal feeds and then list campaigns in a single workflow.

Example prompt: Call GET `/me/feeds/personal` to list personal feeds, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RSS Ground 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'get user info', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Get User Info |
| GET | `/me/feeds/personal` | List Personal Feeds |
| GET | `/me/campaigns` | List Campaigns |
| GET | `/campaign/sampleresponse` | Get Sample Webhook Response |
| POST | `/feed/personal/item` | Create Feed Item |
| POST | `/campaign/webhook` | Subscribe to Webhook |
| DELETE | `/campaign/webhook` | Unsubscribe from Webhook |

## Key resources

- **campaign** — Operations related to campaign
- **feed** — Operations related to feed
- **me** — Operations related to me

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 73 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rssground.com/rssground/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring RSS Ground by hand means running its OAuth2 authorization-code flow against rssground.com/oauth and refreshing tokens yourself before each feed or campaign call. Through Jentic you install once, import RSS Ground from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** RSS Ground takes feed items and webhook targets in the request body, so scope the agent to the operations it needs, such as listing campaigns or creating a feed item. You pick that allowed set, so unsubscribing a webhook stays out unless you include it.
- **Credential handling:** Your RSS Ground OAuth credential 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 my personal feeds' or 'subscribe to a campaign webhook', and Jentic returns the matching RSS Ground operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the RSS Ground API use?

The RSS Ground API uses OAuth 2.0 for authorization. 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 get user info with the RSS Ground API?

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

### What are the rate limits for the RSS Ground 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 get user info through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get user info'. Jentic returns the matching RSS Ground API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the RSS Ground API have?

The RSS Ground API exposes 7 endpoints covering campaign, feed, me operations.

### Can I limit what my agent is allowed to do with the RSS Ground API?

Yes. Because Jentic One is self-hosted, your own rules decide which RSS Ground operations and credentials the agent may use. You can allow read-only calls like listing personal feeds or listing campaigns while withholding write actions such as creating a feed item or subscribing to a campaign webhook. Since you pick that allowed set, an operation like unsubscribing a webhook stays off limits unless you explicitly include it.