Storable Leads & Reservations API

Lead pipeline - reservations, inquiries, waitlist.

Business capability
Opportunity & Pipeline Management BC-410.30

Operations 7

GET /{facility_id}/leads List leads #
POST /{facility_id}/leads Create a lead (inquiry, reservation, or waitlist entry) #
PATCH /{facility_id}/leads/{id} Update a lead #
DELETE /{facility_id}/leads/{id} Delete a lead #
GET /{facility_id}/leads/reservations List leads in reservation status #
GET /{facility_id}/leads/waitlist List waitlisted leads #
GET /companies/{company_id}/leads List leads across every facility in a company #

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-leads-reservations-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.

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

OpenAPI Specification

storable-leads-reservations-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Storable Edge (storEDGE) Leads & Reservations 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: Leads & Reservations
  description: Lead pipeline - reservations, inquiries, waitlist.
paths:
  /{facility_id}/leads:
    get:
      operationId: listLeads
      tags:
      - Leads & Reservations
      summary: List leads
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - $ref: '#/components/parameters/page'
      - $ref: '#/components/parameters/perPage'
      responses:
        '200':
          description: A page of leads.
          content:
            application/json:
              schema:
                type: object
                properties:
                  meta:
                    $ref: '#/components/schemas/Meta'
                  leads:
                    type: array
                    items:
                      $ref: '#/components/schemas/Lead'
    post:
      operationId: createLead
      tags:
      - Leads & Reservations
      summary: Create a lead (inquiry, reservation, or waitlist entry)
      parameters:
      - $ref: '#/components/parameters/facilityId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/LeadInput'
      responses:
        '201':
          description: Lead created.
  /{facility_id}/leads/{id}:
    patch:
      operationId: updateLead
      tags:
      - Leads & Reservations
      summary: Update a lead
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - name: id
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/LeadInput'
      responses:
        '200':
          description: Lead updated.
    delete:
      operationId: deleteLead
      tags:
      - Leads & Reservations
      summary: Delete a lead
      parameters:
      - $ref: '#/components/parameters/facilityId'
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '204':
          description: Lead deleted.
  /{facility_id}/leads/reservations:
    get:
      operationId: listReservationLeads
      tags:
      - Leads & Reservations
      summary: List leads in reservation status
      parameters:
      - $ref: '#/components/parameters/facilityId'
      responses:
        '200':
          description: Reservation leads.
  /{facility_id}/leads/waitlist:
    get:
      operationId: listWaitlistLeads
      tags:
      - Leads & Reservations
      summary: List waitlisted leads
      parameters:
      - $ref: '#/components/parameters/facilityId'
      responses:
        '200':
          description: Waitlisted leads.
  /companies/{company_id}/leads:
    get:
      operationId: listCompanyLeads
      tags:
      - Leads & Reservations
      summary: List leads across every facility in a company
      parameters:
      - $ref: '#/components/parameters/companyId'
      responses:
        '200':
          description: Company-wide leads.
components:
  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
    Lead:
      type: object
      properties:
        id:
          type: string
        status:
          type: string
          enum:
          - inquiry
          - reservation
          - waitlist
          - missed_move_in
          - current
        first_name:
          type: string
        last_name:
          type: string
        email:
          type: string
        phone:
          type: string
        unit_group_id:
          type: string
        source:
          type: string
    LeadInput:
      type: object
      properties:
        status:
          type: string
        first_name:
          type: string
        last_name:
          type: string
        email:
          type: string
        phone:
          type: string
        unit_group_id:
          type: string
        source:
          type: string
  parameters:
    facilityId:
      name: facility_id
      in: path
      required: true
      description: The storEDGE facility ID the request is scoped to.
      schema:
        type: string
    perPage:
      name: per_page
      in: query
      description: Items per page for paginated collection endpoints (default 100).
      schema:
        type: integer
        default: 100
    companyId:
      name: company_id
      in: path
      required: true
      description: The storEDGE company (multi-facility account) ID.
      schema:
        type: string
    page:
      name: page
      in: query
      description: Page number for paginated collection endpoints.
      schema:
        type: integer
        default: 1
  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.'