POST | Disable API secret
- 1 minute to read
- Print
- DarkLight
- PDF
POST | Disable API secret
- 1 minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Disable an API secret in MySafe.
Requirements
- Permission to edit the API secret.
- An active API secret in MySafe.
Request
POST /api/mysafe/password/inactive/[identifier]
Request parameters
Send the parameter below in the path of the URL.
identifier - int - required - API secret unique identification code.Example request
POST {{url}}/api/mysafe/secretapi/inactive/5
Response
HTTP/1.1 200 OK
{
"code": 200,
"response": {
"status": 200,
"message": "Api secret successfully deactivated",
"error": false,
"error_code": 0,
"detail": "",
"mensagem": "Api secret successfully deactivated",
"erro": false,
"cod_erro": 0
}
}
Info
If the API secret is already inactive, the call will return a 200 response code with the message Api secret has already been deactivated.
Errors
400 - Bad Request.
Message: "1005: Api secret not found"
Possible cause: Api secret wasn't found
identifier and resend the request.Message: "1006: User does not have access"
Possible cause: user doesn't have access to the API secret.
500 - Internal Server Error.
Message: "Unexpected error."
Possible cause: the error is on the senhasegura server.
Solution: contact the support team for more information.
No route matched with those values.
Message: "No route matched with those values."
Possible causes: failure in your application authentication with the senhasegura server or incorrect URL.
Solution: check the authentication parameters such as Access Token URL, Client ID and Client Secret and request a new access token or check and correct the URL.
An invalid response was received from the upstream server .
Message: "An invalid response was received from the a seupstream server
Possible cause: the upstream server may be taking too long to respond, leading to a timeout error that is interpreted as an invalid response by the proxy/gateway server.
Solution: check the connectivity between the source of the request and the senhasegura server.
The upstream server is timing out.
Message: "The upstream server is timing out"
Possible cause: the request time has expired.
Solution: check the connectivity between the source of the request and the senhasegura server.
Was this article helpful?
