[Feature Request] Include field uuid in the values array of submission/submitter API & webhook responses

[ali-fetty]

Problem

Each entry in the values array is identified only by the field name:

{ "field": "Full Name", "value": "John Doe" }

The field name isn't a reliable unique key: a submission can span multiple documents that reuse the same field names (Signature, Date, etc.), and names can also be blank, duplicated, or renamed. There's no way to map a value back to a specific field. (Related: #431 — a user makes separate /templates/:id calls just to get field uuids.)

Proposal

Add the field uuid to each values entry:

{ "field": "Full Name", "uuid": "a1b2c3d4-...", "value": "John Doe" }

Why not the fields array? It has the uuid, but values is the array most integrations consume (and the one in the API/webhook docs). Adding uuid inline avoids joining a second array on a non-unique name. The uuid is unique per field and stable across every submission of a template — a dependable key.

Notes

• Additive / non-breaking — new key alongside field and value.
• Implementation: one line in build_values_array (lib/submitters/serialize_for_webhook.rb), which feeds both the webhook and REST API:

  { 'field' => field_name, 'uuid' => field['uuid'], 'value' => value }

• Would also update openapi.yml (values.items, both definitions) to match — the current { field, value } shape was locked in via Incorrect typing on 'values' property of create submission response in openapi.yaml #399.

Happy to open a PR (serializer + spec + OpenAPI) if maintainers are open to it.

[omohokcoj]

@ali-fetty use ?include=fields param to add fields[] array with uuids and values to the response

[ali-fetty]

Great thank you!