Why am I getting 400 or 500 validation errors when creating or updating objects?

When you POST or PATCH objects through Rutter's write endpoints, a request can be rejected for how a field is formatted rather than what it contains. These are the most common write-path validation issues and how to fix them.

Send a value or omit the field — never send null

Rutter's responses may return a field as null, but in a request body a field must be either a valid value (such as a string) or left out entirely. Sending null explicitly will return a 400 error.

• Incorrect: { "payee": null }
• Correct: omit payee from the body, or send { "payee": "Acme Inc" }.

Match documented field formats and lengths

Fields validate against documented patterns and length limits. For example, a description field constrained to ^.{1,512}$ must be between 1 and 512 characters. Idempotency keys are currently limited to 100 characters — a longer key can surface as a 500 error rather than a clear validation message.

Understand idempotency-key behavior on retries

• Reusing the same idempotency key returns the original result instead of creating a duplicate — this is the intended way to safely retry a failed request.
• For bank feeds specifically, internal_bank_account_id must be unique per bank feed account. Reusing it for a different account returns a DUPLICATE_VALUE_CONFLICT error.

Tips

1. Check the exact field requirements in the API reference for the object you are writing.
2. Diff your request body against the schema to catch any field you are sending as null.
3. If an error message is unclear, share the request ID with Rutter Support. 📄 How do I contact Rutter Support and what are your SLAs?