API REFERENCEv1

Delete Scheduled Group SMS & MMS Campaigns

DELETEhttps://api2.protexting.com/v1/sms/delete-group-schedule-message

⌘

Pass your server-side token as access_token. Replace sample values with your own. Authentication & setup →

Response parameters:

message

String

Example Response Headers:

Response headers example

1Status Code: 200 OK
2Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
3Connection: Keep-Alive
4Content-Type: application/json; charset=utf-8
5Keep-Alive: timeout=5, max=100
6Link: <https://api2.protexting.com/v1/sms/delete-group-schedule-message?access_token=your_access_token>; 7rel=self Pragma: no-cache Transfer-Encoding: chunked  X-Powered-By: PHP/5.6.2 X-Rate-Limit-Limit: 60 X-Rate-Limit-Remaining: 59 X-Rate-Limit-Reset: 0

Example Response Body:

JSON response example

1[
2    {
3    	"message": "Group Scheduled Message successfully deleted!",4} ]

XML response example

1<response>2 3   <item>4       <message>Group Scheduled Message successfully deleted!</message> 5    </item>6</response>

HTTP Status Codes:

The standard HTTP Status Codes are used. More information is available here: http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

Error Codes:

Error Codes and Examples here »

Request example

1# Set PROTEXTING_ACCESS_TOKEN in your environment2curl --request DELETE \3  "https://api2.protexting.com/v1/sms/delete-group-schedule-message?access_token=${PROTEXTING_ACCESS_TOKEN:?Set your API token}" \4  --header 'Accept: application/json'

Server-side exampleJSON · HTTPS

← PreviousList Scheduled Group SMS & MMS Campaigns Next →Schedule Single SMS & MMS

Reference from the ProTexting documentation catalog. Code examples are illustrative; this page does not execute API requests.