ManyRequests API: which plan has it, what it does and where the docs are

Yes, ManyRequests has an API, and it needs Pro

Yes. ManyRequests has an API. The help center article on getting started with it, dated 29 April 2026, says the API is available only on the Pro plan. The plan comparison table on the pricing page agrees: the API row is unavailable on Core and available on Pro.

Pro costs $99 per month on monthly billing or $79 per month on annual billing, as read on 3 October 2026, with one team seat included. Core, at $59 or $39, does not include the API or webhooks.

One point is inconsistent. The Enterprise card on the same pricing page lists API access as an Enterprise benefit, and Enterprise starts at $1,000 per month. Two official sources place the API on Pro, so that is the reading used here. Confirm it with support before you buy Pro for the API alone.

How API access and authentication work

The official setup has three requirements:

1. A portal on the Pro plan.
2. An API token. Create it under Settings, then Integrations, then API, then Create token. Name it and copy it.
3. Your portal domain, which is the address your ManyRequests portal runs on.

Every call uses the token and the portal domain together. The API reference shows the base address as your portal domain followed by /api/v1. Treat the token like a password and keep it out of client-side code.

What the API covers, per the official documentation

The full reference is published at app.manyrequests.com/docs/v1/api. The help center says it lists all endpoints, request and response formats and code examples. This site has not made API calls. Rate limits were not stated on the pages read, so ask the vendor if you plan a high-volume sync.

Webhooks: seven events, Pro only

Webhooks push an event to a URL you choose, which saves you from polling the API. They are a Pro feature. To add one, open Settings, then Integrations, go to the Webhooks tab, click Add Webhook and enter a name, a URL and an event.

The help center example sends a webhook to Make, which then posts a Slack message when a new request arrives. Note there is no documented webhook for a completed request. A request updated event would have to be filtered by status on your side.

The MCP server for AI assistants

ManyRequests also documents an MCP server, which lets an AI assistant such as Claude or ChatGPT read and change portal data in plain language. It signs in with your portal login, so no API token is needed. The article lists what it cannot do: it cannot cancel subscriptions, refund or delete invoices, upload attachments, or change the credits on a request. The article does not say which plan includes it.

What to use if you are on Core

Core includes Zapier, which is enough for most simple automations. Triggers include request created, request completed, client created and payment created. Actions include creating a client, creating a request and updating a request status. The ManyRequests integrations overview has the full list and setup steps.

Upgrade to Pro for the API when you need something Zapier cannot do: a custom dashboard, a bulk import, or a sync that must react within seconds. The Core vs Pro comparison covers the other Pro features. If API access on a cheaper plan is the deciding factor, check the ManyRequests alternatives. Assembly, for example, lists API access from its Starter plan at $49 monthly or $29 per month annually.