Skip to content
Omniglass Omniglass Omniglass

Create one of your own API tokens

POST
/auth/me/tokens
 
curl --request POST \
  --url https://example.com/api/v1/auth/me/tokens \
  --header 'Content-Type: application/json' \
  --data '{ "description": "example", "ttl_days": 1 }'

Mints a CLI/API token for the caller and returns it once (store it now; it cannot be retrieved again). A description is required (what the token is for); an optional ttl_days bounds its lifetime (default 90, maximum 365). Requires authentication; self-scoped (always issued for you). The token is stamped with the device and address that created it.

Request Body required

Section titled “Request Body required ”
Media type application/json
object
$schema

A URL to the JSON Schema for this object.

string format: uri
description
required

What the token is for (required)

string
>= 1 characters <= 200 characters
ttl_days

Days until the token expires (default 90, maximum 365)

integer format: int64
>= 1 <= 365

Responses

Section titled “ Responses ”

201

Section titled “201 ”

Created

Media type application/json
object
$schema

A URL to the JSON Schema for this object.

string format: uri
description
required

What the token is for

string
expires_at
required

When the token expires (RFC 3339)

string
prefix
required

The non-secret ogp locator for the new token

string
token
required

The bearer token, shown once. Store it now: it cannot be retrieved again.

string
Example 
{
  "$schema": "/api/v1/schemas/CreateMeTokenOutputBody.json"
}

default

Section titled “default ”

Error

Media type application/problem+json
object
$schema

A URL to the JSON Schema for this object.

string format: uri
detail

A human-readable explanation specific to this occurrence of the problem.

string
errors

Optional list of individual error details

Array<object> | null
object
location

Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’

string
message

Error message text

string
value

The value at the given location

instance

A URI reference that identifies the specific occurrence of the problem.

string format: uri
status

HTTP status code

integer format: int64
title

A short, human-readable summary of the problem type. This value should not change between occurrences of the error.

string
type

A URI reference to human-readable documentation for the error.

string format: uri
default: about:blank
Example 
{
  "$schema": "/api/v1/schemas/ErrorModel.json",
  "detail": "Property foo is required but is missing.",
  "instance": "https://example.com/error-log/abc123",
  "status": 400,
  "title": "Bad Request",
  "type": "about:blank"
}