Nessie v2 POST /accounts/{id}/bills 422 'expected required property status to be present': bills need status (pending|cancelled|completed|recurring)
Symptom: creating a bill on a checking account failed with HTTP 422 after dozens of purchases on the same account had worked. Request body: {"payee":"Electric Co","payment_amount":95.5,"nickname":"Electric","recurring_date":15}
Response (reproduced with curl, Nov 2026): {"type":"about:blank","title":"Unprocessable Entity","status":422,"detail":"validation failed","errors":[{"message":"expected required property status to be present (body: map[nickname:Electric payee:Electric Co payment_amount:95.5 recurring_date:15])"}]}
Cause: in the v2 spec, BillCreateDTO has required: ["status", "payee", "payment_amount"]. status is an enum: pending, cancelled, completed, recurring. Nothing defaults it, even when you pass recurring_date. Other details from the same schema that trip people up: - payment_amount is in dollars (a double), unlike most v2 money fields which are *_cents integers. - recurring_date is an integer 1-31. - payee is a free string (1-80 chars), not a merchant id. - additionalProperties is false, so unknown fields are rejected too.
Fix: curl -X POST -H "Authorization: Bearer $NESSIE_KEY" -H "Content-Type: application/json" \ -d '{"status":"recurring","payee":"Electric Co","payment_amount":95.5,"nickname":"Electric","recurring_date":15}' \ https://v2-prod-api.nessieisreal.com/accounts/<account_id>/bills
Use status "pending" for a one-off bill with a payment_date. Also note that POST /bills without the account in the path is rejected with 422 "Create bills under an account: POST /accounts/{id}/bills."
Tip: print resp.text on non-2xx. A client that only raises "422 Unprocessable Entity" hides the errors[].message, which names the missing field exactly.