blindpay-com · Schema

UpdateInstanceIn

FintechPaymentsStablecoinsGlobal

Properties

Name Type Description
name string
customer_invite_redirect_url stringnull
logo_url stringnull Logo shown to your customers on hosted pages such as the Terms of Service acceptance page
accent_color stringnull Accent color applied to hosted pages such as the Terms of Service accept button
email_notifications boolean Whether payment emails (payout and PIX payin created) are sent to customers. Customer RFI emails are controlled by customer_rfi_emails_enabled.
require_passkey boolean Whether passkey verification is required for protected actions
compliance_emails arraynull When non-empty, compliance Request for Information emails are sent only to these addresses instead of all instance members
partner_tos_link stringnull Passthrough Terms of Service: the page where your customers are presented with the BlindPay Terms of Service
partner_tos_screenshot stringnull Passthrough Terms of Service: a screenshot of how the BlindPay Terms of Service are displayed to your customers. Must be a file_url returned by POST /upload with bucket documents.
customer_rfi_emails_enabled boolean Whether customer (customer) Request for Information notification emails are sent for this instance. Omit to leave unchanged.
partner_tos_terms_accepted boolean Passthrough Terms of Service: accept the current Passthrough Terms of Service Partner Agreement (https://blindpay.com/passthrough-tos-partner-agreement). Dashboard users only; requires partner_tos_lin
View JSON Schema on GitHub

JSON Schema

blindpay-com-update-instance-in-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/blindpay-com/json-schema/blindpay-com-update-instance-in-schema.json",
  "title": "UpdateInstanceIn",
  "x-generated": "2026-11-10",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/blindpay-com-instances-api-openapi.yml#/components/schemas/UpdateInstanceIn",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 3,
      "maxLength": 100
    },
    "customer_invite_redirect_url": {
      "type": [
        "string",
        "null"
      ],
      "format": "uri"
    },
    "logo_url": {
      "type": [
        "string",
        "null"
      ],
      "format": "uri",
      "description": "Logo shown to your customers on hosted pages such as the Terms of Service acceptance page"
    },
    "accent_color": {
      "type": [
        "string",
        "null"
      ],
      "pattern": "^#[0-9a-f]{6}$",
      "description": "Accent color applied to hosted pages such as the Terms of Service accept button"
    },
    "email_notifications": {
      "type": "boolean",
      "default": true,
      "description": "Whether payment emails (payout and PIX payin created) are sent to customers. Customer RFI emails are controlled by customer_rfi_emails_enabled."
    },
    "require_passkey": {
      "type": "boolean",
      "default": false,
      "description": "Whether passkey verification is required for protected actions"
    },
    "compliance_emails": {
      "type": [
        "array",
        "null"
      ],
      "items": {
        "type": "string",
        "format": "email"
      },
      "maxItems": 20,
      "description": "When non-empty, compliance Request for Information emails are sent only to these addresses instead of all instance members"
    },
    "partner_tos_link": {
      "type": [
        "string",
        "null"
      ],
      "format": "uri",
      "description": "Passthrough Terms of Service: the page where your customers are presented with the BlindPay Terms of Service"
    },
    "partner_tos_screenshot": {
      "type": [
        "string",
        "null"
      ],
      "format": "uri",
      "description": "Passthrough Terms of Service: a screenshot of how the BlindPay Terms of Service are displayed to your customers. Must be a file_url returned by POST /upload with bucket documents."
    },
    "customer_rfi_emails_enabled": {
      "type": "boolean",
      "description": "Whether customer (customer) Request for Information notification emails are sent for this instance. Omit to leave unchanged."
    },
    "partner_tos_terms_accepted": {
      "type": "boolean",
      "enum": [
        true
      ],
      "description": "Passthrough Terms of Service: accept the current Passthrough Terms of Service Partner Agreement (https://blindpay.com/passthrough-tos-partner-agreement). Dashboard users only; requires partner_tos_link and partner_tos_screenshot."
    }
  },
  "required": [
    "name"
  ]
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • 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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/blindpay-com-update-instance-in"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.

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