Update Bill
Updates an editable bill. Only the fields you send are changed, and the bill stays a draft pending approval; this never moves money.
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.
Path parameters
The bill ID.
Headers
Optional entity_id to scope requests to a specific entity.
Request body
A short description of the bill. Send null to clear it.
An internal memo (up to 140 characters). Send null to clear it.
The vendor's invoice number. Send null to clear it. On a recurring bill's template (ordinal 0), its first run of letters A-Z and digits 0-9, cut to 16 characters, becomes the schedule's prefix and the template's stored number. The update is rejected when the number has no letters A-Z or digits 0-9. For a pending, active, or completed schedule, it is also rejected when it would clear the number or when another pending, active, or completed schedule uses that prefix.
The vendor this bill is payable to. The vendor must exist. A bill cannot be left without one, so send a different vendor rather than null.
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.
How the bill will be paid once approved.
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.
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.