Reinos.nl internet media add-ons

Webservice 10.0: every endpoint in view, with Try it, OpenAPI and rate limiting

6 November 2026

Good news for everyone who connects an app, a front end or another system to ExpressionEngine: Webservice v10.0 is here, with more than a hundred changes. You now see and manage every endpoint in the control panel, send a call with Try it, describe your API with OpenAPI and protect it with rate limiting. Less guessing about your API, more control over it.

Webservice 10.0: the endpoints overview, a Try it response and the cache page

Every endpoint in one overview

The add-on now opens on the new Endpoints page. It lists every endpoint of your APIs with its status, calls, errors, average duration, cache hits and last call, for the period you choose. Select endpoints to enable, disable or make them public in one go.

Your API tools get the same overview: download the OpenAPI 3 specification or expose it on /webservice/openapi.json, then import it in Postman or generate a client.

The Endpoints page with statistics per endpoint, next to the edit page of an endpoint

Try a call before you write code

Every endpoint has its own Try it page, which replaces the old Testing tools page. Send a request as yourself, with the credentials of a member or without any, and see the status, the duration, the headers and the formatted response. Copy the request as a cURL command, or pick one of your last five requests to send it again.

The Try it page of an endpoint with the request form and the response

Members, comments and categories in the box

The Member, Comment and Category API are now part of the module, so there are no separate packages to install or keep up to date. The Member API follows the registration rules of ExpressionEngine and protects Super Admins. The Comment API follows the rules of the comment form, including moderation, the spam service and the notifications. The Category API is read only and returns categories as a flat list or a tree.

Its own key for every app

Give every app a shortkey with a label, see when it was last used, and revoke it without touching the others. New secrets and shortkeys are generated for you and shown once, then stored as a hash. A member only reaches the APIs you selected for it.

Your credentials can now also travel in the request headers: Authorization: Bearer <shortkey>, Basic auth, X-Api-Key with X-Api-Secret, or X-Session-Id.

The Members page and the credentials of a member, with shortkeys that have a label and a last used date

Protected against overload and guessing

With rate limiting you set the calls per minute for each member, and for public endpoints per IP address. A call over the limit gets a 429 and is not run, and the X-RateLimit headers tell a client how many calls it has left. These two limits are off until you set them. Failed authentications are limited from the start: after ten in a minute by default, an IP address is locked out for the rest of that minute.

This release also improves the security of the authentication, the sessions, the public endpoints, the Entry API, the API logs and the credentials of the members, so we strongly recommend updating.

The rate limiting settings and the requests per minute of a single member

See what every call did

The new Log requests setting is on by default and logs every call with its HTTP status and duration, which is also where the statistics on the Endpoints page come from. The Api Logs page now has filters, bulk delete and a CSV export. Need to know why a call is slow or fails? Turn on Debug to log the queries and the response data too.

The Api Logs page with filters and HTTP statuses, next to the details of a single call

A cache that does its job

We also found a bug we have to be honest about: the response cache was never used or cleared. That is fixed, and the cache now works per member and per request. The new Cache page shows the cache and hit rate of every endpoint that can be cached, and each endpoint can have its own cache setting and cache time. Responses carry an X-Cache header, and the cache is cleared when an entry is saved or deleted. The cache stays off until you enable it in the settings.

The Cache page with the hit rate per endpoint, next to the cache settings

More highlights

Breaking changes to check before you upgrade

Want the complete picture? Every change is listed in the Webservice v10.0.0 changelog. Be sure to read Upgrading to 10.0 before you update, make a backup first and check your API clients afterwards. Curious how it all works together? The video is on the Webservice page. As always, the documentation comes with copy-paste examples, so you can get up and running in no time.

Back to all posts

More posts