Skip to content
← Documentation API documentation

Справочник API ExtensionFlow

Authenticated JSON and XML endpoints for integrations that need extension, release, update or changelog data.

01

What it is

A versioned API namespace under /api/v1 for extension, release, update and changelog data.

02

Why it helps

Internal tooling and trusted integrations can consume метаданные релизов without scraping public HTML pages.

03

How to call it

Send an Authorization: Bearer token header and request JSON endpoints or XML update output.

The API is intended for controlled integrations, automation and downstream tools. It is protected with bearer-token аутентификацией and rate limiting, while the public website remains focused on просмотре человеком and downloads.

Аутентификация

API requests require a bearer token. Tokens are validated by SHA256 hash, can be revoked and may have an expiry date.

Authorization: Bearer YOUR_API_TOKEN

JSON endpoints

MethodPathPurpose
GET/api/v1/extensionsList extensions with filters and pagination.
GET/api/v1/extensions/{id}Read one extension with detailed metadata.
GET/api/v1/releasesList releases with filters and pagination.
GET/api/v1/releases/{id}Read one release with detailed metadata and grouped changelog entries.
GET/api/v1/changelog/{releaseId}Read grouped changelog data, markdown and Joomla changelog node mappings.

Update XML endpoint

The API can also return generated update XML for a type and alias. The public Joomla update feed remains available under /updates when public delivery is enabled.

GET /api/v1/updates/{type}/{alias}?channel=stable

Пагинация

List endpoints accept per_page and return a pager object with the current page and total rows. The maximum per_page value is capped server-side.

GET /api/v1/releases?per_page=50