Price a quote: dry runs and live quotes

You can price a quote directly from a project or version page using the API connection: quoting panel. This is the same API your systems call, so it is a quick way to check a price or see exactly what a response looks like.

Open the quoting panel

The panel appears on every project page and every version page. On a project page it prices against the latest live version. On a version page it prices against that version, which lets you try a draft before it is approved.

The panel shows:

• project_reference and version_reference, the identifiers used in the API call;
• Inputs (JSON), an editable example input built from the model's fields;
• the equivalent curl command.

Choose a dry run or a live quote

• Quote Dry Run prices the quote without saving it. Use it as often as you like to check prices. The response has a quote_reference of null.
• Quote Live prices the quote and saves it to your quote history, where it appears on the Quotes page and in analytics.

The Auth switch is a setting for the whole project. When it is on, quoting the project requires API keys. Turning it off makes the project public, so anyone can quote it without keys, and Ptally asks you to confirm before it changes.

Edit the inputs

Change any value in Inputs (JSON) and run the quote again. For example, change "region" from "midlands" to "greater_london" to see the effect of the region factor. Every field the model expects is listed in its input step, which you can inspect from the steps list.

Read the response

The response appears under the panel, with the HTTP status and how long the quote took. It includes:

• quote_reference, project_reference, version_reference and version;
• input, the values that were priced;
• output, everything the model returns, such as the premium, tax and referral flag;
• result and valid.

To see how each step contributed to the price, see Quote debugging.

Copy the request

Copy curl copies the full request, including headers and inputs, so you can run it from a terminal or share it with a developer. Treat it like a password, because it contains your API keys. The API reference covers the same call in more detail.