---
title: "MultiGroupPoster Public API: Versions and Deprecation"
description: "The read-only MultiGroupPoster info API: endpoints, cursor paging, how versions work and how long an old version keeps working after a new one."
url: https://multiplegroupposter.com/docs/api/
source: MultiGroupPoster (https://multiplegroupposter.com) - Markdown version of the page above, for LLMs.
---

# Public API: endpoints, versions and deprecation

Updated   October 29, 2026  · [Markdown version](https://multiplegroupposter.com/docs/api.md)

Short answer

MultiGroupPoster has a small read-only JSON API at https://multiplegroupposter.com/api/v1/ with prices, limits, MCP details and a docs search. It needs no key. v1 is the current and only version. Breaking changes only come in a new version, and an old version keeps working for at least 6 months after the next one ships.

## Endpoints

No key is needed and nothing is stored. Answers and errors are JSON; an error looks like `{"error": {"code": "...", "message": "...", "hint": "..."}}`. The full description is in [/openapi.json](https://multiplegroupposter.com/openapi.json).

| Endpoint | Returns |
| --- | --- |
| `GET /api/v1/` | The list of endpoints |
| `GET /api/v1/pricing/` | Plans, prices in USD, refund and cancel rules |
| `GET /api/v1/limits/` | Daily limit, pacing, media, comments and other limits |
| `GET /api/v1/mcp/` | MCP server address, OAuth details and tools |
| `GET /api/v1/docs/?q=` | Docs search. Optional: `locale` (en, es, pt, fr, pl), `limit` (1 to 10), `cursor` |
| `GET` / `POST /ask` | The same docs search as an NLWeb endpoint |

## Paging through search results

`/api/v1/docs/` answers with up to `limit` results and a `next_cursor`. For the next results, send the same request again with `cursor` set to that value. When there is nothing more, `next_cursor` is `null`. A cursor only works with the same `q` and `locale`. Treat it as an opaque string.

## Versions

- The version is in the path: `/api/v1/`. v1 is the current and only version.
- Inside v1 we only add things: new fields, new endpoints, new optional parameters. Your code should ignore fields it does not know.
- A change that could break a working client, like removing or renaming a field, changing its type or meaning, or removing an endpoint, only ships under a new path such as `/api/v2/`.
- This policy covers `/api/v1/` and `/ask`. The MCP server is described on [MCP server](https://multiplegroupposter.com/docs/mcp/).

## Deprecation policy

- When a new version ships, the old one keeps working for at least 6 months.
- During those months every answer from the old version has a `Deprecation` header (RFC 9745), a `Sunset` header (RFC 8594) with the date it stops working, and a `Link` to the new version.
- The change and its dates are also listed below, under API changes.
- Today nothing is deprecated, so no answer has those two headers. Every answer links here with `Link: <https://multiplegroupposter.com/docs/api/>; rel="deprecation"`.

## API changes

| Date | Change |
| --- | --- |
| 2026-10-29 | `/api/v1/docs/` takes a `cursor` parameter and returns `next_cursor`. Nothing was removed. |
| 2026-10-28 | v1 published: `/api/v1/pricing/`, `/api/v1/limits/`, `/api/v1/mcp/`, `/api/v1/docs/` and `/ask`. |

For AI agents: every docs page has a Markdown copy (add `.md` to the path), the whole section is indexed in [/docs/llms.txt](https://multiplegroupposter.com/docs/llms.txt) and [/docs.json](https://multiplegroupposter.com/docs.json), and the MCP server is described on [/docs/mcp/](https://multiplegroupposter.com/docs/mcp/).

[Add to Chrome, free](https://chromewebstore.google.com/detail/multigroup-poster-%E2%80%93-faceb/bffigfjkllaipccbpnmckgfhmdmlgdda?utm_source=multiplegroupposter.com&utm_medium=page&utm_campaign=en-api)