mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2025-10-26 11:27:18 +00:00
Merge in DNS/adguard-home from next-fix-ups-logger to master
Squashed commit of the following:
commit 94a0c3508cb16e1b4e7f7793b1ee6a8da0c24de7
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Jun 27 18:11:12 2025 +0300
next: typos
commit 6358dc11c90464b3464d39eb302e5265a3e61cdd
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Jun 27 17:32:03 2025 +0300
next: imp upstream; add more settings
|
||
|---|---|---|
| .. | ||
| CHANGELOG.md | ||
| index.html | ||
| next.yaml | ||
| openapi.yaml | ||
| 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.
Changelog
See CHANGELOG.md where we keep track of all non-compatible changes that are being made.
Authentication
If AdGuard Home’s 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.