canonical: https://jentic.com/apis/vision6.com.au/vision6-com-au

# Vision6 JSON-RPC API

The Vision6 email marketing platform API. Uses JSON-RPC over HTTP POST. All requests go to a single endpoint with a method name and parameters. Vision6 is now owned by Constant Contact. The API exposes 12 endpoints secured with apiKey authentication.

## For AI agents

Programmatically call a vision6 json-rpc method, add contacts to a list. Covers 12 operations with apiKey authentication.

## Scope

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

## Capabilities

- Call a Vision6 JSON-RPC method
- Add contacts to a list
- Search contacts in a list
- Edit contacts in a list
- Delete contacts from a list
- Get contact by ID
- Unsubscribe a contact

## Use cases

### Marketing Operations

Use the Vision6 JSON-RPC API to perform marketing operations programmatically. The API provides 12 endpoints covering core functionality including call a vision6 json-rpc method, add contacts to a list, search contacts in a list.

Example prompt: Call POST / to call a vision6 json-rpc method

### Automated API Management

Automate API operations by combining multiple Vision6 JSON-RPC API endpoints. Agents can add contacts to a list and then search contacts in a list in a single workflow.

Example prompt: Call POST /?method=addContacts to add contacts to a list, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Vision6 JSON-RPC 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 'call a vision6 json-rpc method', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/` | Call a Vision6 JSON-RPC method |
| POST | `/?method=addContacts` | Add contacts to a list |
| POST | `/?method=searchContacts` | Search contacts in a list |
| POST | `/?method=editContacts` | Edit contacts in a list |
| POST | `/?method=deleteContacts` | Delete contacts from a list |
| POST | `/?method=getContactById` | Get contact by ID |
| POST | `/?method=unsubscribeContact` | Unsubscribe a contact |
| POST | `/?method=addList` | Create a new list |

## Key resources

- **API** — Operations related to API
- **Account** — Operations related to Account
- **Contacts** — Operations related to Contacts
- **Lists** — Operations related to Lists
- **Transactional** — Operations related to Transactional

## 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:** 60 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 57 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/vision6.com.au/vision6-com-au/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 Vision6 JSON-RPC API by hand means passing its API-key request header, packing each method name and its arguments into the JSON-RPC body, and posting to the single endpoint yourself. Through Jentic you install once, import the Vision6 JSON-RPC API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Vision6 is a JSON-RPC service where the method and its contact targets travel in the request body rather than the URL path, so scope the agent to the operations it needs, such as adding or searching contacts. You choose that set, so a destructive operation like deleting contacts is not included unless you add it.
- **Credential handling:** Your Vision6 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 'add a contact to a list' or 'search contacts', and Jentic returns the matching Vision6 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 Vision6 JSON-RPC API use?

The Vision6 JSON-RPC API uses an API key passed in the `X-Api-Key` 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 call a vision6 json-rpc method with the Vision6 JSON-RPC API?

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

### What are the rate limits for the Vision6 JSON-RPC 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 call a vision6 json-rpc method through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'call a vision6 json-rpc method'. Jentic returns the matching Vision6 JSON-RPC API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Vision6 JSON-RPC API have?

The Vision6 JSON-RPC API exposes 12 endpoints covering API, account, contacts operations.

### Can I limit what my agent is allowed to do with the Vision6 JSON-RPC API?

Yes. Because Vision6 is a JSON-RPC service where the method name and its contact targets travel in the request body, Jentic One, which you self-host, lets you decide exactly which operations your agent may call. Your own rules scope the agent to the methods it needs, such as adding contacts to a list or searching contacts, and a destructive operation like deleting contacts stays out of reach unless you add it. Jentic One also holds your API key and injects it only for the operations you have allowed.