Skip to main content
GET
/
oauth
/
authorize
Authorize
curl --request GET \
  --url https://api.nomos.energy/oauth/authorize
{
  "code": "BAD_REQUEST",
  "message": "invalid_type in 'end': Required",
  "requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
  "docs": "https://docs.nomos.energy/api-references/errors/BAD_REQUEST"
}

Documentation Index

Fetch the complete documentation index at: https://docs.nomos.energy/llms.txt

Use this file to discover all available pages before exploring further.

Query Parameters

​
response_type
enum<string>
required

The response type, must be 'code' for authorization code flow

Available options:
code
Example:

"code"

​
client_id
string
required

The client identifier issued to the client during registration

Example:

"client_12345"

​
redirect_uri
string<uri>
required

The URI to redirect to after authorization is complete

Example:

"https://your-app.com/callback"

​
scope
string
​
state
string

Optional value used by the client to maintain state between request and callback

Example:

"xcoiv98sj3coijs"

​
code_challenge
string

PKCE code challenge derived from the code verifier

Example:

"E9Melhoa2OwvFrEMTJguCHaoeK1t8URWbuGJSstw-cM"

​
code_challenge_method
enum<string>

Method used to derive the code challenge, either 'S256' or 'plain'

Available options:
S256,
plain
Example:

"S256"

​
flow_type
enum<string>

If you want to use Nomos as identity provider, you can support a login or signup flow via explicitly setting this parameter. In contrast to the default, the login options skips the consent screen. The signup options allows your users to create a new customer without a subscription attached to it, and therefore register an account.

Available options:
login,
signup
Example:

"login"

Response

Redirect to the defined redirect_uri