Deliver and collect e-signatures on move-in and lease documents through the storEDGE API
domain: api.storedgefms.com · 6 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/events/:event_id/documents to list the documents and IDs tied to a move-in or other event.
Fetch a specific document as a PDF with GET /v1/:facility_id/documents/:id (or the session-scoped variant for a move-in).
Request e-signable documents for the event with POST /v1/:facility_id/events/:event_id/esign.
Send the esignable documents to the tenant via email or SMS with POST /v1/:facility_id/documents/:event_id/send_esignable_documents.
Retrieve all documents tied to a ledger over time via GET /v1/:facility_id/ledgers/:ledger_id/documents.
Known gotchas
event_id refers to a storEDGE event (e.g., a move-in), not an arbitrary document ID — look it up via the move-in or lead endpoints first.
send_esignable_documents delivers via email or SMS only; there's no documented endpoint for embedding the esign flow directly in a third-party web page.
Document retrieval endpoints return PDFs, not structured lease data — individual lease terms can't be extracted via this API.
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?