Create Bill
Creates a bill as a draft for approval. The bill is not paid until someone approves it in the Meow dashboard; this never moves money on its own. Drafting is capped at 500 bills per rolling 24 hours per creator; creates past the cap return 429 Too Many Requests.
Request
- Base URLhttps://api.meow.com/v1
- AuthAPI key in header x-api-key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Headers
A unique key you generate (1-50 printable ASCII characters, no spaces) so retrying this request never creates a duplicate. Reusing a key is rejected.
Optional entity_id to scope requests to a specific entity.
Request body
Deprecated: send the key in the Idempotency-Key header instead. When both are sent they must match.
The vendor this bill is payable to. The vendor must already exist as a contact.
The vendor's invoice number. On a recurring bill, its first run of letters A-Z and digits 0-9, cut to 16 characters, becomes the prefix for generated bills, which are numbered <prefix>-01, <prefix>-02, and so on. A recurring bill's invoice number is rejected only when it has no letters A-Z or digits 0-9.
The date on the bill (YYYY-MM-DD), between 1900-01-01 and 2099-12-31.
The date the bill is due (YYYY-MM-DD), between 1900-01-01 and 2099-12-31.
A short description of the bill.
An internal memo (up to 140 characters).
How the bill will be paid once approved: ACH, WIRE, CHECK, or CRYPTO. Defaults to ACH.
Which of the vendor's saved crypto addresses to pay, taken from the contact's payment_methods.crypto[].id. Required when payment_type is CRYPTO, and rejected otherwise.
The account to pay from, in the same id format returned by GET /accounts. Defaults to your configured bill pay account when omitted. A key restricted to one account can only pay from that account, and defaults to it.
RFC 5545 RRULE string. Required: DTSTART, RRULE. Allowed frequencies: WEEKLY, MONTHLY.
Response
Successful Response
Identifier for this bill.
The name of the vendor.
The invoice number.
Description of the bill.
Memo for the bill.
ISO 8601 full-date in the format YYYY-MM-DD (per IETF RFC 3339).
ISO 8601 full-date in the format YYYY-MM-DD (per IETF RFC 3339).
The total amount of the bill.
The ID of the associated contact.
The spend category this bill is coded to, if any.
The name of the spend category, if any.
Who created the bill.
ISO 8601 date-time in the format YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm] (per IETF RFC 3339).
ISO 8601 date-time in the format YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm] (per IETF RFC 3339).
ISO 8601 date-time in the format YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm] (per IETF RFC 3339).
Who submitted the bill.
ISO 8601 date-time in the format YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm] (per IETF RFC 3339).
Who paid the bill.
ISO 8601 date-time in the format YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm] (per IETF RFC 3339).
ISO 8601 date-time in the format YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm] (per IETF RFC 3339).
ISO 8601 date-time in the format YYYY-MM-DDThh:mm:ss.nnn[Z|[+|-]hh:mm] (per IETF RFC 3339).
Who canceled the bill.
The recurring schedule this bill belongs to, if any.
The bill's position in its recurring schedule (template is 0).
A short-lived URL to download the bill's primary document.
RFC 5545 RRULE string. Required: DTSTART, RRULE. Allowed frequencies: WEEKLY, MONTHLY.
Whether the recurring schedule auto-approves generated bills.
Tracks the sync status of a bill with external accounting systems.
Tracks the sync status of a bill payment with external accounting systems.
The bill's ID in your accounting system, once it has synced there.
Whether this bill was excluded from accounting sync. An excluded bill reports no sync status, same as one that never synced.
Changes
No recorded changes to this operation across all 1 revision of this API.