Sign in

Create User

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

Wires Connect login credentials (login + password) to an existing person registered in Register.

This is the second step of the user-onboarding flow. The first step is to issue an invite token for that person at Create invite — the token is delivered to the new user (e-mail link, magic link, etc.) and must be posted back here together with the credentials.

Connect decrypts the invite token with its private key, verifies the organization and personId it carries, and only then writes the User record. The personId of the returned User equals the idPerson used in the invite — that's the binding between the two services.

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: application/json

{
    "inviteToken": "<inviteToken>",
    "login": "maria.silva",
    "password": "S3cretPass!",
    "type": "user"                                              // optional
}

Responses

{
    "organization": "acme",
    "login":        "maria.silva",
    "type":         "user",
    "personId":     44,
    "pass":         "**************",
    "dateTime":     "2026-05-01T12:34:56-03:00"
}

Related

Copied to clipboard