Sell retail/merchandise items and take rental-center payments through 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 via one-legged OAuth 1.0.
Call GET /v1/:facility_id/invoiceable_items/retail to list sellable retail items, and GET /v1/:facility_id/invoiceable_items/rental_center to filter to items eligible for Rental Center sale.
Pull GET /v1/:facility_id/invoiceable_items/services and /fees for the other invoiceable-item categories if the checkout flow needs them.
Charge a retail item to a tenant with POST /v1/:facility_id/invoiceable_items/retail_payment.
Confirm the resulting charge by retrieving the invoice via GET /v1/:facility_id/invoices/:id and its PDF via GET /v1/:facility_id/invoices/:invoice_id/pdf.
Known gotchas
retail_payment is scoped to retail items only — it is not the general-purpose ledger payment endpoint used for rent, so a retail/POS integration and a rent-payment integration need separate code paths.
Rental Center eligibility is a flag on invoiceable items; always filter through the rental_center endpoint rather than assuming all retail items qualify.
There's no documented endpoint for creating new retail items/SKUs — catalog management is store-admin-only inside storEDGE.
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?