Resend Notification
This article explains how to resend the notification for a new transaction through the REST API.
Make a POST request to the /credit/transactions/{ID_DA_TRANSACAO}/notify
endpoint.
With a valid access token, make a request to the (POST/credit/transactions/{TRANSACTION_ID}/notify) endpoint, sending the following parameters:
{
"phone": "CELL_PHONE_NOTIFICATION",
"email": "EMAIL_NOTIFICATION"
}
If everything is right in the request, the response is a JSON with the transaction ID and the link, as follows:
{
"id": "b50ee24c-71eb-4a5d-ade1-41c48b44c240",
"link:": "https://aces.so/example"
}
If an error occurs, the response is a JSON with the error and the error code:
{
"error": {
"code": "40004",
"description": "transaction id is invalid"
}
}
The following is a list of possible errors returned by the service:
HTTP Code | Code | Description | Reason |
---|---|---|---|
400 | 40001 | error decoding json | The data sent does not match the service contract |
400 | 40002 | error validating json | Some of the information is badly formatted or not filled in |
400 | 40004 | transaction id is invalid | The transaction id is invalid (format) |
400 | 40009 | transaction status is invalid | The transaction status does not allow sending the notification again (already completed) |
400 | 40021 | invalid phone | The phone is invalid. The default to be followed is 55 DDD NUMBER. Example: 5543999999999 |
400 | 40022 | invalid email | The e-mail is invalid |
403 | 40301 | not allowed | The user does not have permission to perform such an action. |
404 | 40401 | transaction not found | Transaction not found |
429 | 40001 | too many requests | Ratelimit reached |
500 | 50001 | internal error | Internal service failure |
Any concerns?
Missing something or still need help? If you are already a customer or partner, you can contact us through the Help Center.