Close Lead Statuses API

The lead_statuses API from Close — 2 operation(s) for lead_statuses.

Business capability
Opportunity & Pipeline Management BC-410.30

Operations 5

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /status/lead/ List lead statuses · List lead statuses for your organization #
Ask an LLM
“What lead statuses are set up in my organization?”
“Can I see all the stages a lead can be in?”
Tell an agent
List all lead statuses.
Show my organization's lead status options.
POST /status/lead/ Create a lead status · Create a new status that can be applied to leads #
Ask an LLM
“How do I add a new lead status like 'Nurturing'?”
“Can I create a custom status for leads?”
Tell an agent
Create a new lead status called Nurturing.
Add a lead status option for disqualified leads.
GET /status/lead/{id}/ Fetch a lead status · Fetch a single lead status #
Ask an LLM
“What's the label and color of a specific lead status?”
“Can I retrieve one lead status by id?”
Tell an agent
Fetch lead status {id}.
Show the details of lead status {id}.
PUT /status/lead/{id}/ Rename or recolor a lead status · Rename a lead status #
Ask an LLM
“Can I rename a lead status or change its color?”
“Does renaming a status change which leads have it?”
Tell an agent
Rename lead status {id}.
Change the color of lead status {id}.
DELETE /status/lead/{id}/ Delete a lead status · Delete a lead status #
Ask an LLM
“Can I delete a lead status that leads are still using?”
“Which call removes a lead status option?”
Tell an agent destructive · confirm first
Delete lead status {id}.
Remove the unused lead status {id}.

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/close:close-lead-statuses-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

close-lead-statuses-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  description: Close CRM REST API
  title: Close Lead Statuses API
  version: 1.0.0
servers:
- url: https://api.close.com/api/v1
security:
- ApiKeyAuth: []
- OAuth2: []
tags:
- name: Lead Statuses
  externalDocs:
    url: https://developer.close.com/api/resources/lead-statuses
paths:
  /status/lead/:
    get:
      operationId: lead_statuses_list
      tags:
      - Lead Statuses
      summary: List lead statuses for your organization
      responses:
        '200':
          content:
            application/json:
              example:
                data:
                - id: stat_1ZdiZqcSIkoGVnNOyxiEY58eTGQmFNG3LPlEVQ4V7Nk
                  label: Potential
                  organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
                - id: stat_2ZdiZqcSIkoGVnNOyxiEY58eTGQmFNG3LPlEVQ4V7Nk
                  label: Bad Fit
                  organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
                - id: stat_3ZdiZqcSIkoGVnNOyxiEY58eTGQmFNG3LPlEVQ4V7Nk
                  label: Qualified
                  organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
                - id: stat_8ZdiZqcSIkoGVnNOyxiEY58eTGQmFNG3LPlEVQ4V7Nk
                  label: Not Serious
                  organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
                has_more: false
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
    post:
      operationId: lead_statuses_create
      tags:
      - Lead Statuses
      summary: Create a new status that can be applied to leads
      requestBody:
        content:
          application/json:
            example:
              label: Potential
        required: true
      responses:
        '200':
          content:
            application/json:
              example:
                id: stat_9ZdiZqcSIkoGVnNOyxiEY58eTGQmFNG3LPlEVQ4V7Nk
                label: Potential
                organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
  /status/lead/{id}/:
    get:
      operationId: lead_statuses_get
      tags:
      - Lead Statuses
      summary: Fetch a single lead status
      parameters:
      - in: path
        name: id
        required: true
        schema:
          type: string
      responses:
        '200':
          content:
            application/json:
              example:
                id: stat_1ZdiZqcSIkoGVnNOyxiEY58eTGQmFNG3LPlEVQ4V7Nk
                label: Potential
                organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
    put:
      operationId: lead_statuses_update
      tags:
      - Lead Statuses
      summary: Rename a lead status
      description: Update a lead status. The `label` and `color` can be changed. To update the status of a particular lead, see PUT `/lead/{lead_id}/`.
      parameters:
      - in: path
        name: id
        required: true
        schema:
          type: string
      requestBody:
        content:
          application/json:
            example:
              label: Renamed
        required: true
      responses:
        '200':
          content:
            application/json:
              example:
                id: stat_9ZdiZqcSIkoGVnNOyxiEY58eTGQmFNG3LPlEVQ4V7Nk
                label: Renamed
                organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
    delete:
      operationId: lead_statuses_delete
      tags:
      - Lead Statuses
      summary: Delete a lead status
      description: You should make sure no leads are assigned this status, first.
      parameters:
      - in: path
        name: id
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
components:
  securitySchemes:
    ApiKeyAuth:
      description: Use your API key as the username and leave the password empty.
      scheme: basic
      type: http
    OAuth2:
      flows:
        authorizationCode:
          authorizationUrl: https://app.close.com/oauth2/authorize/
          scopes:
            all.full_access: Full access to all resources
            offline_access: Request a refresh token
          tokenUrl: https://api.close.com/oauth2/token/
      type: oauth2