Skip to content
Keja Cadence Keja Cadence Docs

HTTP status: checkout request invalid

This page documents the problem type URI returned when POST /api/v1/billing/checkout/preview/ or POST /api/v1/billing/checkout/ receives a body that does not match the documented checkout request contract (for example a missing start_datetime on a line item).

Canonical problem type

Section titled “Canonical problem type”
type: "https://docs.keja.co/troubleshooting/status-codes/billing.checkout_validation"

Individual field issues appear in errors[] with a pointer (JSON Pointer into the request body, such as /line_items/0/start_datetime) and a stable code of billing.checkout.field_invalid.

HTTP mapping

Section titled “HTTP mapping”
Item Value
Status code 400
Content-Type application/problem+json
title (problem) `Checkout request invalid`
detail (problem) Summary such as "One or more checkout fields were invalid."; use `errors[].detail` for field-specific copy.
Section titled “Related”
  • OpenAPI: CheckoutRequest, CheckoutLineItem, and CheckoutTender schemas describe the expected JSON body.
  • Domain rule failures raised after the request passes validation may use the same problem shape where noted in API release notes.