Common demo errors and the quickest fixes

Most prospects run into only three error categories the first day.
This is normal. The goal is to fix them in minutes, not hours.

1) "Required field missing"

What it means: Your payload is missing state, invoice_date, role, or another required value.

What to check now:

• Confirm the request is JSON (Content-Type: application/json).
• Confirm invoice_date is YYYY-MM-DD.
• Confirm state is a supported two-letter code (like CA).

2) "Unsupported state"

What it means: The state works in theory, but it is not exposed in this demo scope.

What to check now:

• Call /api/v1/supported-states.
• Compare the returned list with your request payload.
• Add a pre-check in your demo UI before calling /api/v1/calculate-deadline.

3) "Unexpected response shape"

What it means: The response is returning an error object or an error code path.

What to check now:

• Confirm all headers are set consistently.
• Re-run with a copy of the exact request body that failed.
• Compare values in your request against /api/test-api presets.

Fast fix checklist before you escalate

1. Copy your raw request JSON.
2. Copy the full error response body.
3. Run the same request in the guided sandbox with the same payload.
4. Note the state and invoice date used.

If this still fails, your next best move is to attach both request and response when contacting support.