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
Start time for filtering transactions (ISO 8601 format). Also accepts 'start_time' for backwards compatibility.
Start time for filtering transactions (ISO 8601 format). Also accepts 'start_time' for backwards compatibility.
End time for filtering transactions (ISO 8601 format). Also accepts 'end_time' for backwards compatibility.
End time for filtering transactions (ISO 8601 format). Also accepts 'end_time' for backwards compatibility.
Opaque offset identifier for pagination. Use the nextOffset from a previous response.
Opaque offset identifier for pagination. Use the nextOffset from a previous response.
Maximum number of transactions to return
Maximum number of transactions to return
Filter to a specific transfer method.
Filter to a specific transfer method.
- Mock serverhttps://docs.meow.com/_mock/meow_api/accounts/{account_id}/transactions
- Meow API Productionhttps://api.meow.com/v1/accounts/{account_id}/transactions
- Meow API Sandboxhttps://api.sandbox.meow.com/v1/accounts/{account_id}/transactions
- 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?startTime=string&endTime=string&offset=string&limit=10&transferMethod=INCOMING_ACH' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-entity-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'Successful Response
An array of transactions with entity type dependent on the account type. Return an empty array if this information isn't available.
Detailed information about the deposit transaction
Long term persistent identity of the transaction (unique to account). Transactions with status PENDING and POSTED should have different IDs.
For reverse postings, the identity of the transaction being reversed. For the correction transaction, the identity of the reversing post. For credit card posting transactions, the identity of the authorization transaction
Value for a unique identifier
The date and time that the transaction was posted to the account. If not provided then TransactionTimestamp can be used as PostedTimeStamp. This property should not be provided for PENDING transactions and is required for POSTED transactions.
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
The description of the transaction
Debit or credit memo for the transaction
Transaction category, preferably MCC or SIC. Provide MCC if available.
Transaction category, preferably MCC or SIC. Provide MCC if available.
Transaction category detail
Transaction category detail
The status of the transaction
The amount of money in the account currency
The amount of money in the foreign currency. If this amount is specified, the foreignCurrency property should also be set.
The amount of money in the foreign currency. If this amount is specified, the foreignCurrency property should also be set.
The ISO 4217 code of the foreign currency
The ISO 4217 code of the foreign currency
The ID of the card used for this transaction, if it was a card transaction.
The ID of the card used for this transaction, if it was a card transaction.
The type of the deposit transaction
The type of the deposit transaction
Payee name
String of maximum length 255
{ "page": { "nextOffset": "qwer123454q2f" }, "transactions": [ { … } ] }