Deleting Records via OData

Intermediate

Use OData DELETE requests to remove records from FileMaker tables.

What you'll learn

The DELETE request pattern for OData records
Required privilege set permissions for deletion
What happens when you try to delete a non-existent record
Soft delete patterns as a safer alternative

Deleting records via OData uses the HTTP DELETE method against a specific record URL. This is a destructive operation -- unlike the FileMaker client, there is no undo. Understanding the correct URL pattern, required permissions, and error handling is important before using delete in any integration.

Stuck is a valid status

Need a second brain on this one?

If this lesson just collided with your real schema, script stack, or deadline, book consulting and turn the confusion into a concrete plan.

Book consulting

1/4

DELETE request pattern

Send an HTTP DELETE to the record URL with the record ID:

HTTP

DELETE /fmi/odata/v4/MyDB/Contacts(42)
Authorization: Basic {credentials}

// Response: 204 No Content (success)
// The record is permanently deleted

Creating and Updating Records via OData Reading the OData Metadata Document