Cubist Accounts API

The Accounts API from Cubist — 1 operation(s) for accounts.

Operations 1

POST /v0/org/{org_id}/invitation/accept Accept an invitation #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/cubist-accounts-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

cubist-accounts-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: CubeSigner Account Accounts API
  description: The CubeSigner management and signing service.
  contact:
    name: Cubist Inc.
    email: hello@cubist.dev
  version: v0.1.0
servers:
- url: https://gamma.signer.cubist.dev
  description: Testing and staging environment
- url: https://prod.signer.cubist.dev
  description: Production environment
security:
- Cognito: []
tags:
- name: Accounts
paths:
  /v0/org/{org_id}/invitation/accept:
    post:
      tags:
      - Accounts
      summary: Accept an invitation
      description: 'Accept an invitation


        This endpoint allows idp users to register using a token they have received in their email'
      operationId: invitationAccept
      parameters:
      - name: org_id
        in: path
        description: Name or ID of the desired Org
        required: true
        schema:
          type: string
        example: Org#124dfe3e-3bbd-487d-80c0-53c55e8ab87a
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/InvitationAcceptRequest'
        required: true
      responses: {}
      security: []
components:
  schemas:
    AuthSource:
      type: object
      description: 'At redemption time, the user must provide a credential they wish to use to authenticate.

        This enum represents the two possible sources of authentication.'
      required:
      - kind
      - credential
      properties:
        credential:
          type: string
        kind:
          $ref: '#/components/schemas/AuthSourceKind'
    AuthSourceKind:
      type: string
      description: 'At redemption time, the user must provide a credential they wish to use to authenticate.

        This enum represents the two possible sources of authentication.'
      enum:
      - password
      - oidc
    InvitationAcceptRequest:
      type: object
      required:
      - token
      - auth
      properties:
        auth:
          $ref: '#/components/schemas/AuthSource'
        token:
          type: string
          description: Invitation token
  securitySchemes:
    Oidc:
      type: apiKey
      in: header
      name: Authorization
      description: OIDC tokens allow users to authenticate using a third-party service. These are exchanged for signer session tokens.
    SignerAuth:
      type: apiKey
      in: header
      name: Authorization
      description: 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 `cs token create`).