[2] [[GitHub]] は [CODE(HTTP)@en[[[Bearer]]]] のような意味で
[CODE[[[token]]]] を使っています。

[FIG(quote)[
[FIGCAPTION[
[1] [CITE@en[Docker Hub API - Docker Documentation]]
([TIME[2015-03-26 12:53:56 +09:00]] 版)
<https://docs.docker.com/reference/api/docker-io_api/#authorize-a-token-for-a-library>
]FIGCAPTION]

> 
>     WWW-Authenticate: Token signature=123abc,repository="foo/bar",access=write
>     X-Docker-Token: signature=123abc,repository="foo/bar",access=write
>     X-Docker-Endpoints: registry-1.docker.io '''[''', registry-2.docker.io''']'''

]FIG]


[FIG(quote)[
[FIGCAPTION[
[3] [CITE@en[Docker Hub API - Docker Documentation]]
([TIME[2015-03-26 12:53:56 +09:00]] 版)
<https://docs.docker.com/reference/api/docker-io_api/#authorize-a-token-for-a-library>
]FIGCAPTION]

> 
>     Authorization: Token signature=123abc,repository="library/foobar",access=write

]FIG]


[FIG(quote)[
[FIGCAPTION[
[4] [CITE@en[Docker Registry API - Docker Documentation]]
([TIME[2015-03-26 12:53:56 +09:00]] 版)
<https://docs.docker.com/reference/api/registry_api/>
]FIGCAPTION]

> 
>     Authorization: Token signature=123abc,repository="foo/bar",access=read

]FIG]


[5] [CITE@en[Docker Hub and Registry Spec - Docker Documentation]]
([TIME[2015-03-26 12:53:56 +09:00]] 版)
<https://docs.docker.com/reference/api/hub_registry_spec/>

[FIG(quote)[
[FIGCAPTION[
[6] [CITE[Validic | Passing Tokens via Authorization HTTP]]
([TIME[2015-07-28 01:00:16 +09:00]] 版)
<https://support.validic.com/customer/portal/articles/1530226-passing-tokens-via-authorization-http>
]FIGCAPTION]

> curl -X GET -H 'Authorization: Token token={ACCESS_TOKEN}'
> https://api.validic.com/v1/organizations/{ORGANIZATION_ID}.json

]FIG]


[FIG(quote)[
[FIGCAPTION[
[7] [CITE@en[Making a Listing Recommendation API Call]]
([TIME[2015-07-21 03:40:19 +09:00]] 版)
<http://developer.ebay.com/devzone/listing-recommendation/Concepts/MakingACall.html>
]FIGCAPTION]

> HTTP Headers—Each Listing Recommendation API call requires an Authorization HTTP header. The Authorization token value should be pre-fixed by 'TOKEN', so the complete value looks like: TOKEN <authorization token value>.

]FIG]


[FIG(quote)[
[FIGCAPTION[
[8] [CITE@en[buddy-auth - Auth facilities for ring based apps.]]
([[Andrey Antukh, <niwi@niwi.nz>]] 著, [TIME[2015-08-02 19:24:39 +09:00]] 版)
<https://funcool.github.io/buddy-auth/latest/>
]FIGCAPTION]

> This is a possible aspect of the authorization header
> Authorization: Token 45c1f5e3f05d0

]FIG]


[FIG(quote)[
[FIGCAPTION[
[9] [CITE@en[Uber API Authentication Protocols]]
([TIME[2015-09-25 03:53:01 +09:00]] 版)
<https://developer.uber.com/v1/auth/>
]FIGCAPTION]

> In order to access protected resources you can pass your API Token, called a server_token. This must be passed as an Authorization header with type Token.
> Example:
> curl -H 'Authorization: Token YOUR_SERVER_TOKEN' \
> 'https://api.uber.com/v1/products?latitude=37.7759792&longitude=-122.41823'
> 

]FIG]


[FIG(quote)[
[FIGCAPTION[
[10] [CITE[NYPL Digital Collections API]]
([TIME[2016-03-31 01:21:59 +09:00]] 版)
<http://api.repo.nypl.org/>
]FIGCAPTION]

> In the examples below, 'abcdefghijklmn' is the authentication token you receive via email when you sign up for API access.
> Example curl request:
> curl "http://api.repo.nypl.org/api/v1/items/search?q=cats&publicDomainOnly=true" -H 'Authorization: Token token="abcdefghijklmn"'

]FIG]


[FIG(quote)[
[FIGCAPTION[
[11] [CITE@en[HSReplay.net/test_api.py at 1d65082485e319e2f0fe5192ebd6dd4a5c01a882 · HearthSim/HSReplay.net]]
([TIME[2017-02-23 17:53:38 +09:00]])
<https://github.com/HearthSim/HSReplay.net/blob/1d65082485e319e2f0fe5192ebd6dd4a5c01a882/tests/test_api.py>
]FIGCAPTION]

> 
> 		HTTP_AUTHORIZATION="Token %s" % (token),

]FIG]


[FIG(quote)[
[FIGCAPTION[
[12] [CITE@en[Running Build in Debug Mode - Travis CI]]
([TIME[2017-10-06 01:06:34 +09:00]])
<https://docs.travis-ci.com/user/running-build-in-debug-mode/>
]FIGCAPTION]

>   -H "Authorization: token ********************" \

]FIG]