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

Storable Ledgers & Payments API

Tenant ledgers, payments, payment methods, invoices.

Storable Ledgers & Payments API is one of 11 APIs that Storable publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Ledgers & Payments. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

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

Requests are made against a single base URL, https://api.storedgefms.com/v1.

10 operations 9 paths 4 schemas 6 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.storedgefms.com/v1
Authentication
HTTP Oauth1
Contact
Resource Areas
1

Authentication & Security 1

Storable Ledgers & Payments API declares 1 security scheme for authenticating requests. It uses HTTP oauth1 authentication (oauth1). By default, every request must be authenticated.

  • oauth1 — 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 co…

Paths & Operations 10

Across 9 paths, the API surfaces 10 operations — 6 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Ledgers & Payments 10

Tenant ledgers, payments, payment methods, invoices.

GET
/{facility_id}/ledgers
List tenant ledgers
listLedgers 3 params → 200
GET
/{facility_id}/ledgers/{id}
Get a ledger by ID
getLedger 2 params → 200
POST
/{facility_id}/ledgers/{ledger_id}/make_payment
Make a payment against a ledger
makeLedgerPayment 2 params body → 200
PUT
/{facility_id}/ledgers/{ledger_id}/update_autopay
Enable, disable, or update autopay on a ledger
updateLedgerAutopay 2 params body → 200
GET
/{facility_id}/tenants/{tenant_id}/payment_methods
List a tenant's stored payment methods
listTenantPaymentMethods 2 params → 200
POST
/{facility_id}/tenants/{tenant_id}/payment_methods
Add a payment method for a tenant
createTenantPaymentMethod 2 params body → 201
GET
/{facility_id}/payment_intents
List payment intents
listPaymentIntents 1 param → 200
GET
/{facility_id}/invoices/{id}
Get an invoice by ID
getInvoice 2 params → 200
GET
/{facility_id}/invoiceable_items
List invoiceable items (fees, retail, insurance, services)
listInvoiceableItems 1 param → 200
POST
/{facility_id}/authorize_funds
Authorize funds on a payment method (e.g. digital wallet)
authorizeFunds 1 param body → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Meta (7 properties), Ledger (7 properties), PaymentInput (2 properties), PaymentMethodInput (2 properties). Each schema is shown below with its type and property counts.

PaymentMethodInput
object
2 properties
Ledger
object
7 properties
PaymentInput
object
2 properties
Meta
object
Every storEDGE response body includes a meta hash with request parameters, method, pagination, and status/error details.
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

storable-ledgers-payments-api-openapi.yml Raw ↑

Other APIs Storable publishes across the network.

Storable Delinquency & Auctions API
Storable Documents & eSign API
Storable Gate Access API
Storable Insurance API
Storable Leads & Reservations API
Storable Move Ins & Outs API
Storable Reporting API
Storable Tasks API
Storable Tenants API
Storable Units & Rates API
Where this information came from

This is an independent, third-party profile of Storable Ledgers & Payments 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.