Update fields via public link

PUT

/v1/flows/{id}/cards/{cardId}/fields/public

Warning: using this endpoint on a card that has already advanced past its initial phase can wipe (zero out) every field of the card's current phase, without returning any HTTP error — the response comes back empty and the previously filled-in phase data is lost. This behavior was observed when attempting to use it to update entry-form (start-form) fields on an already-existing card: the entry-form fields are not updated (they keep their old value), and the current phase's fields are wiped.

This endpoint is intended exclusively for the initial public submission flow (the same unauthenticated link used to create the card for the first time). To update fields on a card that is already in progress, use the authenticated phase-fields update endpoint, or create a new card with the correct values.

Requisição

Parâmetros de Caminho

Parâmetros Bodyapplication/jsonNecessário

Examples

Respostas

🟢200Call response

application/json

The API returns 200 even when the effect is the unexpected behavior described above — the response observed in that scenario comes back with an empty field list.

Bodyapplication/json

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT '/v1/flows//cards//fields/public' \
--header 'Content-Type: application/json' \
--data '{
    "fields": [
        {
            "id": "string",
            "value": null
        }
    ]
}'

Response Example

{
    "fields": [
        null
    ]
}

Modificado em 2026-07-28 20:38:32

Página anterior

Update card assignee

Próxima página

Update card phase fields