Blend

Blend Closings & eSignature API

Closings, packages, eNotes, and RON sessions.

GitHub OpenAPI
Business capability
Credit Origination Management BC-1320.10

Operations 8

POST /closings Create a closing #
GET /closings List closings #
GET /closings/{closingId} Get a closing #
PATCH /closings/{closingId} Update a closing #
POST /closings/{closingId}/send Submit (send) a closing #
GET /applications/{id}/packages List eSignature packages #
POST /applications/{id}/packages Create an eSignature package #
POST /applications/{id}/packages/{packageId}/issue Issue a draft package for signature #

Documentation

📖
Documentation
https://developers.blend.com/blend/docs/create-a-new-home-loan
📖
APIReference
https://developers.blend.com/blend/reference
📖
Documentation
https://developers.blend.com/blend/docs/export-a-home-loan
📖
Documentation
https://developers.blend.com/blend/docs/los-guide-how-to-integrate-with-blend

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/blend-mortgage/refs/heads/main/openapi/blend-mortgage-closings-esignature-api-openapi.yml

Other Resources

🔗
PostmanCollection
https://raw.githubusercontent.com/api-evangelist/blend-mortgage/refs/heads/main/collections/blend-mortgage.postman_collection.json
🔗
OpenCollection
https://raw.githubusercontent.com/api-evangelist/blend-mortgage/refs/heads/main/collections/blend-mortgage.opencollection.json

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/blend-mortgage-closings-esignature-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

blend-mortgage-closings-esignature-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Blend Public Closings & eSignature API
  description: The Blend Public API is the documented REST surface of the Blend Labs digital lending and account-opening platform (developers.blend.com).
  version: 12.0.0
  contact:
    name: Blend Labs
    url: https://developers.blend.com/blend
  termsOfService: https://blend.com/legal/terms-of-service/
servers:
- url: https://api.blendlabs.com
  description: Production
- url: https://api.beta.blendlabs.com
  description: Beta / integration environment (used in Blend's documentation examples)
security:
- bearerAuth: []
tags:
- name: Closings & eSignature
  description: Closings, packages, eNotes, and RON sessions.
paths:
  /closings:
    post:
      operationId: createClosing
      tags:
      - Closings & eSignature
      summary: Create a closing
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '201':
          description: The created closing.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Closing'
    get:
      operationId: listClosings
      tags:
      - Closings & eSignature
      summary: List closings
      responses:
        '200':
          description: A list of closings.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Closing'
  /closings/{closingId}:
    parameters:
    - $ref: '#/components/parameters/ClosingId'
    get:
      operationId: getClosing
      tags:
      - Closings & eSignature
      summary: Get a closing
      responses:
        '200':
          description: The closing.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Closing'
    patch:
      operationId: updateClosing
      tags:
      - Closings & eSignature
      summary: Update a closing
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: The updated closing.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Closing'
  /closings/{closingId}/send:
    parameters:
    - $ref: '#/components/parameters/ClosingId'
    post:
      operationId: submitClosing
      tags:
      - Closings & eSignature
      summary: Submit (send) a closing
      responses:
        '202':
          description: Closing submitted for processing.
  /applications/{id}/packages:
    parameters:
    - $ref: '#/components/parameters/ApplicationId'
    get:
      operationId: listPackages
      tags:
      - Closings & eSignature
      summary: List eSignature packages
      responses:
        '200':
          description: The packages for the application.
    post:
      operationId: createPackage
      tags:
      - Closings & eSignature
      summary: Create an eSignature package
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
      responses:
        '201':
          description: The created package.
  /applications/{id}/packages/{packageId}/issue:
    parameters:
    - $ref: '#/components/parameters/ApplicationId'
    - name: packageId
      in: path
      required: true
      schema:
        type: string
    post:
      operationId: issuePackage
      tags:
      - Closings & eSignature
      summary: Issue a draft package for signature
      responses:
        '202':
          description: Package issued to recipients.
components:
  parameters:
    ClosingId:
      name: closingId
      in: path
      required: true
      schema:
        type: string
      description: The closing ID.
    ApplicationId:
      name: id
      in: path
      required: true
      schema:
        type: string
      description: The application ID.
  schemas:
    Closing:
      type: object
      properties:
        id:
          type: string
        applicationId:
          type: string
        status:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Blend authenticates requests with an authorization Bearer token. Each call must also send blend-api-version (to pin the API version) and blend-target-instance (tenant~instance) headers. API Secret Keys are exchanged for short-lived, request-scoped JWTs at Blend's API Gateway. Credentials are issued to Blend customers and certified partners - contact your Blend account team or partnerships to obtain them.