Create a call blocking rule

post

https://api.emaktalk.com/api/v1/call_block

Adds an inbound blocking rule, then rebuilds and reloads your account's call blocking routing so it applies to the next call. New rules are created enabled with a match count of zero. The new rule's ID is not returned, so list the rules again to find it. If your key is limited to specific extensions and you send no extension_uuid, or one you do not hold, a separate rule is created for each extension you do hold.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

call_block_name

string | null

Display name for the rule. Whitespace is trimmed and an empty value is stored as no name.

call_block_number

string | null

The calling number to block. Trimmed, and an empty value is stored as no number.

call_block_description

string | null

Free-text note about the rule. Trimmed, and an empty value is stored as no note.

extension_uuid

string

Limit the rule to one extension. Send all or leave it empty to apply the rule across your whole account.

call_block_app_category

string | null

Category of the action applied to a blocked call.

call_block_app

string | null

The action taken on a blocked call. reject, busy and hold clear call_block_data.

call_block_data

string | null

Argument for the action, such as a destination. Ignored for reject, busy and hold.

call_block_country_code

number | null

Country code stored alongside the blocked number.

call_block_direction

string

Call direction the rule applies to. Defaults to inbound.

domain

string

Internal field. Omit it; rules are created on your own account.

Responses

401

Missing or invalid API key.

Language

Credentials

Bearer

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The rule was created. Its ID is not returned.

400The body was empty, or the rule could not be created.

403Your key is below the required role.