domi/forgejo-domi
1
0
Fork 0
forked from forgejo/forgejo
Code Pull requests Activity

Added Table of Contents to long documentation pages (#13890)

Browse source 
* Redo #13836 with new shortcode
(https://gitea.com/gitea/theme/pulls/90)

* add Api Usage

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
This commit is contained in:
6543 2020-12-08 04:52:26 +00:00 • committed by GitHub
parent e7938c9c44
commit 6bdcacd73b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
20 changed files with 82 additions and 66 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/content/doc/developers/api-usage.en-us.md
View file

@ -13,7 +13,9 @@ menu:
identifier: "api-usage"
---
# Gitea API Usage
# API Usage
{{< toc >}}
## Enabling/configuring API access
@ -22,7 +24,7 @@ By default, `ENABLE_SWAGGER` is true, and
Sheet](https://docs.gitea.io/en-us/config-cheat-sheet/) for more
information.
## Authentication via the API
## Authentication
Gitea supports these methods of API authentication:
@ -39,7 +41,7 @@ Gitea parses queries and headers to find the token in
You can create an API key token via your Gitea installation's web interface:
`Settings | Applications | Generate New Token`.
### OAuth2
## OAuth2 Provider
Access tokens obtained from Gitea's [OAuth2 provider](https://docs.gitea.io/en-us/oauth2-provider) are accepted by these methods: