mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2025-02-20 11:44:09 +08:00
Merge in DNS/adguard-home from beta-client-2 to master Squashed commit of the following: commit b2640cc49a6c5484d730b534dcf5a8013d7fa478 Merge: 659def862 aef4659e9 Author: Eugene Burkov <e.burkov@adguard.com> Date: Tue Dec 29 19:23:09 2020 +0300 Merge branch 'master' into beta-client-2 commit 659def8626467949c35b7a6a0c99ffafb07b4385 Author: Eugene Burkov <e.burkov@adguard.com> Date: Tue Dec 29 17:25:14 2020 +0300 all: upgrade github actions node version commit b4b8cf8dd75672e9155da5d111ac66e8f5ba1535 Author: Vladislav Abdulmyanov <v.abdulmyanov@adguard.com> Date: Tue Dec 29 16:57:14 2020 +0300 all: beta client squashed
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.