xavio-in Leads API

Lead inbox + ingestion.

Operations 3

GET /api/v1/leads List leads for the caller's host #
POST /api/v1/leads Append a lead to one of your lead forms (scope leads:write). #
POST /api/v1/leads/outcome Report what a lead turned out to be worth (scope leads:write): won + value… #

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/xavio-in:xavio-in-leads-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

xavio-in-leads-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Nafafy Public Leads API
  version: 1.0.0
  description: 'Programmatic access to publish stories, manage products and variants, fulfil orders, run bookings and read analytics on Nafafy.


    - **REST** — `Authorization: Bearer nf_live_…` (or `nf_test_…`) with a key of kind **REST API** minted at https://nafafy.com/dashboard/developer. Each Series F operation names the scope it needs (`x-required-scope`); `x:write` implies `x:read`. `customers:pii` and `refunds:write` are standalone and never implied.

    - **MCP** — https://nafafy.com/api/mcp (JSON-RPC 2.0 over HTTP) needs a key of kind **MCP**; a REST key is refused there, and an MCP key is refused on REST (`wrong_kind`).


    Errors use the envelope `components.schemas.V1Error`; branch on `error.code`. Series F operations list every code they can answer in `x-error-codes` and their limit in `x-rate-limit`.'
  contact:
    name: Nafafy support
    url: https://nafafy.com/developers
servers:
- url: https://nafafy.com
  description: Production
security:
- bearerAuth: []
tags:
- name: Leads
  description: Lead inbox + ingestion.
paths:
  /api/v1/leads:
    get:
      summary: List leads for the caller's host
      tags:
      - Leads
      responses:
        '200':
          description: OK
      operationId: getApiV1Leads
      x-operation-id-source: derived
    post:
      summary: Append a lead to one of your lead forms (scope leads:write).
      tags:
      - Leads
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                form_id:
                  type: string
                  format: uuid
                values:
                  type: object
                  description: Keyed by the form's field ids.
                idempotency_key:
                  type: string
                utm:
                  type: object
              required:
              - form_id
              - values
      responses:
        '200':
          description: Duplicate (same idempotency_key)
        '201':
          description: Created
        '409':
          description: Form requires phone OTP
      operationId: postApiV1Leads
      x-operation-id-source: derived
  /api/v1/leads/outcome:
    post:
      summary: 'Report what a lead turned out to be worth (scope leads:write): won + value…'
      tags:
      - Leads
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                pipeline_id:
                  type: string
                  format: uuid
                lead_id:
                  type: string
                  format: uuid
                email:
                  type: string
                phone:
                  type: string
                outcome:
                  type: string
                  enum:
                  - won
                  - lost
                  - disqualified
                value_inr:
                  type: number
                value_paise:
                  type: integer
                reason:
                  type: string
                outcomes:
                  type: array
                  maxItems: 100
                  description: 'Batch form: an array of the objects above.'
              required: []
      responses:
        '200':
          description: All applied
        '207':
          description: Some items failed — see data.results
      operationId: postApiV1LeadsOutcome
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: nf_live_<32-char> | nf_test_<64-char>