Update a question
PUT
https://www.rapidoform.com/be/api/question/:questionId
All requests require X-EMAIL and X-API-KEY. See authentication and errors. JSON request bodies also require Content-Type: application/json. All IDs in examples are synthetic; replace them with your own values.
Parameters
| Name | Type / location | Description |
|---|---|---|
| questionId | path string | Required question ObjectId. |
| surveyId | body string | Required parent form ID, even for a text-only update. |
| questionText | body string | Example of a field to change. Other question configuration fields may be updated. |
surveyId must match the question’s stored parent form. Foreign-workspace questions are denied. Send only editable fields: ownership fields, update operators and dotted keys are rejected. Logic rules are validated when rule is supplied.
Example request
curl --request PUT 'https://www.rapidoform.com/be/api/question/000000000000000000000001' \
--header "X-EMAIL: $RAPIDOFORM_EMAIL" \
--header "X-API-KEY: $RAPIDOFORM_API_KEY" \
--header 'Content-Type: application/json' \
--data '{"surveyId":"12345","questionText":"What could work better?"}'
JSON request body
{
"surveyId": "12345",
"questionText": "What could work better?"
}
Response
Examples show selected fields, not every stored property. Empty arrays are valid for list/report endpoints.
{
"Errors": [],
"Info": [],
"Data": [
{
"updateQuestions": {
"_id": "000000000000000000000001",
"surveyId": "12345",
"questionOrder": 1,
"questionText": "What could work better?",
"questionType": "Text Question"
}
}
],
"ErrorCode": "SUCCESS",
"fieldErrors": {
"List": []
}
}
HTTP 200 alone does not indicate success. Check ErrorCode and Errors; see troubleshooting.