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 Login API

The Login API from Cubist — 2 operation(s) for login.

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

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

This API exposes 3 operations across 2 paths, and defines 56 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.

3 operations 2 paths 56 schemas 1 PATCH2 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 Login 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 3

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

Login 3
POST
/v0/org/{org_id}/idp/authenticate
Authenticate
idpAuthenticate 1 param body → 200default
POST
/v0/passkey
Initiate Login with Passkey
passkeyAuthInit body → 200default
PATCH
/v0/passkey
Complete Login with Passkey
passkeyAuthComplete body → 200default

Schemas 56

The contract defines 56 schemas that model the data the API accepts and returns. The most detailed are MfaRequestInfo (11 properties), ClientSessionInfo (7 properties), Status (6 properties), PublicKeyCredentialRequestOptions (6 properties). Each schema is shown below with its type and property counts.

PreconditionErrorOwnCodes
string
BadRequestErrorCode
string
MfaRequiredArgs
object
5 properties 3 required
PreconditionErrorCode
AcceptedValueCode
string
PolicyErrorOwnCodes
string
ClientSessionMetadata
object
Attributes that are expected to be provided by the client
2 properties
AcceptedValue
Different responses we return for success status codes.
ClientProfile
object
Client information representing the nature of front-end in [ClientSessionMetadata] and reflected in [SessionMetadata].
3 properties
Id
string
ForbiddenErrorCode
string
PublicKeyCredential
object
This type represents a wire-encodable form of the PublicKeyCredential interface Clients may need to manually encode into this format to communicate with the se…
3 properties 2 required
UnauthorizedErrorCode
string
AuthenticationRequest
object
The request body for the idp authenticate endpoint
2 properties 2 required
SignerErrorOwnCodes
string
SignDryRunArgs
object
2 properties 1 required
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…
Status
object
6 properties 4 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
AuthenticatorAssertionResponse
object
Represents the assertion response used by clients when attempting to log in with a known credential https://www.w3.org/TR/webauthn-2/authenticatorassertionresp…
4 properties 3 required
SignerErrorCode
UserVerificationRequirement
string
A WebAuthn Relying Party may require user verification for some of its operations but not for others, and may use this type to express its needs. https://www.w…
BybitDryRunArgs
object
3 properties 3 required
PolicyErrorCode
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
AuthenticatorAttestationResponse
object
The AuthenticatorAttestationResponse interface represents the authenticator's response to a client’s request for the creation of a new public key credential. I…
2 properties 2 required
SolanaTxCmp
object
1 property
AuthenticatorTransport
string
Authenticators may implement various transports for communicating with clients. This enumeration defines hints as to how clients might communicate with a parti…
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])
PasskeyAssertAnswer
object
Sent from the client to the server to answer a fido challenge
2 properties 2 required
PublicKeyCredentialType
string
This enumeration defines the valid credential types. It is an extension point; values can be added to it in the future, as more credential types are defined. T…
EvmTxCmp
object
3 properties
PublicKeyCredentialDescriptor
object
This dictionary contains the attributes that are specified by a caller when referring to a public key credential as an input parameter to the create() or get()…
3 properties 2 required
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
BadGatewayErrorCode
string
ChallengePieces
object
Describes how to derive a WebAuthn challenge value.
2 properties 2 required
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
PublicKeyCredentialRequestOptions
object
The PublicKeyCredentialRequestOptions dictionary supplies get() with the data it needs to generate an assertion. Its challenge member MUST be present, while it…
6 properties 1 required
LoginRequest
InternalErrorCode
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cubist-login-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 Metrics API
Where this information came from

This is an independent, third-party profile of Cubist Login 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.