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
- Mock serverhttps://docs.meow.com/_mock/meow_api/billing/invoices/{invoice_id}
- Meow API Productionhttps://api.meow.com/v1/billing/invoices/{invoice_id}
- Meow API Sandboxhttps://api.sandbox.meow.com/v1/billing/invoices/{invoice_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.meow.com/_mock/meow_api/billing/invoices/{invoice_id}' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-entity-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'Successful Response
The name of the invoice
The name of the invoice
List of line item IDs associated with the invoice
The date the invoice is scheduled to be sent
The date the invoice payment is due
List of allowed payment methods for the invoice
Whether to send an email upon invoice creation
List of additional email addresses to receive the invoice
A note associated with the invoice
A note associated with the invoice
The account ID where funds will be collected
ISO 8601 date-time in format 'YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm]' according to IETF RFC3339
The timestamp when the invoice was last updated
ISO 8601 date-time in format 'YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm]' according to IETF RFC3339
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "customer_id": "160c0c4b-9966-4dc1-a916-8407eb10d74e", "line_item_ids": [ "497f6eca-6276-4993-bfeb-53cbbbba6f08" ], "invoice_date": "2019-08-24", "due_date": "2019-08-24", "payment_method_types": [ "BANK_TRANSFER" ], "send_email_on_creation": true, "additional_recipient_emails": [ "string" ], "note": "string", "collection_account_id": "d84ddb2f-39e1-4c6d-be0c-2221e75ce546", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" }
- Mock serverhttps://docs.meow.com/_mock/meow_api/billing/invoices/{invoice_id}/download
- Meow API Productionhttps://api.meow.com/v1/billing/invoices/{invoice_id}/download
- Meow API Sandboxhttps://api.sandbox.meow.com/v1/billing/invoices/{invoice_id}/download
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.meow.com/_mock/meow_api/billing/invoices/{invoice_id}/download' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-entity-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'Binary PDF content