How to test in demo mode without credentials

If you are evaluating a new API, the first question is always: Can I try this before buying in?
Our demo path is built for that exact moment.

You can run realistic API requests on:

• /api/v1/calculate-deadline
• /api/v1/supported-states
• /api/v1/state-guides
• /api/v1/state-guides/{state_code}
• /api/v1/state-guides/{state_code}/calculator-payload

These are the only endpoints used in the public demo experience. Everything else in the API (admin, project, and internal operations routes) is intentionally hidden from this view.

Why this is a good prospect experience

• You can validate business outcomes first (notice timing, state support, deadline confidence).
• You can use the same request shape you would use later in production.
• You can compare results across multiple states before asking engineering for an integration sprint estimate.

What changes once you go live

• Add a permanent API key header in your production integration.
• Keep the same base URLs and response shapes where possible.
• Add retry and timeout rules in your backend client.
• Add operational monitoring around 4xx/5xx codes so missed calls do not block closeout workflows.

Production header example

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json

The goal is simple: use demo mode to prove outcome, then add credentials only at the implementation stage.