Delete responses to a form. You must specify the included_response_ids
parameter.
Deletion does not happen straight away, instead, a 200 response status code indicates the request had been succesfully registered.
Not found response IDs will be ignored. Consider checking if responses have been actually deleted using the "Retrieve responses" endpoint or checking Typeform itself.
Comma-separated list of response_id values of the responses to delete. You can list up to 1000 tokens and choose to do so either in the request URL, or in its body.
Unique ID for the form. Find in your form URL. For example, in the URL "https://mysite.typeform.com/to/u6nXL7" the form_id is u6nXL7.
ids of responses to be deleted
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description of the error, expanding on the terse code.
An optional object containing more detailed info regarding which field the error occurred in.
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description about the field-level error.
Which field the error occurred. This could refer to a field in the request body, request header, or query parameter.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.
The type of field that caused the error.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description of the error, expanding on the terse code.
An optional object containing more detailed info regarding which field the error occurred in.
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description about the field-level error.
Which field the error occurred. This could refer to a field in the request body, request header, or query parameter.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.
The type of field that caused the error.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description of the error, expanding on the terse code.
An optional object containing more detailed info regarding which field the error occurred in.
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description about the field-level error.
Which field the error occurred. This could refer to a field in the request body, request header, or query parameter.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.
The type of field that caused the error.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description of the error, expanding on the terse code.
An optional object containing more detailed info regarding which field the error occurred in.
A developer-readable snake_case key, indicating some idea of what type of error occurred.
A developer-readable description about the field-level error.
Which field the error occurred. This could refer to a field in the request body, request header, or query parameter.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.
The type of field that caused the error.
A URL linking to help content, to aid the client developer in resolving the error. This value should be provided whenever available.