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

# VBOUT API

VBOUT marketing automation API providing programmatic access to social media, email marketing, and application data. The API exposes 19 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get authenticated user info, list social media channels. Covers 19 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get authenticated user info
- List social media channels
- Create a social media post
- Edit a social media post
- Monitor VBOUT API operational status and events

## Use cases

### Marketing Operations

Use the VBOUT API to perform marketing operations programmatically. The API provides 19 endpoints covering core functionality including get authenticated user info, list social media channels, get social media calendar.

Example prompt: Call GET `/App/Me` to get authenticated user info

### Automated Application Management

Automate application operations by combining multiple VBOUT API endpoints. Agents can list social media channels and then get social media calendar in a single workflow.

Example prompt: Call GET `/SocialMedia/Channels` to list social media channels, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call VBOUT 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/App/Me` | Get authenticated user info |
| GET | `/SocialMedia/Channels` | List social media channels |
| GET | `/SocialMedia/Calendar` | Get social media calendar |
| GET | `/SocialMedia/Stats` | Get social media statistics |
| GET | `/SocialMedia/GetPost` | Get a specific post |
| POST | `/SocialMedia/AddPost` | Create a social media post |
| POST | `/SocialMedia/EditPost` | Edit a social media post |
| DELETE | `/SocialMedia/DeletePost` | Delete a social media post |

## Key resources

- **Application** — Operations related to Application
- **Email Marketing** — Operations related to Email Marketing
- **Social Media** — Operations related to Social Media

## 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:** 48 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/vbout.com/vbout/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 the VBOUT API by hand means appending its api_key query parameter to every call against api.vbout.com and coding each social media channel, calendar, and post operation yourself. Through Jentic you install once, import the VBOUT API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** VBOUT social media operations carry the post and channel targets in the request body and query, so limit the agent to the operations it needs, such as listing channels or adding a post. You choose that allowed set, so writes like deleting a post are excluded unless you add them.
- **Credential handling:** Your VBOUT API key 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 'schedule a social media post' or 'get social channel stats', and Jentic returns the matching VBOUT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the VBOUT API use?

The VBOUT API uses an API key passed in the `api_key` query. 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 authenticated user info with the VBOUT API?

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

### What are the rate limits for the VBOUT 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 authenticated 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 authenticated user info'. Jentic returns the matching VBOUT API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the VBOUT API have?

The VBOUT API exposes 19 endpoints covering application, email marketing, social media operations.

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

Yes. Because you run Jentic One yourself, you decide which VBOUT operations the agent may call and which stored key it uses, so you can allow read-only calls like GET `/SocialMedia/Channels` and GET `/SocialMedia/Calendar` while withholding the rest. Write operations such as POST `/SocialMedia/AddPost` or DELETE `/SocialMedia/DeletePost` are only reachable if you add them to the allowed set. This lets an operator, for example, let an agent list channels and schedule posts without ever granting it the ability to delete a post.