Limits: read your daily withdrawal limit with an API key
- You can now select the
banking:limits:readscope when you create an API key in the dashboard. Get Daily Withdrawal Limit requires an admin user in each business. - The daily withdrawal limit covers every outbound transfer type combined.
- When
max_daily_withdrawal_limitisnull, no maximum is set for your entity. You can lower the limit, but a request to raise it is rejected. Contact support@meow.com to have a maximum set. Set Daily Withdrawal Limit.
Cards: choose who a card is issued to
- Create Card accepts an optional
cardholder_id, anidfrom List Users. With an entity API key, the card is issued to that member. Omit it to keep the current behavior, where the card goes to the entity’s longest-standing active admin. - A user API key can only name its own user. A user who is not an active member of the entity, or who has no access, returns
400. A frozen user returns403.
API keys: limit reads to the data your key allows
- Reading an approval initiated by another key or the web app now requires
accounts:transactionsas well asaccounts:read. An unrestricted key with onlyaccounts:readreceives403. Keys can still read their own approvals. Account-restricted keys continue to receive404for other actors’ approvals. - Account-restricted keys now receive
403when listing reimbursements or users, even withreimbursements:readorusers:read. These lists require an unrestricted key. Reimbursements, Users. - Account details now return
nullfor balance fields and investment holdings unless the key hasaccounts:balances. Meow skips the corresponding balance reads when the scope is absent. Reference.
Bill Pay: report on bills by department
- Bills in
GET /billsandGET /bills/{bill_id}now includedepartment_idanddepartment_name. Both arenullwhen a bill has no department. GET /billsaccepts a repeatabledepartment_idfilter. NewGET /billpay/departments(billpay:read) lists your company’s department IDs for the filter. Guide.- A key restricted to one account still gets only that account’s bills.
Reimbursements: follow a payout after it is sent
- Reimbursement
statusgains two additive values.PROCESSINGmeans the payment was sent and is on its way, but delivery is not yet confirmed.PAYMENT_FAILEDmeans the payment failed or was returned after it was sent. Meow reviews it before it can be paid again. Reference. PAIDnow means delivery was confirmed. Before, a reimbursement moved toPAIDwhen the payment was sent.
Invoicing: save an invoice as a draft for review
POST /billing/invoicesacceptssave_as_draft. A draft has no invoice number and sends nothing until a user on your team publishes it in the dashboard.- Without
save_as_draft, an invoice is published when you create it, as before. Guide.
Cards: read and write transaction memos
- List Card Transactions and Get Card Transaction now return
memo, your note about the purchase, ornullwhen there is none. - New
PUT /v1/cards/transactions/{transaction_id}/memosets or removes a memo with thecards:writescope. A retry with the same memo leaves the transaction unchanged. Guide.
API keys: account restrictions apply across the API
- A key restricted to one bank account now reads and acts only on that account across the API: accounts, transfers, cards, receipts, bills, invoices, tax forms, check deposits, wire drawdowns, and sandbox simulations. Another account’s resources return their existing not-found error, usually
404. ForPOST /billsandGET /billpay/expected-payment-date, a restricted key gets404for another account or an unknownaccount_id. An unrestricted key retains400for an unknownaccount_id. - An approval read returns only approvals the key initiated.
- These business-wide actions return
403for a restricted key: creating an account, changing the daily withdrawal limit, and managing webhook subscriptions. Use an unrestricted key for them. - Contacts, security policies, and accounting catalogs stay business-wide. A book transfer from the key’s account can still go to any account of the business.
- Keys that are not restricted are unchanged.
Bill Pay: a key restricted to one account stays on that account
- A key restricted to one bank account can now only create, read, and change bills and bill schedules funded from that account. Another account’s bills and schedules return
404. POST /billsandGET /billpay/expected-payment-datedefault to the key’s account when you omitaccount_id, instead of the business’s default Bill Pay account. Naming another account returns404. An unknownaccount_idreturns404for a restricted key and400for an unrestricted key.GET /billpay/settingsreports the key’s account asdefault_account_id.- Keys that are not restricted are unchanged.
Webhooks: get notified as bills move
- New
bill.createdandbill.updatedevents. A bill starts as a draft wherever it comes from: the API, the dashboard, an emailed invoice, or a recurring schedule.bill.createdfires when it is first submitted. bill.updatedfires on every status move after that: approved, rejected, scheduled, paid, failed, canceled, or moved back to draft. Edits such as a new memo or line item show up in the payload on the next status move. Dispatch ondata.status. Catalog.- Add the new event types to a subscription’s
event_types, or leaveevent_typesunset to receive every event.
Bill Pay: manage the complete bill draft workflow through the API and MCP
- Read Bill Pay settings, expected delivery dates, accounting vendors, expense accounts, and classes before you create a bill.
- Add, update, or remove one line item without replacing the complete list.
- Upload or remove the primary invoice separately from supporting documents.
- Set bill and line-item accounting mappings, then request an accounting sync for an eligible bill.
- List recurring bill schedules, read generated bills, and cancel future occurrences.
- MCP adds the same bill draft and schedule tools under the new
meow.billpayscope. Every created bill still requires human approval in the dashboard. Guide.
Payments: attach your own metadata for reconciliation
- ACH, wire, book, crypto, international, and scheduled ACH create requests accept a
metadataobject with up to 20 string pairs and a 5 KB total limit. - Meow returns the metadata unchanged in create responses, approval reads, payment reads, and snapshot webhook events. A scheduled ACH payment inherits the schedule’s metadata.
- Use metadata to carry identifiers from your system without parsing a payment description. Guide.
Information requests: explain a document you cannot provide, and read what is outstanding as data
POST /entities/{entity_id}/info-requests/{request_id}acceptsunavailable_proof_explanations, keyed byproof_type. An accepted explanation settles that document exactly as an upload does, so a request for a document the business cannot produce no longer stays open forever. Guide.answerson that endpoint is now optional, so a request that asks no questions can be settled with explanations alone.outstandingis also reported per request onnext_step.info_requests[]. Reference.- Outstanding documents now name the proof type in the same public vocabulary as
required_proof_types. Previously an item could read “Uk Shareholder Registry” beside arequired_proof_typesofshareholder_registry. GET /entities/{entity_id}/info-requests/{request_id}/schemanow returns adescriptionon eachfile_uploadelement, carrying the same explanation the Meow dashboard shows. Reference.
Crypto transfers: one bidirectional lifecycle webhook
- Wallet-funded and direct bank-funded outbound sends now emit lifecycle updates from Bridge provider state changes. Catalog.
GET /accounts/{account_id}/crypto/{transaction_id}now includesstatusfor incoming and outgoing transactions. Reference.GET /accounts/{account_id}/transactions?deposit_tx_hash=...now resolves deposits into bank accounts as well as global accounts.- Crypto transfer events include
account_id. Webhook subscriptions are entity-scoped, so every matching subscription for the entity receives the event. Useaccount_idto route it.
Bill Pay: pay a vendor in stablecoin
POST /billsandPATCH /bills/{bill_id}acceptpayment_type: "CRYPTO"with acrypto_contact_destination_id, one of the vendor’s saved crypto addresses from the contact’spayment_methods.crypto[].id. The bill stays a draft for dashboard approval, as every bill created through the API does. A crypto bill must be inUSD. Reference, Guide.GET /bills/{bill_id}returnsbill_payment_details.crypto_destination, the address a crypto bill will pay.- The same fields are available through the
create_billandupdate_billMCP tools.
Transfers: pay a contact in their own currency
POST /accounts/{account_id}/internationalsends a payment in the recipient’s local currency, converting from US dollars at the rate quoted when you call. Fix either leg: passrecipient_amountto send an exact amount in their currency, orsource_amountto spend an exact number of dollars. Reference, Guide.POST /accounts/{account_id}/international/quoteprices a payment without sending it, returning therate, thefeeand thetotal_debitso you can show them before committing. It reserves nothing, and the payment is priced again when you send, so figures can move with the rate. Reference.GET /contacts/international-requirementsreports the fields a destination needs, given a currency and bank country. Destinations differ: some route on an IBAN, others on a domestic routing code, and some want the recipient’s address. Checksupportedfirst, since not every currency reaches every country. Reference.POST /contactsacceptsinternationalalongsidecounterpartyandcrypto_address, carrying the bank details those requirements ask for. Provide exactly one of the three. Reference.- To send US dollars instead, including to a bank outside the US, keep using
POST /accounts/{account_id}/wire.
POST /accounts/{account_id}/liquidation-addressescreates a blockchain address that converts cryptocurrency sent to it into USD and deposits it into the account you name. Repeating the same account, network and currency returns the address that already exists rather than creating another. Reference.
Onboarding: see which agreements an application still owes
GET /entities/{entity_id}now returnsconsent, carryingstatus,consented_items,remaining_items,viewed_atandcompleted_at. Poll it to see whether the primary representative has finished the agreements behindconsent_url. Reference.next_step.stepreportsaccept_termsafter you submit while agreements are outstanding, and lists the outstanding ones innext_step.missing. It moves on tomonitor_reviewonce they are all accepted.- Previously a submitted application reported
monitor_reviewwith nothing missing even when every agreement was still unaccepted, so there was no way to tell from the API that it was waiting on the representative.
BlockchainNetworkacceptsXDC, andPaymentMethodTypeacceptsUSDC_XDC.
addresson a contact now returns the full address object rather than being omitted.
Transfers: read incoming crypto deposits, and tell the two directions apart
GET /accounts/{account_id}/crypto/{transaction_id}now returns incoming deposits as well as outgoing transfers. An inbound deposit carriessource_address, the on-chain address the funds came from, andsource_tx_hash, the deposit’s on-chain hash. Use them to match a deposit to whoever sent it. Reference.source_addressis null when the sender is not known to us, so treat a null as “unattributed” rather than assuming an address is always present.- Pass the transaction ID that List Transactions reports. The same ID comes back on the response, so you can fetch the transfer again with it. Reference.
- Every transfer response now carries
direction, eitherinboundoroutbound. ACH and wire have returned both directions for a while, and the field says which one you are looking at instead of leaving you to infer it. ACH, Wire.
POST /accounts/{account_id}/cryptoandPOST /accounts/{account_id}/usdcaccept theIdempotency-Keyheader, so a retried send cannot create a second transfer. Reference.
Accounts: correlate a new account with your own reference
POST /accountsaccepts an optionalreference_id, your own identifier of up to 255 characters. It comes back on the create response, onGET /accountsandGET /accounts/{account_id}asreferenceId, and in theaccount.created/account.updatedwebhooks. Reference.- This is how you match an account to the request that opened it. It matters most for products that open in the background: that response carries no
account_id, so the reference is the only thing tying the lateraccount.createdevent to your call. Catalog. - It is a label, not an idempotency key, so reuse it freely. Use the
Idempotency-Keyheader to make a retry safe.
Webhooks: account lifecycle events
account.createdfires when a Meow deposit account is live and addressable onGET /accounts. For Treasury Prime that is when the bank confirms the application, later than thePOST /accountsresponse, so you can subscribe instead of polling.account.updatedfires on status changes, including closes. Catalog.
Onboarding: hosted consent, additional products, and non-US businesses
- Submitting an application now returns a
consent_url, a hosted page where the primary representative reviews and accepts the required agreements, disclosures, and attestations in their browser, no login needed. The same link is returned onGET /entities/{entity_id}after submission. Guide. product_featuresonPOST /entities/{entity_id}/submitrequests additional products alongside the checking account.stablecoinsrequests USDC access, enabled once the representative accepts the terms and the application is approved.GET /entities/{entity_id}/representativeslists every representative with their KYC status. Reference.- Non-US businesses can now complete onboarding through the API. Guide.
entity_id for routing. Reference.Accounts: PATCH /accounts/{account_id} sets a custom account nickname (2-25 characters) shown in the dashboard. Reference.Webhooks: delivery sequence numbers and partner webhooks
- Out-of-order protection: every resource event now carries a per-resource
sequence. Keep the highest you’ve applied per resource and drop anything at or below it. Monotonic, not gapless. How it works. - Richer delivery history:
GET /webhooks/deliveriesrows now includeevent_type,resource_object,resource_id, andsequence, so you can find and redrive a failure without opening the event. - Partner Webhooks: subscribe to onboarding
application.*events with a partner API key. Same delivery machinery, scopespartner:webhooks:read/partner:webhooks:write. Reference. - Deleting a subscription retains its delivery history and frees the URL for reuse.
Webhooks: subscribe to events and inspect deliveries
POST /webhooks/subscriptionsto subscribe. Choosepayload_mode:snapshot(full resource) orthin({id, object}).- 13 events across ACH, wire, inbound transactions, check deposits, and global accounts. Dispatch on
data.status. - Signed with Standard Webhooks headers.
GET /webhooks/deliveriesand/attemptsfor history;POST /webhooks/deliveries/{id}/redriveto replay one.- New scopes:
webhooks:read,webhooks:write. - Guide · event catalog.
Cards:
PATCH /cards/{card_id} to freeze, unfreeze, or update spend limits on a cardTax Forms: GET /tax-forms and GET /tax-forms/{taxFormId} to retrieve IRS 1099 tax formsInstant payments: FedNow supported as a payment railPartner Onboarding API: Submit and track partner onboarding applications
POST /partner-onboarding/applications- Create an applicationGET /partner-onboarding/applications- List applicationsGET /partner-onboarding/applications/{application_id}- Get application detailsPOST /partner-onboarding/applications/{application_id}/upload-url- Get a presigned upload URLPOST /partner-onboarding/applications/{application_id}/confirm-document- Confirm a document upload
Approval Workflow: Programmatic transfers now flow through configurable approval policies
- Pending-approval state surfaced to API callers
- Mutating endpoints honor entity-level approval requirements
Payment Networks:
GET /accounts/{account_id}/payment-networks now returns deposit instruction fields for each supported methodAudit Logging: Structured audit logs added to all mutating Meow API endpointsWallet Transfers: The Meow API now supports transfers from Global Account wallets
crypto_idaccepted on wallet crypto transfers; currency is derived from the destination
Invoices: Added lifecycle tracking fields (e.g.,
paid_at, voided_at, sent_at) to Invoice responsesCrypto Transaction API: New endpoint for crypto transfers
GET /accounts/{account_id}/crypto/{transaction_id}- Get crypto transaction detailsPOST /accounts/{account_id}/crypto- Create crypto transactions- New API scope:
transfers:crypto:write
GET /accounts/{account_id}/check-deposits/{transaction_id}- Get check deposit details
Treasury Products: Commercial paper and liquid treasuries holdings exposed in the Meow API
Transfer Lookup: ACH and wire transfer GET endpoints now resolve Global Account-originated transfers
- Clarified that wire and ACH transfer GET endpoints return details for both incoming and outgoing transfers
- Updated Transfers tag description to include all transfer types
Billpay API: Bill management endpoints
GET /bills- List all bills with optional status filtering and paginationGET /bills/{bill_id}- Get bill details including line items- New API scope:
billpay:read
Scheduled ACH Transfers: Create and manage scheduled ACH transfers
POST /accounts/{account_id}/ach/scheduled- Create a scheduled ACH transferGET /accounts/{account_id}/ach/scheduled- List scheduled ACH transferstransferMethodquery parameter on transaction list endpoint to filter by transfer method (e.g., INCOMING_ACH, OUTGOING_WIRE, CARD)
Transfer details: Retrieve more information about ACH and wire transfers
GET /accounts/{account_id}/achs/{ach_transfer_id}- Get ACH transfer detailsinternal_notefield added to wire transfer response
Contacts API: Full CRUD operations for managing payment contacts
POST /contacts- Create a new contact with ACH/wire/check or crypto address detailsGET /contacts- List all contacts with optional nickname filteringGET /contacts/{contact_id}- Get contact detailsPATCH /contacts/{contact_id}- Update contact information and add payment detailsDELETE /contacts/{contact_id}- Delete a contact- New API scopes:
contacts:readandcontacts:write
- Products:
GET /billing/products,POST /billing/products,GET /billing/products/{product_id} - Customers:
GET /billing/customers,POST /billing/customers,GET /billing/customers/{customer_id} - Invoices:
GET /billing/invoices,POST /billing/invoices,GET /billing/invoices/{invoice_id},GET /billing/invoices/{invoice_id}/pdf - Line Items:
GET /billing/invoices/{invoice_id}/line-items,GET /billing/invoices/{invoice_id}/line-items/{line_item_id} - Payment Config:
GET /billing/payment-method-types,GET /billing/accounts - New API scopes:
billing:products:read/write,billing:customers:read/write,billing:invoices:read/write,billing:accounts:read - Recurring invoice support with RFC 2445 RRULE scheduling
- Invoice email notifications with custom recipient lists
POST /accounts/{account_id}/book- Create internal book transfers between accountsPOST /accounts/{account_id}/ach- Create ACH transfers to external counterpartiesPOST /accounts/{account_id}/wire- Create wire transfers to external counterpartiesGET /accounts/{account_id}/wires/{wire_transfer_id}- Get wire transfer details- New API scopes:
transfers:book:write,transfers:ach:write,transfers:wire:write
GET /accounts/{account_id}/payment-networks- List payment networks supported by an account
GET /routing-numbers/{routing_number}- Validate routing numbers and get bank information
GET /api-keys/accessible-entities- List all entities accessible by the current API keyGET /api-keys/current- Get metadata about the current API key
- Optional
x-entity-idheader to scope API requests to specific entities
Combined Read and Write APIs into a single unified Meow API.Accounts API: Comprehensive financial data access
GET /accounts- List bank accountsGET /accounts/{account_id}- Get account detailsGET /accounts/{account_id}/transactions- List transactions with time filtering and paginationGET /accounts/{account_id}/balances- List account balances with time filtering- New API scopes:
accounts:read,accounts:transactions,accounts:balances
POST /accounts/{account_id}/usdc- Create USDC transactionsGET /accounts/{account_id}/transactions/{transaction_id}- Get USDC transaction details- New API scope:
transfers:usdc:write - Support for multiple blockchain networks: Ethereum, Solana, Base
GET /health- API service health status endpoint
- API key authentication via
x-api-keyheader - Standardized error handling with detailed validation responses
- Scoped API permissions for granular access control