## 3.3 Request

### 3.3.1 deleteRequest

A "deleteRequest" element, which consists of multiple, "delete" object ids. Since REST conventions do not support payloads on HTTP DELETE messages, all multi-object Delete Requests are conveyed via an HTTP PUT message containing an additional HTTP Header Field value of methodOverride set to DELETE.

SIF_Events are not reported for this object.

Figure 3.3.1-1: deleteRequest

| Element/@Attribute | Char | Privacy Rating | Description | Type
--- | --- | --- | --- | --- | ---
| deleteRequest |  |  | A "deleteRequest" element, which consists of multiple, "delete" object ids. Since REST conventions do not support payloads on HTTP DELETE messages, all multi-object Delete Requests are conveyed via an HTTP PUT message containing an additional HTTP Header Field value of methodOverride set to DELETE. |
| deletes | M |  |  | deleteIdCollectionType

Table 3.3.1-1: deleteRequest
JSON
[ { "deleteRequest": { "deletes": { "delete": [ { "id": "df789e1c-dfe7-4c18-8ef0-d907b81ea61e", "value": "" }, { "id": "abc89e1c-34e7-4cde-908a-d9abc81ea09a", "value": "" }, { "id": "ff789e1c-dfe7-4c18-8ef0-d907b81ea61e", "value": "" } ] } } } ]
XML
<deleteRequest> <deletes> <delete id="df789e1c-dfe7-4c18-8ef0-d907b81ea61e" /> <delete id="abc89e1c-34e7-4cde-908a-d9abc81ea09a" /> <delete id="ff789e1c-dfe7-4c18-8ef0-d907b81ea61e" /> </deletes> </deleteRequest>
Example 3.3.1-1: deleteRequest