Retrieve metadata about API keys and their accessible entities
Meow API (1.0.0)
The Meow API provides comprehensive financial services and billing capabilities for businesses.
- Financial Data Access: Securely access account information, transactions, balances, and payment networks
- USDC Operations: Create and manage cryptocurrency contacts, initiate USDC transfers across multiple blockchain networks
The Billing API enables businesses to streamline their invoicing and payment collection:
- Product Management: Create and manage products with customizable pricing
- Customer Management: Maintain invoicing customers with billing addresses
- Invoice Creation: Generate invoices with line items, discounts, and custom notes
- Flexible Payment Options: Accept payments via bank transfer, ACH, cards, international wires, and USDC
- Collection Accounts: Configure accounts for automated payment collection
Authenticate using your API key in the request header: x-api-key: your-api-key
For multi-entity access, you can optionally include the x-entity-id header to scope API requests to a specific entity. Use the /api-keys/accessible-entities endpoint to list all entities accessible by your API key.
Errors return JSON with code, message, and debug_message. The code aligns with FDX where possible; debug_message is for troubleshooting only.
Common error codes:
500: Internal server error501: Subsystem unavailable503: Scheduled maintenance601: Data not found602: Customer not authorized701: Account not found703: Invalid input (including invalid date ranges)704: Account type not supported705: Account is closed801: Transaction not found
Email address to notify when the operation completes
Email address to notify when the operation completes
- Mock serverhttps://docs.meow.com/_mock/meow_api/accounts/{account_id}/wire
- Meow API Productionhttps://api.meow.com/v1/accounts/{account_id}/wire
- Meow API Sandboxhttps://api.sandbox.meow.com/v1/accounts/{account_id}/wire
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://docs.meow.com/_mock/meow_api/accounts/{account_id}/wire' \
-H 'Content-Type: application/json' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-entity-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-d '{
"email": "user@example.com",
"amount": 1,
"counterparty_id": "fd38dae9-b300-4017-a630-101c4279eafd",
"instructions": "string",
"purpose": "string",
"internal_note": "string",
"idempotency_key": "string"
}'{ "id": "string", "status": "pending", "amount": "string", "instructions": "string", "counterparty_id": "fd38dae9-b300-4017-a630-101c4279eafd", "created_time": 0, "transfer_type": "book" }
- Mock serverhttps://docs.meow.com/_mock/meow_api/accounts/{account_id}/transactions/{transaction_id}
- Meow API Productionhttps://api.meow.com/v1/accounts/{account_id}/transactions/{transaction_id}
- Meow API Sandboxhttps://api.sandbox.meow.com/v1/accounts/{account_id}/transactions/{transaction_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.meow.com/_mock/meow_api/accounts/{account_id}/transactions/{transaction_id}' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-entity-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'{ "id": "string", "amount": "string", "destination_address": "string", "destination_payment_rail": "arbitrum", "destination_tx_hash": "string", "destination_address_nickname": "string" }
- Mock serverhttps://docs.meow.com/_mock/meow_api/accounts/{account_id}/wires/{wire_transfer_id}
- Meow API Productionhttps://api.meow.com/v1/accounts/{account_id}/wires/{wire_transfer_id}
- Meow API Sandboxhttps://api.sandbox.meow.com/v1/accounts/{account_id}/wires/{wire_transfer_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.meow.com/_mock/meow_api/accounts/{account_id}/wires/{wire_transfer_id}' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-entity-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'Successful Response
The current status of the transfer
Instructions or OBI (Originator to Beneficiary Information)
Instructions or OBI (Originator to Beneficiary Information)
The unique identifier for the counterparty
The unique identifier for the counterparty
The account number of the counterparty
The routing number of the counterparty
The name of the counterparty's bank
ISO 8601 date-time in format 'YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm]' according to IETF RFC3339
ISO 8601 date-time in format 'YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm]' according to IETF RFC3339
Error message if the transfer failed
Error message if the transfer failed
IMAD (Input Message Accountability Data) for the wire
IMAD (Input Message Accountability Data) for the wire
The purpose of the wire transfer
The purpose of the wire transfer
{ "amount": "1000.00", "counterparty_account_number": "123456789", "counterparty_bank_name": "Chase Bank", "counterparty_id": "cp_789", "counterparty_name": "ABC Corp", "counterparty_routing_number": "021000021", "created_at": "2024-01-01T12:00:00Z", "id": "wire_123456", "imad": "2024010100000001", "instructions": "Wire transfer for invoice payment", "internal_note": "Payment for invoice 123", "purpose": "invoice_payment", "status": "sent", "updated_at": "2024-01-01T12:00:00Z" }