~sircmpwn/sr.ht-dev

1

Consider cURL examples for https://man.sr.ht/builds.sr.ht/

Details
Message ID
<1596225027.26636.0@typedspace.com>
DKIM signature
pass
Download raw message
Howdy,
I plan to fetch artifacts from my git repo's build and found the REST 
API.
It took me a few minutes to dig up the required authorization header.

I propose we do one or both.
State what header is expected for authentication.
Add a single paragraph documenting how to authenticate with the API.
Something like:
curl --oauth2-bearer $PERSONAL_TOKEN  https://builds.sr.ht/api/jobs | 
jq .total

Though, given plans for GraphQL support, I can defer any documentation 
contribution till then.

Best,
Eli

Re: Consider cURL examples for https://man.sr.ht/builds.sr.ht/

Details
Message ID
<C4L5ZH0C339G.1G5QAWEA9IPL@homura>
In-Reply-To
<1596225027.26636.0@typedspace.com> (view parent)
DKIM signature
pass
Download raw message
I don't want to duplicate this information through the docs - it's the
same for everything, so it's documented once for everything.
Export thread (mbox)