Clear a custom field's value on a resource
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Body
Takes no parameters, and an empty body is expected. The value is addressed by the id the read publishes, not by the (resource_type, resource_id, definition_id) triple the PUT carries: a DELETE taking a body would have a target invisible in the request line and in every access log. 204 whether or not a row was removed, so a client retrying after a lost 204 does not read a SUCCESS as a failure; "this field is not set on this resource" is the state the caller asked for either way. A namespace ANOTHER application reserved is still 403 namespace_reserved rather than a silent 204: that is not a miss, it is a caller with no claim on a row that exists. Removing the DEFINITION is not on this API at all, because that would cascade every value of the field across the whole catalogue.
Response
Success. The response has no body.
