All Verbs | /portal/schedule |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
AccountId | query | string | No | |
CustomerId | query | string | No | |
EndpointId | query | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
TimeZoneId | form | string | No | |
CustomerStates | form | List<string> | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /portal/schedule HTTP/1.1
Host: team.evovoice.io
Accept: application/json
Content-Type: application/json
Content-Length: length
{"accountId":"String","customerId":"String","endpointId":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"timeZoneId":"String","customerStates":["String"]}