Skip to main content
POST
Update OAuth application

Authorizations

x-auth-apikey
string
header
required

Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Headers

x-auth-scheme
enum<string>
default:api-token
required

Authentication scheme identifier. Use api-token for standard API key authentication, partner-api-token for partner API key authentication. Must be paired with the x-auth-apikey header containing your API key.

Available options:
api-token,
api,
partner-api-token,
partner-api

Body

application/json

Request object for OAuth application management.

clientId
string<RUUID> | null
RUUID

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

contactEmail
string | null

Contact email for the OAuth application

Example:

"admin@myapp.com"

description
string | null

Description of the OAuth application

Example:

"Integration app for accessing Rhombus API"

name
string | null

Name of the OAuth application

Example:

"My Integration App"

redirectUri
string | null

OAuth redirect URI

Example:

"https://myapp.com/oauth/callback"

tokenEndpointAuthMethod
string | null

OAuth token endpoint auth method. 'none' registers a PUBLIC (PKCE-only) client with no secret; omit or 'client_secret_basic'/'client_secret_post' for a confidential client.

Example:

"none"

Response

200 - application/json

OK

Base response object denoting success, or failure with a reason, for an endpoint.

error
boolean | null
errorMsg
string | null
warningMsg
string | null
Last modified on August 21, 2026