From dea4f3234e454ad8a6eb330af7868c7d123a19ca Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?= Date: Thu, 10 Sep 2026 16:42:32 -0300 Subject: [PATCH] docs: document one verb per status endpoint The reference noted that change_state also accepts GET and that list_states also accepts POST. Both routes do accept the second verb, but documenting it reads as an endorsement: a GET that mutates an answer's status is what we do not want integrations to build. Each endpoint now shows a single verb, the one its purpose calls for: POST for the status change, GET for the lookup. The routes are unchanged, so existing integrations keep working either way. Co-Authored-By: Claude Opus 5 --- source/index.html.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/source/index.html.md b/source/index.html.md index 93c6758487b..9a7d5ead3eb 100644 --- a/source/index.html.md +++ b/source/index.html.md @@ -682,7 +682,7 @@ Statuses are the values reported as `form_state` on an answer. This endpoint lis `GET https://www.mydatascope.com/api/external/list_states` -`POST` is also accepted. The endpoint takes no parameters either way. +The endpoint takes no parameters. ### Response Fields @@ -751,8 +751,6 @@ Changing the status through the API works like changing it from the web app: the `POST https://www.mydatascope.com/api/external/change_state` -`GET` is also accepted, with the same parameters. - ### Input Parameter Parameter | Type | Description --------- | ------- | -----------