How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cubist OAuth2 API

The OAuth2 API from Cubist — 7 operation(s) for oauth2.

Cubist OAuth2 API is one of 30 APIs that Cubist publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 7 paths, and defines 57 schemas. It is described by OpenAPI 3.2.0, at version v0.1.0.

Requests are made against 2 base URLs: https://gamma.signer.cubist.dev, https://prod.signer.cubist.dev.

9 operations 7 paths 57 schemas 2 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0.1.0
Base URL
https://prod.signer.cubist.dev
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Cubist OAuth2 API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Oidc). An API key is passed in the header as Authorization (SignerAuth). By default, every request must be authenticated.

  • Oidc — OIDC tokens allow users to authenticate using a third-party service. These are exchanged for signer session tokens.
  • SignerAuth — Signing API end-points use session tokens for auth. Specifically, with each request you need to use the \token\ from your signer session (which you create with…

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 2 PATCH, 7 POST. Each is listed below with its method, path, parameters, and response codes.

OAuth2 9
POST
/v0/oauth/token
Token refresh endpoint, compliant with OAuth.
oauth2TokenRefresh body → 200default
POST
/v0/org/{org_id}/oauth2/twitter
Mint an OIDC ID token for Twitter
oauth2Twitter 2 params body → 200default
POST
/v0/org/{org_id}/oidc
Login with OIDC
oidcAuth 1 param body → 200202default
POST
/v0/org/{org_id}/oidc/email-otp
Initiate login via email token
emailOtpAuth 1 param body → 200default
POST
/v0/org/{org_id}/oidc/siwe
Initiate login via Sign-in With Ethereum (SIWE).
siweInit 1 param body → 200default
PATCH
/v0/org/{org_id}/oidc/siwe
Complete login via Sign-in With Ethereum (SIWE)
siweComplete 1 param body → 200default
POST
/v0/org/{org_id}/oidc/siws
Initiate login via Sign-in With Solana (SIWS).
siwsInit 1 param body → 200default
PATCH
/v0/org/{org_id}/oidc/siws
Complete login via Sign-in With Solana (SIWS)
siwsComplete 1 param body → 200default
POST
/v0/org/{org_id}/oidc/telegram
Allows a user to authenticate with the telegram API using the tgWebAppData value
telegramAuth 1 param body → 200default

Schemas 57

The contract defines 57 schemas that model the data the API accepts and returns. The most detailed are SignInInput (12 properties), MfaRequestInfo (11 properties), SiwsInitRequest (9 properties), SiweInitRequest (8 properties). Each schema is shown below with its type and property counts.

PreconditionErrorOwnCodes
string
TelegramAuthRequest
object
3 properties 3 required
BadRequestErrorCode
string
MfaRequiredArgs
object
5 properties 3 required
SiweCompleteRequest
object
Answer to a Sign-in with Ethereum challenge.
2 properties 2 required
SiweInitRequest
object
Initialize the request to sign in with ethereum. The response will contain a SIWE message that the client has to sign and submit via the corresponding PATCH en…
8 properties 3 required
PreconditionErrorCode
AcceptedValueCode
string
PolicyErrorOwnCodes
string
AcceptedValue
Different responses we return for success status codes.
ClientSessionMetadata
object
Attributes that are expected to be provided by the client
2 properties
ClientProfile
object
Client information representing the nature of front-end in [ClientSessionMetadata] and reflected in [SessionMetadata].
3 properties
Id
string
ForbiddenErrorCode
string
Seconds
integer
Duration measured in seconds A wrapper type for serialization that encodes a Duration as a u64 representing the number of seconds.
UnauthorizedErrorCode
string
SignerErrorOwnCodes
string
SignDryRunArgs
object
2 properties 1 required
AcceptedResponse
EpochDateTime
integer
DateTime measured in seconds since unix epoch. A wrapper type for serialization that encodes a [SystemTime] as a [u64] representing the number of seconds since…
SiwsCompleteRequest
object
Answer to a Sign-in with Solana challenge.
2 properties 2 required
RatchetConfig
object
4 properties
B32
string
Wrapper around a zeroizing 32-byte fixed-size array
CoinbaseDryRunArgs
object
2 properties 2 required
ErrorResponse
object
The structure of ErrorResponse must match the response template that AWS uses
5 properties 2 required
NotFoundErrorCode
string
ConflictErrorCode
string
SignerErrorCode
TokenRequest
object
2 properties 2 required
SolanaNetwork
string
The Solana network a SIWS message is bound to (the Chain ID field).
BybitDryRunArgs
object
3 properties 3 required
PolicyErrorCode
SiwsInitRequest
object
Initialize the request to sign in with Solana. The response will contain a structured SignInInput that the client must render to text, sign, and submit via the…
9 properties 2 required
SignInInput
object
The structured input to a Sign-In With Solana request (SolanaSignInInput in the spec). The relying party fills in domain/address/uri/... and the wallet renders…
12 properties 2 required
OsInfo
object
OS information set in [ClientSessionMetadata] and reflected in [SessionMetadata]
4 properties
MfaType
string
Different types that can be used to approve an MFA request
Scope
All scopes for accessing CubeSigner APIs
SolanaTxCmp
object
1 property
TimeoutErrorCode
string
HttpRequest
object
Information about the request. Captures all the relevant info (including the request body) about requests that require MFA. We use this to verify that when a r…
3 properties 2 required
HttpRequestCmp
How to compare HTTP requests when verifying MFA receipt (see [MfaRequest::verifyrequest])
EvmTxCmp
object
3 properties
NewSessionResponse
object
Information about a new session, returned from multiple endpoints (e.g., login, refresh, etc.).
5 properties 4 required
BinanceDryRunArgs
object
2 properties 2 required
ClientSessionInfo
object
Session information sent to the client. This struct works in tandem with its server-side counterpart [SessionData].
7 properties 7 required
TelegramEnvironment
string
Telegram has two environments: production and test Each one has an associated public key for verifying signatures, and we assign each one a unique OIDC issuer
BadGatewayErrorCode
string
ApprovalInfo
object
1 property 1 required
Receipt
object
Receipt that an MFA request was approved.
3 properties 3 required
EvmTxDepositErrorCode
string
OidcLoginRequest
OIDC login request
ExplicitScope
string
Explicitly named scopes for accessing CubeSigner APIs
MfaRequestInfo
object
Returned as a response from multiple routes (e.g., 'get mfa', 'approve mfa', 'approve totp').
11 properties 6 required
Status
object
6 properties 4 required
EmailOtpRequest
object
The request users send to initiate email OTP
1 property 1 required
RefreshGrantType
string
InternalErrorCode
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cubist-oauth2-api-openapi.yml Raw ↑

Other APIs Cubist publishes across the network.

Cubist Account API
Cubist Accounts API
Cubist Audit API
Cubist AuthMigration API
Cubist Babylon API
Cubist Contact API
Cubist Cube3Signer API
Cubist Identity API
Cubist Internal API
Cubist Keys API
Cubist Keys In Role API
Cubist Login API
Where this information came from

This is an independent, third-party profile of Cubist OAuth2 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.