AdGuardHome/openapi
Ainar Garipov 20e56b7171 Pull request 2326: more-md-lint
Merge in DNS/adguard-home from more-md-lint to master

Squashed commit of the following:

commit 39e7ea3b44
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Thu Dec 19 17:03:36 2024 +0300

    all: imp docs more

commit 7aa08036b2
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Thu Dec 19 16:08:13 2024 +0300

    all: add more docs to lint
2024-12-19 17:17:40 +03:00
..
CHANGELOG.md Pull request 2326: more-md-lint 2024-12-19 17:17:40 +03:00
README.md Pull request 2326: more-md-lint 2024-12-19 17:17:40 +03:00
index.html
openapi.yaml Pull request #2325: 7510 Fix openapi spec 2024-12-19 15:38:18 +03:00
package.json
v1.yaml
yarn.lock

README.md

AdGuard Home OpenAPI

We are using OpenAPI specification to generate AdGuard Home API specification.

How to edit the API spec

The easiest way would be to use Swagger Editor and just copy/paste the YAML file there.

How to read the API doc

  1. yarn install
  2. yarn start
  3. open http://localhost:4000/

Changelog

Here we keep track of all non-compatible changes that are being made.

Authentication

If AdGuard Homes web user is password-protected, a web client must use authentication mechanism when sending requests to server. Basic access authentication is the most simple method: a client must pass Authorization HTTP header along with all requests:

Authorization: Basic BASE64_DATA

Where BASE64_DATA is base64-encoded data for username:password string.