mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2024-11-16 02:18:28 -07:00
3af079a81b
Merge in DNS/adguard-home from 2609-dns-answer-string to master Updates #2609. Squashed commit of the following: commit 1922f90c50f47735d8025d862fbf60bcf707140f Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Thu Jan 28 15:19:11 2021 +0300 querylog: stricter typing commit 6ef73a45d822f77cfda44d8c093f272704d5afb6 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Thu Jan 28 15:04:06 2021 +0300 querylog: make answer actually a string |
||
---|---|---|
.. | ||
.gitignore | ||
CHANGELOG.md | ||
index.html | ||
openapi.yaml | ||
package.json | ||
README.md | ||
yarn.lock |
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
yarn install
yarn start
- Open
http://localhost:4000/
Changelog
Here 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.