Releases Index
Mint a publish token
View .md

Mint a publish token for one of your sources

POST
/me/publish-tokens

Signed-in session only: the web cookie session, or the session token from releases login as a Bearer. API keys, machine tokens and OAuth access tokens are refused. Cookie requests must come from the web origin. Mints a relk_ token bound to one source, usable ONLY on that source's POST …/releases/batch route (e.g. from the publish-changelog GitHub Action). Requires a verified ownership claim on the source's organization; the token stops working if the claim or the source goes away. The plaintext token is returned once. At most 5 active publish tokens per source per user.

Authorization

bearerAuth
headerAuthorizationBearer <relk_… | relu_… | OAuth JWT>

Machine/operator tokens use the relk_ prefix; self-serve read-only user keys use relu_; Sign in with Releases supplies an OAuth access token. Required scope depends on the endpoint.

Request Body

application/json
  1. body
sourceId*string
Length1 <= length <= 64
name*string
Length1 <= length <= 200

Response Body

Created publish token, including the one-time secret

application/json
  1. response
token*string
id*string
sourceId*string
name*string
createdAt*string
Example Request
curl -X POST 'https://api.releases.sh/v1/me/publish-tokens' \  -H 'Content-Type: application/json' \  -d '{  "sourceId": "string",  "name": "string"}'
Example Response
{  "token": "string",  "id": "string",  "sourceId": "string",  "name": "string",  "createdAt": "string"}