Cubby Operator API

The Cubby Operator API is a JSON HTTP API — explicitly not RESTful — oriented around actions performed on system entities rather than transfer of state. Roughly 70 POST endpoints cover access codes, locks, organizations, managers, facilities, facility groups, units, pricing groups, customers, leads, leases, payment methods, ledgers, coverage, payments, auctions, notes, tasks, reports, storefront search, messaging and checkout. Responses are wrapped in a {status, data} envelope, money is expressed as integer cents, timestamps are ISO-8601 with facility-local or UTC semantics, and related entities are retrieved through explicit expansions.

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/cubby-operator-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.

API entry from apis.yml

apis.yml Raw ↑
name: Cubby Operator API
description: The Cubby Operator API is a JSON HTTP API — explicitly not RESTful — oriented around actions
  performed on system entities rather than transfer of state. Roughly 70 POST endpoints cover access codes,
  locks, organizations, managers, facilities, facility groups, units, pricing groups, customers, leads,
  leases, payment methods, ledgers, coverage, payments, auctions, notes, tasks, reports, storefront search,
  messaging and checkout. Responses are wrapped in a {status, data} envelope, money is expressed as integer
  cents, timestamps are ISO-8601 with facility-local or UTC semantics, and related entities are retrieved
  through explicit expansions.
humanURL: https://cubbystorage.github.io/docs/api/
baseURL: https://api.cubbystorage.com/v1
tags:
- Self Storage
- Facility Management
- Leases
- Payments
- Property Management
properties:
- type: Documentation
  url: https://cubbystorage.github.io/docs/api/
- type: APIReference
  url: https://cubbystorage.github.io/docs/api/
- type: Authentication
  url: authentication/cubby-authentication.yml
- type: ErrorCatalog
  url: errors/cubby-problem-types.yml
- type: Conventions
  url: conventions/cubby-conventions.yml
- type: DataModel
  url: data-model/cubby-data-model.yml
- type: Examples
  url: examples/cubby-examples.yml