Cubi Estate

Cubi Estate Lead API

The Lead API from Cubi Estate — 7 operation(s) for lead.

GitHub OpenAPI

Operations 9

GET /lead/{token} Agent-facing lead brief (magic-link, mig 348) #
POST /lead/{token}/action Agent action on a lead brief: a=reply | a=decline&r= #
POST /lead/{token}/answer Agent answers the buyer on the lead brief — held for admin review (Secretary S2) #
POST /lead/{token}/schedule Agent accepts one proposed callback/meeting time, or declines them (Secretary… #
GET /lead/ics/{ics_token}.ics Calendar file for an ACCEPTED callback / meeting (Secretary S3) #
GET /lead/relay/{review_token} Admin review of an agent's answer before it reaches the buyer (side-effect-free… #
POST /lead/relay/{review_token} Admin Relay / Drop of a held agent answer (single use by state) #
GET /lead/approve/{approval_token} Admin one-time forward-approval confirm page (side-effect-free GET) #
POST /lead/approve/{approval_token} Admin one-time forward approval → sends the agent email #

Documentation

📖
Documentation
https://mcp.cubi.estate/docs

Specifications

⚙
OpenAPI
https://artifacts.apis.io/cubi-estate/openapi/cubi-estate-lead-api-openapi.yml

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/cubi-estate:cubi-estate-lead-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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

OpenAPI Specification

cubi-estate-lead-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Cubi Estate Lead API
  version: 0.1.0
  description: 'Operations tagged Lead across 2 of this provider''s published API definitions: cubi-estate-openapi.json, cubi-estate-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://mcp.cubi.estate
  description: Host serving this spec (Swagger UI at https://mcp.cubi.estate/docs loads /openapi.json); also hosts the MCP endpoint https://mcp.cubi.estate/mcp
tags:
- name: Lead
paths:
  /lead/{token}:
    get:
      summary: Agent-facing lead brief (magic-link, mig 348)
      operationId: lead_brief_page_lead__token__get
      parameters:
      - name: token
        in: path
        required: true
        schema:
          type: string
          title: Token
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
  /lead/{token}/action:
    post:
      summary: 'Agent action on a lead brief: a=reply | a=decline&r='
      operationId: lead_brief_action_lead__token__action_post
      parameters:
      - name: token
        in: path
        required: true
        schema:
          type: string
          title: Token
      - name: a
        in: query
        required: false
        schema:
          type: string
          default: ''
          title: A
      - name: r
        in: query
        required: false
        schema:
          type: string
          default: ''
          title: R
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
  /lead/{token}/answer:
    post:
      summary: Agent answers the buyer on the lead brief — held for admin review (Secretary S2)
      description: 'Brief token + not expired + LEAD_REPLY_RELAY_MODE on. The answer is

        stored HELD; nothing reaches the buyer until the admin relays it.'
      operationId: lead_brief_answer_lead__token__answer_post
      parameters:
      - name: token
        in: path
        required: true
        schema:
          type: string
          title: Token
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
  /lead/{token}/schedule:
    post:
      summary: Agent accepts one proposed callback/meeting time, or declines them (Secretary…
      description: 'Brief token + not expired + SECRETARY_SCHEDULING_ENABLED. Accept =

        ONE still-future slot (+ a valid meeting link for a meeting) → the buyer

        is told on their channels; a callback''s phone is shown only here, after

        acceptance. Decline → the buyer is told. Both single-use by state.'
      operationId: lead_brief_schedule_lead__token__schedule_post
      parameters:
      - name: token
        in: path
        required: true
        schema:
          type: string
          title: Token
      - name: a
        in: query
        required: false
        schema:
          type: string
          default: ''
          title: A
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
  /lead/ics/{ics_token}.ics:
    get:
      summary: Calendar file for an ACCEPTED callback / meeting (Secretary S3)
      operationId: lead_schedule_ics_lead_ics__ics_token__ics_get
      parameters:
      - name: ics_token
        in: path
        required: true
        schema:
          type: string
          title: Ics Token
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
  /lead/relay/{review_token}:
    get:
      summary: Admin review of an agent's answer before it reaches the buyer (side-effect-free…
      operationId: lead_relay_review_page_lead_relay__review_token__get
      parameters:
      - name: review_token
        in: path
        required: true
        schema:
          type: string
          title: Review Token
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
    post:
      summary: Admin Relay / Drop of a held agent answer (single use by state)
      operationId: lead_relay_review_action_lead_relay__review_token__post
      parameters:
      - name: review_token
        in: path
        required: true
        schema:
          type: string
          title: Review Token
      - name: a
        in: query
        required: false
        schema:
          type: string
          default: ''
          title: A
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
  /lead/approve/{approval_token}:
    get:
      summary: Admin one-time forward-approval confirm page (side-effect-free GET)
      operationId: lead_approve_page_lead_approve__approval_token__get
      parameters:
      - name: approval_token
        in: path
        required: true
        schema:
          type: string
          title: Approval Token
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
    post:
      summary: Admin one-time forward approval → sends the agent email
      operationId: lead_approve_send_lead_approve__approval_token__post
      parameters:
      - name: approval_token
        in: path
        required: true
        schema:
          type: string
          title: Approval Token
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Lead
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
x-refined-from:
- cubi-estate-openapi.json
- cubi-estate-openapi.yml