Actions221
- ACL Group Actions
- Alarm Clock Actions
- Application Actions
- Broadcast Actions
- Call Actions
- Call History Actions
- Call Queue Actions
- Colleague Actions
- Contact Actions
- Department Actions
- Device Actions
- Dialplan Actions
- Add DB Value
- Create Dialplan
- Create IVR
- Create Paging Group
- Create Switch
- Create Time Table
- Delete DB Family
- Delete DB Key
- Delete Dialplan
- Delete IVR
- Delete Paging Group
- Delete Switch
- Delete Time Table
- Get DB Family Keys
- Get DB Value
- Get Dialplan
- Get Dialplans
- Get General Settings
- Get IVR
- Get Paging Groups
- Get Switches
- Get Time Tables
- Import Time Tables
- Update DB Value
- Update Dialplan
- Update General Settings
- Update IVR
- Update Paging Group
- Update Switch
- Update Time Table
- Fax Actions
- Group Actions
- Notification Actions
- OAuth2 Client Actions
- PBX Actions
- PBX Setting Actions
- PBX System Actions
- PBX Upgrade Actions
- Personal Actions
- Phonebook Actions
- Recording Actions
- SIP Registration Actions
- SMS Actions
- Sound Actions
- Trunk Actions
- Create FXO Trunk
- Create PSTN Trunk
- Create SIP Trunk
- Create Trunk Group
- Create Trunk Price List
- Delete FXO Trunk
- Delete PSTN Trunk
- Delete SIP Trunk
- Delete Trunk Group
- Delete Trunk Price List
- Export Trunk Price List
- Get FXO Trunks
- Get PSTN Trunks
- Get SIP Trunks
- Get Trunk Groups
- Get Trunk Prices
- Update FXO Trunk
- Update PSTN Trunk
- Update SIP Trunk
- Update Trunk Group
- Update Trunk Price List
- Trusted IP Actions
- Video Conference Actions
- Voicemail Actions
Dialplan → Delete DB Key
AI-generatedSummary
Delete a key from a Dialplan database family in Wildix. Provide the family name and key, then choose Bearer Token or OAuth2 authentication.
Inputs
- Authentication — Select Bearer Token or OAuth2 authentication.
- Family (required) — Name of the dialplan database family containing the key.
- Key (required) — Key within the specified family to delete.
Output shape
Not determinable from the provided source pack.
The source pack includes only signature-level placeholders for the operation implementation, so its request details and returned data shape cannot be confirmed.