Sign in

Update User

PUT https://{organization}.myguper.com/api/connect/user

Updates one user login of the organization. personId and login must both be sent and must belong to the same user: the login locates the record and the personId confirms it, so a wrong pair changes nothing and answers 404 or 409.

Only password, type and active can be changed. Fields you omit stay as they are.

Try-it values populated from environment ACME (Demo)


Authentication

Token

Most Connect endpoints require a valid x-guper-authorization token. Token issuance itself (/api/connect/auth) is the exception — it uses the x-guper-apikey and x-guper-apisecret credentials.

Headers

Name Type Description
x-guper-authorization * string User token issued by Guper.
Content-Type * string Always `application/json` for endpoints that accept a JSON body.

Request body

Content-Type: json

{
    "personId": "44",
    "login": "tintim",
    "password": "a10b20c30",
    "active": false
}

Responses

{
    "affectedRows": 1
}
Copied to clipboard