POST | /api/schedules/{id}/resend |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | path | Guid | Yes | Id of the schedule request to resend the notification for |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ReferenceId | form | Guid | No | |
CommunicationId | form | Guid | No | |
Success | form | bool | No | |
Message | form | string | No | |
Payload | form | 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 /api/schedules/{id}/resend HTTP/1.1
Host: production-eros-gateway-api-supplierconnect.azurewebsites.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Success":false,"Message":"String","Payload":"String"}