Update DID Group
This request updates a DID group, targeted by secure ID.
patch | /phonenumber/did_groups/{did_group_sid} |
put | /phonenumber/did_groups/{did_group_sid} |
Sample
A sample PATCH request to update the DID Group object, targeted by secure ID, with the values in the request body:
curl -X PATCH \
'https://api.carrierx.com/core/v2/phonenumber/did_groups/41e21049-e5eb-433c-a93d-d57417b1863c' \
-H 'Content-Type: application/json' \
--data-binary '{"name":"my_did_group"}' \
-H 'Authorization: Bearer 5ebc03d6-8b2b-44ad-bf65-72d4f1491dda'
Response
200
status code with a serialized copy of the updated DID Group object:
{
"callback_url": null,
"did_group_sid": "41e21049-e5eb-433c-a93d-d57417b1863c",
"name": "my_did_group",
"partner_sid": "e00430c3-a7d0-4666-ab5c-f7202448382f"
}
A DID group object can be updated using either a PATCH
or PUT
request.
-
A
PATCH
request can be used to update one or more attribute values. When using aPATCH
request, only the attributes specified in the request payload will be updated, all other attributes and values will remain the same. The DID group secure ID is passed in the query URL, and the values to be modified are passed in the request body. -
A
PUT
request can be used to update an entire DID group object. The DID group secure ID is passed in the query URL, and the entire DID group object is passed in the request body.
Note, while all the fields must be present in a PUT
request, not all the attribute values may be modified after the initial creation, because when created, some of them become read-only.
Required Scopes
To update a DID group object, the partner must have one of the following scopes enabled:
phonenumber.manage
phonenumber.update
Path Arguments
Parameter | Data Type | Description |
---|---|---|
did_group_sid required | string | The DID group secure ID. |
Body Arguments
JSON representation of the fields and values to be updated.
Fields that can be modified are:
callback_url
name
Refer to this table to view all fields that appear in the DID group object.