canonical: https://jentic.com/apis/walls.io/walls

# Walls.io API

Walls.io API provides access to social wall posts, user management, analytics, and sponsored posts. Supports JSON and XML response formats. The API exposes 15 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a native post, list posts. Covers 15 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a native post
- List posts
- Get posts ordered by update time
- Update post visibility, pinned status, language, or spam flag
- Monitor Walls.io API operational status and events

## Use cases

### CRM Operations

Use the Walls.io API to perform crm operations programmatically. The API provides 15 endpoints covering core functionality including create a native post, list posts, get posts ordered by update time.

Example prompt: Call POST /posts to create a native post

### Automated Analytics Management

Automate analytics operations by combining multiple Walls.io API endpoints. Agents can list posts and then get posts ordered by update time in a single workflow.

Example prompt: Call GET /posts to list posts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Walls.io 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 'create a native post', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/posts` | Create a native post |
| GET | `/posts` | List posts |
| GET | `/posts/changed` | Get posts ordered by update time |
| GET | `/posts/{postId}` | Get a single post |
| PUT | `/posts/{postId}` | Update post visibility, pinned status, language, or spam flag |
| GET | `/posts.rss` | Get posts as RSS feed |
| GET | `/posts/changed.rss` | Get changed posts as RSS feed |
| POST | `/media_upload` | Upload image or video |

## Key resources

- **Analytics** — Operations related to Analytics
- **Media** — Operations related to Media
- **Posts** — Operations related to Posts
- **Sponsored Posts** — Operations related to Sponsored Posts
- **User Management** — Operations related to User Management

## 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:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/walls.io/walls/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 Walls.io API by hand means passing your access_token as a query parameter on the api.walls.io/v1 host and attaching it to every request yourself. Through Jentic you install once, import the Walls.io API from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** The Walls.io API puts the post id in the URL path (`/posts/{postId}`), so a rule can pin your agent to one post. You choose the operations it may call, so you can allow reading posts and creating a native post while an update to an existing post is not included unless you add it.
- **Credential handling:** Your Walls.io access 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 'create a native post' or 'list changed posts', and Jentic returns the matching Walls.io API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Walls.io API use?

The Walls.io API uses an API key passed in the `access_token` 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 create a native post with the Walls.io API?

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

### What are the rate limits for the Walls.io 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 create a native post through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a native post'. Jentic returns the matching Walls.io API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Walls.io API have?

The Walls.io API exposes 15 endpoints covering analytics, media, posts operations.

### Can I limit what my agent is allowed to do with the Walls.io API?

Yes. Because you self-host Jentic One, your own rules decide which Walls.io operations and credentials the agent may use. You can allow it to read posts with GET /posts and create a native post with POST /posts while leaving out updates to an existing post via PUT `/posts/{postId}` unless you add that. Since the post id sits in the URL path (`/posts/{postId}`), a rule can also pin the agent to a single post.