Resend notification
Latest notification: October 31st, 2019
The following use case is assumed:
- Owner of the request: API
|
Description |
| SERVICE |
MESSAGE RESEND NOTIFIATION |
| URL |
/api/v3/messages/resend/notification/ |
| SECURITY |
YES |
| METHOD |
PUT |
| CONTENT/APPLICATION |
JSON
{
"messageCode" : "string",
"email" : "string",
"phone" : "string",
"userCode" : "string",
"deviceCode" : "string"
}
|
| PARAMS |
• messageCode: request code associated with the resubmission of the notification.
• email: the forwarding will be made via email to the account defined here.
• phone: the forwarding will be done via SMS to the number specified here. It is required to use the country code in +99 format, for example +34 for Spain.
• userCode: the forwarding will be done through PUSH notification to the user specified here.
• deviceCode: the forwarding will be done via PUSH notification to the device code indicated here. |
| RESPONSE |
200: HTTP status code 200/OK – Request received. |
Response content type: string
Corresponds to the code of the restarted request.
Alternative responses in case of error: HTTP status codes other than 200/OK will be returned. In this case a JSON describing the problem will always be returned:
{
"code": "string",
"type": "string",
"message": "string",
"trace” : "string"
}
