Close

Close Send As API

The send_as API from Close — 3 operation(s) for send_as.

GitHub OpenAPI

Operations 6

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 /send_as/ List send-as permissions · List Send As Associations #
Ask an LLM
“Who is allowed to send emails as me?”
“Which teammates have let me send email on their behalf?”
Tell an agent
List everyone allowed to send as me.
Show the send-as associations where {allowed_user_id} is the allowed user.
POST /send_as/ Let another user send as you · Create a Send As Association #
Ask an LLM
“How do I let a teammate send emails as me?”
“Can I grant one user send-as permission on my account?”
Tell an agent
Allow my assistant to send emails as me.
Create a send-as permission for one teammate.
DELETE /send_as/ Revoke send-as for a specific user · Delete a Send As Association by allowed user #
Ask an LLM
“Can I revoke send-as permission by naming the user instead of the association?”
“How do I stop a particular teammate from sending as me?”
Tell an agent destructive · confirm first
Revoke send-as permission from user {allowed_user_id}.
Stop {allowed_user_id} from sending as {allowing_user_id}.
POST /send_as/bulk/ Allow and disallow many send-as users · Edit Send As Associations in bulk #
Ask an LLM
“Can I update who can send as me for many users in one request?”
“What's the fastest way to reset my send-as permissions?”
Tell an agent
Allow these three users and disallow those two from sending as me in bulk.
Bulk update my send-as list with the users I want allowed and disallowed.
GET /send_as/{id}/ Get a send-as association · Retrieve a single Send As Association #
Ask an LLM
“How do I look up one send-as association by ID?”
“What does a send-as association record contain?”
Tell an agent
Show send-as association {id}.
Fetch send-as record {id}.
DELETE /send_as/{id}/ Delete a send-as association by ID · Delete a Send As Association by ID #
Ask an LLM
“Can I delete a send-as permission using its association ID?”
“How do I remove a single send-as record?”
Tell an agent destructive · confirm first
Delete send-as association {id}.
Remove the send-as record {id}.

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/close/refs/heads/main/openapi/close-send-as-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/close:close-send-as-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.

GitHub Google LinkedIn

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

OpenAPI Specification

close-send-as-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  description: Close CRM REST API
  title: Close Send As API
  version: 1.0.0
servers:
- url: https://api.close.com/api/v1
security:
- ApiKeyAuth: []
- OAuth2: []
tags:
- name: send_as
  externalDocs:
    url: https://developer.close.com/api/resources/send-as
paths:
  /send_as/:
    get:
      operationId: send_as_list
      tags:
      - send_as
      summary: List Send As Associations
      description: A user only has access to associations they are involved in. This means that when using this endpoint, `allowing_user_id` or `allowed_user_id` must be equal to your user ID. If neither filter is provided, `allowing_user_id` is assumed by default.
      parameters:
      - in: query
        name: allowed_user_id
        required: false
        schema:
          title: Allowed User ID
          type: string
      - in: query
        name: allowing_user_id
        required: false
        schema:
          title: Allowing User ID
          type: string
      responses:
        '200':
          content:
            application/json:
              example:
                data:
                - allowed_user_id: user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA
                  allowing_user_id: user_Ova4RGFG7pztSeJiiMFdN7O2MFl71nD0uGO3bIOo4Wk
                  id: sdas_3KlXHOKx4afZ19TfpxMISa
                  organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
    post:
      operationId: send_as_create
      tags:
      - send_as
      summary: Create a Send As Association
      description: Create a send-as permission. The `allowing_user_id` must be equal to your own user ID.
      requestBody:
        content:
          application/json:
            example:
              allowed_user_id: user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA
              allowing_user_id: user_Ova4RGFG7pztSeJiiMFdN7O2MFl71nD0uGO3bIOo4Wk
        required: true
      responses:
        '201':
          content:
            application/json:
              example:
                allowed_user_id: user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA
                allowing_user_id: user_Ova4RGFG7pztSeJiiMFdN7O2MFl71nD0uGO3bIOo4Wk
                id: sdas_3KlXHOKx4afZ19TfpxMISa
                organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
    delete:
      operationId: send_as_delete_by_user
      tags:
      - send_as
      summary: Delete a Send As Association by allowed user
      description: 'The `allowing_user_id` must be equal to your user ID.


        Supply both the `allowing_user_id` and the `allowed_user_id` to delete an association by those users.'
      parameters:
      - in: query
        name: allowed_user_id
        required: false
        schema:
          title: Allowed User ID
          type: string
      - in: query
        name: allowing_user_id
        required: false
        schema:
          title: Allowing User ID
          type: string
      responses:
        '204':
          description: No content
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
  /send_as/bulk/:
    post:
      operationId: send_as_bulk_create
      tags:
      - send_as
      summary: Edit Send As Associations in bulk
      description: 'You can allow and disallow many other users to send as you in a single command by supplying the user IDs you want to allow and disallow.


        Once completed, this endpoint returns all existing associations where your user is the allowing user.'
      requestBody:
        content:
          application/json:
            example:
              allowed_user_ids:
              - user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA
              disallowed_user_ids:
              - user_SJMF1fEyZGdtl2RPzCm9zVQ7qhd33VajdGDREhbsxjF
        required: true
      responses:
        '200':
          content:
            application/json:
              example:
                data:
                - allowed_user_id: user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA
                  allowing_user_id: user_Ova4RGFG7pztSeJiiMFdN7O2MFl71nD0uGO3bIOo4Wk
                  id: sdas_3KlXHOKx4afZ19TfpxMISa
                  organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
  /send_as/{id}/:
    get:
      operationId: send_as_get
      tags:
      - send_as
      summary: Retrieve a single Send As Association
      parameters:
      - in: path
        name: id
        required: true
        schema:
          type: string
      responses:
        '200':
          content:
            application/json:
              example:
                allowed_user_id: user_N6KhMpzHRCYQHdn4gRNIFNN5JExnsrprKA6ekxM63XA
                allowing_user_id: user_Ova4RGFG7pztSeJiiMFdN7O2MFl71nD0uGO3bIOo4Wk
                id: sdas_3KlXHOKx4afZ19TfpxMISa
                organization_id: orga_RbREgmiiwcr1w2b4cOnCMQaQPSIFxMqAD2Dh243uxcH
          description: Successful response
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '404':
          description: Not found
    delete:
      operationId: send_as_delete
      tags:
      - send_as
      summary: Delete a Send As Association by ID
      parameters:
      - in: path
        name: id
        required: true
        schema:
          type: string
      responses:
        '204':
          description: No content
        '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
x-provenance:
  method: harvested
  publisher: Close
  source: https://developer.close.com/openapi.json
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)