Delete an existing custom field. If a field is referenced in a flow and is deleted, an HTTP 202 will be returned but that flow will continue to operate as though the field still exists. The errors for each flow will be returned to the response body and the recorded on the flow’s error property. More changes to the flow must dereference the field.
Standard fields cannot be deleted.
LeadConduit uses HTTP Basic Authentication
with the username API and your API key as the password.
For example: API:1f1b96c9150d8050e858c043d543bb4eadae0e6f'
ID of the field to delete 24 character alpha-numeric BSON identifier
^[0-9a-fA-F]{24}$"5fd4371e940df5a34a3888b2"
OK
The required alphanumeric identifier of the field. Custom fields have an account-specific suffix (e.g. '_acme')
"first_name"
"last_name"
"email"
"phone_1"
The human-readable name of the field
"First Name"
"Last Name"
"Email"
"Phone 1"
The textual description of the purpose of this field
Read-only flag indicating whether this is a built-in LeadConduit field
The flag indicating that this field should no longer be used
The alternative field ID to be used instead of this deprecated field
^[0-9a-fA-F]{24}$"5fd4371e940df5a34a3888b2"
Read-only time the field was created
Read-only time the field was last updated