Skip to main content
AI Puffer exposes REST endpoints under the WordPress REST API. Use the API when an external application needs to generate text, generate images, create embeddings, send a message to a chatbot, read chat logs, or add content to a vector store. Base URL:

Authentication

Most endpoints require the AI Puffer REST API key.
  1. Open WordPress Admin > AI Puffer > Settings.
  2. Open Developers.
  3. Enter a value in REST API Key.
  4. Wait for the setting to save.
Developer Settings with the REST API Key field
Leaving the field blank disables REST API access. Treat the key like a password. Anyone with the key can call the enabled REST endpoints from outside WordPress.

Send the key in a header

Use an Authorization header when possible.

Send the key as a request parameter

You can also send the key as aipkit_api_key.

Endpoints

Text generation

Generate a text response with one of the configured text providers.

Parameters

Request

Response

Image generation

Generate images from a text prompt.

Parameters

Request

Response

Embeddings

Create embeddings from one string or an array of strings.

Parameters

Google task_type values:

Request

Response

Chat message

Send a message to one chatbot. The chatbot must exist in WordPress. The request uses the chatbot settings saved in AI Puffer.

Parameters

Request

Response

Chat logs

Read saved chatbot conversation logs.

Parameters

The response includes pagination headers:

Request

Response

Vector store upsert

Embed text and add the vectors to Pinecone, Qdrant, or Chroma. The target index or collection must already exist. AI Puffer creates embeddings, then sends vectors to the selected vector database.

Parameters

Each vectors item must include:

Request

Response

Chatbot embed config

Read the config and rendered HTML for an externally embedded chatbot. This endpoint is not authenticated with the REST API key. Access is controlled by the chatbot’s embed settings and allowed domains.

Parameters

Response

If the request origin is not allowed, the endpoint returns 403.

Error format

Errors use the standard WordPress REST error format.