Storable

Storable Ledgers & Payments API

Tenant ledgers, payments, payment methods, invoices.

GitHub OpenAPI
Business capability
Accounts Receivable Management BC-200.30

Operations 10

GET /{facility_id}/ledgers List tenant ledgers #
GET /{facility_id}/ledgers/{id} Get a ledger by ID #
POST /{facility_id}/ledgers/{ledger_id}/make_payment Make a payment against a ledger #
PUT /{facility_id}/ledgers/{ledger_id}/update_autopay Enable, disable, or update autopay on a ledger #
GET /{facility_id}/tenants/{tenant_id}/payment_methods List a tenant's stored payment methods #
POST /{facility_id}/tenants/{tenant_id}/payment_methods Add a payment method for a tenant #
GET /{facility_id}/payment_intents List payment intents #
GET /{facility_id}/invoices/{id} Get an invoice by ID #
GET /{facility_id}/invoiceable_items List invoiceable items (fees, retail, insurance, services) #
POST /{facility_id}/authorize_funds Authorize funds on a payment method (e.g. digital wallet) #

Documentation

📖
APIReference
https://api.storedgefms.com/docs/v1.html

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/storable/refs/heads/main/openapi/storable-ledgers-payments-api-openapi.yml

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/storable-ledgers-payments-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.

GitHub Google LinkedIn

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

OpenAPI Specification

storable-ledgers-payments-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Storable Edge (storEDGE) Ledgers & Payments API
  description: A representative OpenAPI reference for the Storable Edge (storEDGE) REST API, the modern property-management API in the Storable brand family (SiteLink, storEDGE, SpareFoot).
  version: '1.0'
  contact:
    name: Storable
    url: https://www.storable.com/products/edge/
servers:
- url: https://api.storedgefms.com/v1
  description: Storable Edge (storEDGE) production API, one-legged OAuth 1.0
security:
- oauth1: []
tags:
- name: Ledgers & Payments
  description: Tenant ledgers, payments, payment methods, invoices.
paths:
  /{facility_id}/ledgers:
    get:
      operationId: listLedgers
      tags:
      - Ledgers & Payments
      summary: List tenant ledgers
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - $ref: '#/components/parameters/page'
      - $ref: '#/components/parameters/perPage'
      responses:
        '200':
          description: A page of ledgers.
          content:
            application/json:
              schema:
                type: object
                properties:
                  meta:
                    $ref: '#/components/schemas/Meta'
                  ledgers:
                    type: array
                    items:
                      $ref: '#/components/schemas/Ledger'
  /{facility_id}/ledgers/{id}:
    get:
      operationId: getLedger
      tags:
      - Ledgers & Payments
      summary: Get a ledger by ID
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: The ledger.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Ledger'
  /{facility_id}/ledgers/{ledger_id}/make_payment:
    post:
      operationId: makeLedgerPayment
      tags:
      - Ledgers & Payments
      summary: Make a payment against a ledger
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - name: ledger_id
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PaymentInput'
      responses:
        '200':
          description: Payment result.
  /{facility_id}/ledgers/{ledger_id}/update_autopay:
    put:
      operationId: updateLedgerAutopay
      tags:
      - Ledgers & Payments
      summary: Enable, disable, or update autopay on a ledger
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - name: ledger_id
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                enabled:
                  type: boolean
                payment_method_id:
                  type: string
      responses:
        '200':
          description: Autopay updated.
  /{facility_id}/tenants/{tenant_id}/payment_methods:
    get:
      operationId: listTenantPaymentMethods
      tags:
      - Ledgers & Payments
      summary: List a tenant's stored payment methods
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - $ref: '#/components/parameters/tenantId'
      responses:
        '200':
          description: Payment methods.
    post:
      operationId: createTenantPaymentMethod
      tags:
      - Ledgers & Payments
      summary: Add a payment method for a tenant
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - $ref: '#/components/parameters/tenantId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PaymentMethodInput'
      responses:
        '201':
          description: Payment method created.
  /{facility_id}/payment_intents:
    get:
      operationId: listPaymentIntents
      tags:
      - Ledgers & Payments
      summary: List payment intents
      parameters:
      - $ref: '#/components/parameters/facilityId'
      responses:
        '200':
          description: Payment intents.
  /{facility_id}/invoices/{id}:
    get:
      operationId: getInvoice
      tags:
      - Ledgers & Payments
      summary: Get an invoice by ID
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: The invoice.
  /{facility_id}/invoiceable_items:
    get:
      operationId: listInvoiceableItems
      tags:
      - Ledgers & Payments
      summary: List invoiceable items (fees, retail, insurance, services)
      parameters:
      - $ref: '#/components/parameters/facilityId'
      responses:
        '200':
          description: Invoiceable items.
  /{facility_id}/authorize_funds:
    post:
      operationId: authorizeFunds
      tags:
      - Ledgers & Payments
      summary: Authorize funds on a payment method (e.g. digital wallet)
      parameters:
      - $ref: '#/components/parameters/facilityId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                payment_method_id:
                  type: string
                amount:
                  type: number
      responses:
        '200':
          description: Authorization result.
components:
  parameters:
    tenantId:
      name: tenant_id
      in: path
      required: true
      schema:
        type: string
    perPage:
      name: per_page
      in: query
      description: Items per page for paginated collection endpoints (default 100).
      schema:
        type: integer
        default: 100
    facilityId:
      name: facility_id
      in: path
      required: true
      description: The storEDGE facility ID the request is scoped to.
      schema:
        type: string
    page:
      name: page
      in: query
      description: Page number for paginated collection endpoints.
      schema:
        type: integer
        default: 1
  schemas:
    Meta:
      type: object
      description: Every storEDGE response body includes a meta hash with request parameters, method, pagination, and status/error details.
      properties:
        status_code:
          type: integer
        status_message:
          type: string
        error_code:
          type:
          - integer
          - 'null'
        request_id:
          type: string
        page:
          type: integer
        per_page:
          type: integer
        total_count:
          type: integer
    Ledger:
      type: object
      properties:
        id:
          type: string
        tenant_id:
          type: string
        unit_id:
          type: string
        balance:
          type: number
        next_due_date:
          type: string
          format: date
        autopay_enabled:
          type: boolean
        delinquent:
          type: boolean
    PaymentInput:
      type: object
      properties:
        payment_method_id:
          type: string
        amount:
          type: number
    PaymentMethodInput:
      type: object
      properties:
        type:
          type: string
          enum:
          - credit_card
          - ach
          - digital_wallet
        token:
          type: string
  securitySchemes:
    oauth1:
      type: http
      scheme: oauth1
      description: 'Non-standard OpenAPI representation of storEDGE''s actual scheme: one-legged OAuth 1.0. The API access key issued to a storEDGE customer is used as the OAuth consumer key and the API secret key as the consumer secret, signing each request; there is no three-legged redirect/token exchange.'