HTTP DELETE Request with Body

[Axel]

Helle SeaTable team,

I recently stumbled upon this : https://apidog.com/articles/http-delete-request-body/

The HTTP specification explicitly states that the DELETE method does not expect a request body

Which brings me to this SeaTable API call https://api.seatable.io/reference/deleterow

I was just wondering what your thoughts are on this topic.

Best,
Axel.

[bennhatton]

Hi @Axel ,
The SeaTable team will probably answer you better than me, but here are just few considerations:

The apidog’s article mention that

The HTTP specification explicitly states that the DELETE method does not expect a request body

After looking at the HTML specifications, it is not so obvious to me : the specifications actually indicates that the resource to delete is identified by the Request-URI, but that’s all…

Moreover, I guess that the idea was to keep the same URL for every “rows” operations (see bellow)

List rows
https://cloud.seatable.io/api-gateway/api/v2/dtables/{baseUUID}/rows/?table_name={tableName}

Update rows
https://cloud.seatable.io/api-gateway/api/v2/dtables/{baseUUID}/rows/

Append rows
https://cloud.seatable.io/api-gateway/api/v2/dtables/{baseUUID}/rows/

Delete rows
https://cloud.seatable.io/api-gateway/api/v2/dtables/{baseUUID}/rows/

Of course, the delete URL could be the same than the Get row URL (see bellow) where the row id is actually passed through the URL, but as the delete API call can apparently delete one or more rows, I guess it’s not possible to pass several rows’ ids in the URL…

Get row (row id passed in the URL)
https://cloud.seatable.io/api-gateway/api/v2/dtables/{baseUUID}/rows/{rowID}/?table_name={tableName}

Once again, please keep in mind that it’s just my own interpretation…

Bests,
Benjamin

[Axel]

Hello @bennhatton and thank you for your interpretation. What you say makes sense. Thanks