Read and post payments against tenant ledgers via the storEDGE API
domain: api.storedgefms.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with one-legged OAuth 1.0 using the company's API access ID and secret
Call GET /v1/:facility_id/ledgers or /ledgers/:id to retrieve current or specific ledger balances
Call POST /v1/:facility_id/ledgers/:ledger_id/make_payment to post a single payment, or /ledgers/pay_multiple_ledgers for batch payments
Call GET /v1/:facility_id/ledgers/:ledger_id/invoices and /invoices/:invoice_id/pdf to retrieve invoice records and PDFs
Use GET /v1/:facility_id/ledgers/:ledger_id/delinquency and /rate_changes to check status before processing a payment
Known gotchas
Collections are paginated at 100 items per page by default - paginate with per_page/page or you'll silently miss ledgers on large facilities
Use the updated_since query parameter for incremental syncs instead of pulling the full ledger collection on every run
Error code 6 ('Cannot Change Reservation') and code 7 ('Tenant Access Denied') are storEDGE-specific business rules, not generic HTTP errors - handle them distinctly from validation failures
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?