/users/update
These are the possible response codes when you make an API call to the /users/update
endpoint.
Response Code | Error | Message | Scenario | Resolution |
---|---|---|---|---|
200 OK | Successfully update user details (Make sure to add profile fields the same with the client settings) | |||
200 OK | Invalid | Successful call. Not a required field. | ||
200 OK | Missing | Successful call. Not a required field. | ||
200 OK | Removed | Successful call. Not a required field. | ||
200 OK | Invalid | Successful call. Not a required field. | ||
200 OK | Missing | Successful call. Not a required field. | ||
200 OK | Removed | Successful call. Not a required field. | ||
200 OK | Invalid | Successful call. Not a required field. | ||
200 OK | Missing | Successful call. Not a required field. | ||
200 OK | Remove | Successful call. Not a required field. | ||
400 Bad Request |
| "Invalid json format" | Empty payload | Add the payload. |
400 Bad Request |
| "Invalid json format" | Invalid JSON format used in the payload. | Use correct JSON format for the payload. |
403 Forbidden | "http_exception" | "Forbidden" | Used invalid | Ensure the |
422 Unprocessable Entity |
| "client_id": { | Missing | Include the correct |
422 Unprocessable Entity |
| "client_id": "field required" | Removed | Include the |
422 Unprocessable Entity |
| "error_details": null | Invalid | The |
422 Unprocessable Entity | "missing_argument" | "error_details": "provide either | Missing | The |
422 Unprocessable Entity | "missing_argument" | "error_details": "provide either | Removed | The |
422 Unprocessable Entity |
| "error_details": null | Incorrect | Ensure that the |
422 Unprocessable Entity |
| "error_details": "value is a string but attribute_name not given" | Missing value for | Include the |
422 Unprocessable Entity |
| "error_details": "value is a string but attribute_name not given" | Removed | Include the |