DELETE HTTP
Deprecated: The
DELETE HTTPsyntax is kept for backwards compatibility. Use the unifiedDELETEkeyword instead, which auto-detects HTTP URLs.
Redirect to DELETE
The DELETE keyword now automatically handles HTTP DELETE requests when given a URL:
' Preferred - unified DELETE
DELETE "https://api.example.com/resource/123"
' Also works (backwards compatibility)
DELETE HTTP "https://api.example.com/resource/123"
See Also
- DELETE — Unified delete keyword (recommended)
The unified DELETE keyword automatically detects:
- HTTP URLs → HTTP DELETE request
- Table + filter → Database delete
- File path → File delete
Quick Example
' Set authentication header
SET HEADER "Authorization", "Bearer " + api_token
' Delete resource via API
DELETE "https://api.example.com/users/456"
' Clear headers
CLEAR HEADERS
TALK "User deleted"
Migration
Replace this:
DELETE HTTP "https://api.example.com/resource/123"
With this:
DELETE "https://api.example.com/resource/123"
Both work, but the unified DELETE is cleaner and more intuitive.