Skip to content

feat: sync CLI with API changes - #26

Open
BernardoSM wants to merge 1 commit into
mainfrom
api-sync
Open

feat: sync CLI with API changes#26
BernardoSM wants to merge 1 commit into
mainfrom
api-sync

Conversation

@BernardoSM

Copy link
Copy Markdown
Collaborator

Automated, script-generated CLI update from API changes.
No LLM was involved in producing this diff — see scripts/api-sync/ in this repo.

Applied automatically

  • quotes.create: +refund_wallet_address

Needs a human — NOT applied, NOT auto-merged

  • New endpoint POST /v1/instances/{id}/ownership. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers/{customer_id}/bank-accounts. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/bank-accounts. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers/{customer_id}/bank-accounts/{bank_account_id}/offramp-wallets. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/bank-accounts/{bank_account_id}/offramp-wallets. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/bank-accounts/{bank_account_id}/offramp-wallets/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/bank-accounts/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint DELETE /v1/instances/{instance_id}/customers/{customer_id}/bank-accounts/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers/{customer_id}/blockchain-wallets. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/blockchain-wallets. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/blockchain-wallets/sign-message. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/blockchain-wallets/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint DELETE /v1/instances/{instance_id}/customers/{customer_id}/blockchain-wallets/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers/{customer_id}/limit-increase. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/limit-increase. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/rfi. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers/{customer_id}/rfi. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers/{customer_id}/virtual-accounts. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/virtual-accounts. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/virtual-accounts/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint PUT /v1/instances/{instance_id}/customers/{customer_id}/virtual-accounts/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/customers/{customer_id}/wallets. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/wallets. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/wallets/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint DELETE /v1/instances/{instance_id}/customers/{customer_id}/wallets/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{customer_id}/wallets/{id}/balance. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/customers/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint PUT /v1/instances/{instance_id}/customers/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint DELETE /v1/instances/{instance_id}/customers/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/limits/customers/{id}. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint GET /v1/instances/{instance_id}/rfi. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/instances/{instance_id}/rfi. Needs a human to decide whether it warrants a new CLI command.
  • New endpoint POST /v1/upload/analyze. Needs a human to decide whether it warrants a new CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/api-keys. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/api-keys. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/api-keys/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: DELETE /v1/instances/{instance_id}/api-keys/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/limits/receivers/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: PUT /v1/instances/{instance_id}/receivers/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: DELETE /v1/instances/{instance_id}/receivers/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers/{receiver_id}/bank-accounts. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/bank-accounts. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers/{receiver_id}/bank-accounts/{bank_account_id}/offramp-wallets. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/bank-accounts/{bank_account_id}/offramp-wallets. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/bank-accounts/{bank_account_id}/offramp-wallets/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/bank-accounts/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: DELETE /v1/instances/{instance_id}/receivers/{receiver_id}/bank-accounts/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers/{receiver_id}/blockchain-wallets. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/blockchain-wallets. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/blockchain-wallets/sign-message. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/blockchain-wallets/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: DELETE /v1/instances/{instance_id}/receivers/{receiver_id}/blockchain-wallets/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers/{receiver_id}/limit-increase. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/limit-increase. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/rfi. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers/{receiver_id}/rfi. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers/{receiver_id}/virtual-accounts. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/virtual-accounts. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/virtual-accounts/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: PUT /v1/instances/{instance_id}/receivers/{receiver_id}/virtual-accounts/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: POST /v1/instances/{instance_id}/receivers/{receiver_id}/wallets. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/wallets. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/wallets/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: DELETE /v1/instances/{instance_id}/receivers/{receiver_id}/wallets/{id}. Needs a human to decide whether to remove the corresponding CLI command.
  • Endpoint removed: GET /v1/instances/{instance_id}/receivers/{receiver_id}/wallets/{id}/balance. Needs a human to decide whether to remove the corresponding CLI command.
  • Field "customer_id" added to the request body of POST /v1/e/instances/{instance_id}/tos, a path this generator does not recognize. Needs a human to decide the CLI surface (new command, or extend known-resources.ts).
  • Field "receiver_id" removed from the request body of POST /v1/e/instances/{instance_id}/tos (request). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Response field added on GET /v1/e/payins/{id}: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of GET /v1/e/payins/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of GET /v1/e/payins/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Type changed for "created_at" on GET /v1/e/payins/{id} (response): unknown → string,null
  • Enum values changed for "manual_execution_status" on GET /v1/e/payins/{id} (response): +[failed] -[]. CLAUDE.md says update help text only, but there is no safe anchor to regenerate that text from.
  • Type changed for "updated_at" on GET /v1/e/payins/{id} (response): unknown → string,null
  • Response field added on GET /v1/e/payouts/{id}: "billing_fee_amount" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/e/payouts/{id}: "cpn_payment_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/e/payouts/{id}: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/e/payouts/{id}: "customer_local_amount" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/e/payouts/{id}: "sender_legal_name" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of GET /v1/e/payouts/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_local_amount" removed from the request body of GET /v1/e/payouts/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of GET /v1/e/payouts/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Type changed for "created_at" on GET /v1/e/payouts/{id} (response): unknown → string,null
  • Type changed for "updated_at" on GET /v1/e/payouts/{id} (response): unknown → string,null
  • Response field added on GET /v1/e/transfers/{id}: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/e/transfers/{id}: "customer_network" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/e/transfers/{id}: "customer_token" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/e/transfers/{id}: "customer_wallet_address" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of GET /v1/e/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_network" removed from the request body of GET /v1/e/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_token" removed from the request body of GET /v1/e/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_wallet_address" removed from the request body of GET /v1/e/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of GET /v1/e/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Type changed for "created_at" on GET /v1/e/transfers/{id} (response): unknown → string,null
  • Type changed for "updated_at" on GET /v1/e/transfers/{id} (response): unknown → string,null
  • Field "compliance_emails" added to the request body of PUT /v1/instances/{id}, a path this generator does not recognize. Needs a human to decide the CLI surface (new command, or extend known-resources.ts).
  • Field "customer_invite_redirect_url" added to the request body of PUT /v1/instances/{id}, a path this generator does not recognize. Needs a human to decide the CLI surface (new command, or extend known-resources.ts).
  • Field "customer_rfi_emails_enabled" added to the request body of PUT /v1/instances/{id}, a path this generator does not recognize. Needs a human to decide the CLI surface (new command, or extend known-resources.ts).
  • Field "receiver_invite_redirect_url" removed from the request body of PUT /v1/instances/{id} (request). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Type changed for "created_at" on GET /v1/instances/{instance_id}/billing/fees (response): unknown → string,null
  • Type changed for "updated_at" on GET /v1/instances/{instance_id}/billing/fees (response): unknown → string,null
  • Response field added on POST /v1/instances/{instance_id}/payins/evm: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of POST /v1/instances/{instance_id}/payins/evm (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of POST /v1/instances/{instance_id}/payins/evm (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Response field added on GET /v1/instances/{instance_id}/payins/{id}: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of GET /v1/instances/{instance_id}/payins/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of GET /v1/instances/{instance_id}/payins/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Type changed for "created_at" on GET /v1/instances/{instance_id}/payins/{id} (response): unknown → string,null
  • Enum values changed for "manual_execution_status" on GET /v1/instances/{instance_id}/payins/{id} (response): +[failed] -[]. CLAUDE.md says update help text only, but there is no safe anchor to regenerate that text from.
  • Type changed for "updated_at" on GET /v1/instances/{instance_id}/payins/{id} (response): unknown → string,null
  • Response field added on POST /v1/instances/{instance_id}/payouts/evm: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of POST /v1/instances/{instance_id}/payouts/evm (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of POST /v1/instances/{instance_id}/payouts/evm (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Response field added on POST /v1/instances/{instance_id}/payouts/solana: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of POST /v1/instances/{instance_id}/payouts/solana (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of POST /v1/instances/{instance_id}/payouts/solana (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Response field added on POST /v1/instances/{instance_id}/payouts/stellar: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of POST /v1/instances/{instance_id}/payouts/stellar (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of POST /v1/instances/{instance_id}/payouts/stellar (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Response field added on GET /v1/instances/{instance_id}/payouts/{id}: "billing_fee_amount" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/instances/{instance_id}/payouts/{id}: "cpn_payment_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/instances/{instance_id}/payouts/{id}: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/instances/{instance_id}/payouts/{id}: "customer_local_amount" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/instances/{instance_id}/payouts/{id}: "sender_legal_name" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of GET /v1/instances/{instance_id}/payouts/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_local_amount" removed from the request body of GET /v1/instances/{instance_id}/payouts/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of GET /v1/instances/{instance_id}/payouts/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Type changed for "created_at" on GET /v1/instances/{instance_id}/payouts/{id} (response): unknown → string,null
  • Type changed for "updated_at" on GET /v1/instances/{instance_id}/payouts/{id} (response): unknown → string,null
  • Response field added on POST /v1/instances/{instance_id}/quotes: "customer_local_amount" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_local_amount" removed from the request body of POST /v1/instances/{instance_id}/quotes (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "customer_network" added to the request body of POST /v1/instances/{instance_id}/transfer-quotes, a path this generator does not recognize. Needs a human to decide the CLI surface (new command, or extend known-resources.ts).
  • Field "customer_token" added to the request body of POST /v1/instances/{instance_id}/transfer-quotes, a path this generator does not recognize. Needs a human to decide the CLI surface (new command, or extend known-resources.ts).
  • Field "customer_wallet_address" added to the request body of POST /v1/instances/{instance_id}/transfer-quotes, a path this generator does not recognize. Needs a human to decide the CLI surface (new command, or extend known-resources.ts).
  • Field "receiver_network" removed from the request body of POST /v1/instances/{instance_id}/transfer-quotes (request). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_token" removed from the request body of POST /v1/instances/{instance_id}/transfer-quotes (request). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_wallet_address" removed from the request body of POST /v1/instances/{instance_id}/transfer-quotes (request). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of POST /v1/instances/{instance_id}/transfers (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Response field added on GET /v1/instances/{instance_id}/transfers/{id}: "customer_id" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/instances/{instance_id}/transfers/{id}: "customer_network" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/instances/{instance_id}/transfers/{id}: "customer_token" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Response field added on GET /v1/instances/{instance_id}/transfers/{id}: "customer_wallet_address" — whether to surface it as a CLI output column is a judgment call (CLAUDE.md), not scripted.
  • Field "receiver_id" removed from the request body of GET /v1/instances/{instance_id}/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_network" removed from the request body of GET /v1/instances/{instance_id}/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_token" removed from the request body of GET /v1/instances/{instance_id}/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "receiver_wallet_address" removed from the request body of GET /v1/instances/{instance_id}/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Field "tracking_partner_fee" removed from the request body of GET /v1/instances/{instance_id}/transfers/{id} (response). Removing a CLI flag is a breaking change for scripts using it and needs a human call.
  • Type changed for "created_at" on GET /v1/instances/{instance_id}/transfers/{id} (response): unknown → string,null
  • Type changed for "updated_at" on GET /v1/instances/{instance_id}/transfers/{id} (response): unknown → string,null
  • Enum values changed for "actor_type" across schemas: +[] -[api_key, user].
  • Enum values changed for "aiprise_document_type" across schemas: +[ADDRESS_PROOF_DOCUMENT, BANK_STATEMENT_DOCUMENT, OTHER, SOURCE_OF_FUNDS_DOCUMENT, TAX_CERTIFICATE, USER_SELFIE, VISA_DOCUMENT] -[].
  • Enum values changed for "approval_rate" across schemas: +[high, low, medium] -[].
  • Enum values changed for "banking_partner" across schemas: +[portage, ssb] -[].
  • Enum values changed for "billing_scheme" across schemas: +[] -[fixed, metered].
  • Enum values changed for "customer_network" across schemas: +[arbitrum, arbitrum_sepolia, base, base_sepolia, ethereum, polygon, polygon_amoy, sepolia, solana, solana_devnet, stellar, stellar_testnet, tron] -[].
  • Enum values changed for "customer_token" across schemas: +[USDB, USDC, USDT] -[].
  • Enum values changed for "customer_type" across schemas: +[business, individual] -[].
  • Enum values changed for "decision" across schemas: +[] -[approved, rejected].
  • Enum values changed for "events" across schemas: +[customer.delete, customer.new, customer.update] -[receiver.new, receiver.update].
  • Enum values changed for "kyc_status" across schemas: +[approved_rfi] -[].
  • Enum values changed for "manual_execution_status" across schemas: +[failed] -[].
  • Enum values changed for "notificationType" across schemas: +[] -[transactions.inbound, transactions.outbound].
  • Enum values changed for "onboarding_step" across schemas: +[] -[applicant, blocked, business_details, business_profile, completed, documents, initial].
  • Enum values changed for "operation" across schemas: +[] -[create, delete, update].
  • Enum values changed for "permission" across schemas: +[] -[full_access].
  • Enum values changed for "receiver_network" across schemas: +[] -[arbitrum, arbitrum_sepolia, base, base_sepolia, ethereum, polygon, polygon_amoy, sepolia, solana, solana_devnet, stellar, stellar_testnet, tron].
  • Enum values changed for "receiver_token" across schemas: +[] -[USDB, USDC, USDT].
  • Enum values changed for "receiver_type" across schemas: +[] -[business, individual].
  • Enum values changed for "status" across schemas: +[] -[active, claimable, collected, overdue, owing, paid, past_due, pending_payment].
  • Enum values changed for "subscription_plan" across schemas: +[] -[Basic, Business, Enterprise].
  • Enum values changed for "subscription_status" across schemas: +[] -[active, cancelled, past_due, pending_payment].
  • Enum values changed for "supporting_document_type" across schemas: +[business_accounts_receivable, business_contract, business_merchant_processor_statement, business_shareholder_loan, individual_blockchain_wallet_statement, individual_crypto_exchange_statement, individual_employment_letter, individual_investment_statement, individual_pay_stub] -[].
  • Enum values changed for "webhook_event" across schemas: +[customer.delete, customer.new, customer.update] -[receiver.new, receiver.update].
  • New schema "CreateCustomerIn" in the spec.
  • New schema "CustomerDeleteWebhookOut" in the spec.
  • New schema "CustomerLimitIncreaseIn" in the spec.
  • New schema "CustomerLimitIncreaseOut" in the spec.
  • New schema "CustomerNewWebhookOut" in the spec.
  • New schema "CustomerOut" in the spec.
  • New schema "CustomerUpdateWebhookOut" in the spec.
  • New schema "Error" in the spec.
  • New schema "GetCustomerLimitIncreaseOut" in the spec.
  • New schema "GetCustomerLimitsOut" in the spec.
  • New schema "InstanceRfi" in the spec.
  • New schema "MigrateInstanceOwnershipIn" in the spec.
  • New schema "UpdateCustomerIn" in the spec.
  • New schema "UploadAnalyzeIn" in the spec.
  • New schema "UploadAnalyzeOut" in the spec.
  • Schema removed: "AcceptTosIn".
  • Schema removed: "AcceptTosOut".
  • Schema removed: "AddonItemSchema".
  • Schema removed: "ApiKeyPublic".
  • Schema removed: "AuditActor".
  • Schema removed: "AuditLog".
  • Schema removed: "AuditLogOut".
  • Schema removed: "BillingDetails".
  • Schema removed: "BillingSubscription".
  • Schema removed: "CircleTransactionWebhookOut".
  • Schema removed: "CollectInvoiceBody".
  • Schema removed: "CollectInvoiceSchemaOut".
  • Schema removed: "CreateApiKeyIn".
  • Schema removed: "CreateApiKeyOut".
  • Schema removed: "CreateComplaintIn".
  • Schema removed: "CreateExternalReceiverTokenIn".
  • Schema removed: "CreateFeedbackIn".
  • Schema removed: "CreateInstanceOnboardingInviteIn".
  • Schema removed: "CreateInviteIn".
  • Schema removed: "CreatePortalSessionSchemaOut".
  • Schema removed: "CreateReceiverIn".
  • Schema removed: "CreateRecurringItemSchemaIn".
  • Schema removed: "CreateRfiBody".
  • Schema removed: "CreateTransferSchemaOut".
  • Schema removed: "CurrentUsageSchema".
  • Schema removed: "ExternalInstanceOut".
  • Schema removed: "ExternalOnboardingInfo".
  • Schema removed: "FeedbackActor".
  • Schema removed: "FeedbackOut".
  • Schema removed: "FeedbackWithActorOut".
  • Schema removed: "GetInvoicePdfSchemaOut".
  • Schema removed: "GetInvoiceSchemaOut".
  • Schema removed: "GetInvoicesSchemaOut".
  • Schema removed: "GetReceiverLimitIncreaseOut".
  • Schema removed: "GetReceiverLimitsOut".
  • Schema removed: "InstanceIn".
  • Schema removed: "InstanceOut".
  • Schema removed: "InvoiceItemSchema".
  • Schema removed: "KycDecisionBody".
  • Schema removed: "PayInvoiceSchemaOut".
  • Schema removed: "PaymentMethodSchemaOut".
  • Schema removed: "ReceiverLimitIncreaseIn".
  • Schema removed: "ReceiverLimitIncreaseOut".
  • Schema removed: "ReceiverNewWebhookOut".
  • Schema removed: "ReceiverOut".
  • Schema removed: "ReceiverUpdateWebhookOut".
  • Schema removed: "RecurringItem".
  • Schema removed: "UpdateDynamicRateOtcIn".
  • Schema removed: "UpdateReceiverIn".
  • Schema removed: "UpdateRecurringItemSchemaIn".
  • Schema removed: "VirtualAccountsUsage".

Version bump: minor

@BernardoSM BernardoSM added the api-sync Automated CLI sync with blindpay API label Aug 4, 2026
@BernardoSM

Copy link
Copy Markdown
Collaborator Author

Auto-merge NOT enabled: this changelog contains 243 change(s) the generator cannot express (see the needs-human section above). A human needs to review and merge this manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api-sync Automated CLI sync with blindpay API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant