AuthMe
  1. User Identities
AuthMe
  • Getting Started
  • User Identities
    • Create Identity
      POST
    • Retrieve an Identity
      POST
    • Generate Param
      POST
    • User identification
      POST
    • Login user
      POST
    • Login legacy user
      POST
    • Authenticate user by param
      POST
    • User remember-me
      POST
    • User renovate-token
      POST
    • User associate-user-device
      POST
    • Generates token when user navigates between applications
      POST
    • Generates an Access token
      POST
    • Renew Token
      POST
    • Create password
      POST
    • Change Password
      POST
    • Reset password
      POST
    • Get Identities from user
      GET
    • Remove Identity
      DELETE
    • Updates specific identity attributes
      PATCH
    • Provision logon in mainframe
      POST
    • Lock an user credential
      POST
    • Unlock an user credential
      POST
    • Remove Identity
      DELETE
    • Add Identity
      PATCH
    • Leverage MFA
      POST
    • Fulfill MFA
      POST
    • Generate token to login with digital certificate
      POST
    • Authenticate with digital certificate
      POST
    • Generate a renew app token based on SAML integration informed data
      POST
    • Associate legacy logon by email
      POST
    • Associate legacy logon by mobile
      POST
    • Complete Associate legacy logon
      POST
    • Retrieve a legacy identity
      POST
    • Reset a legacy identity
      POST
    • Add alternative contacts to use on MFA process
      POST
    • Retrieve all user authentication factors
      GET
    • Update an alternative contact to use on MFA process
      PUT
    • Delete an alternative contact
      DELETE
    • Send a token to an authentication factor
      POST
    • Validate a Token previously sent to an authentication factor.
      POST
    • Grant Auth Smart Role
      POST
    • Login using federated accounts
      POST
    • Add alternative contacts to use on MFA process
      POST
    • Partial update to alternative contact to use on MFA process with adminstrative roles.
      PATCH
    • Delete an alternative contact with administrative roles
      DELETE
  • Client Identities
    • Create Identity
    • Remove Identity
    • Bulk Migrates Client Identities Organizational Structure
    • Login client
    • Login client
  • My Client Identities
    • Create Identity
    • Remove Client Identity
  • User Accesses
    • Groups - List Users
    • Groups - Add User
    • Groups - Remove User
    • Groups - List Business Users
    • Groups - Add Business User
    • Groups - Remove Business User
    • List User Roles
  • Business Accesses
    • Groups - List Business
    • Groups - Add Business
    • Groups - Remove Business
    • List Business Roles
  • Service Accesses
    • Groups - List Services
    • Groups - Add Service
    • Groups - Remove Service
    • List Service Roles
  • Product Accesses
    • Generate Opaque Token
    • Validate Opaque Token
  • Keys
    • Gets public key used to validate JWT
  • Corporate Groups
    • Creates a corporate group
    • Lists corporate groups
    • Gets corporate group by id
    • Updates a corporate group
    • Deletes a corporate group
  • Customer
    • Creates a Business Customer
    • Creates a User Customer
  • Identific
    • Create a new ApiKey for the Identific
    • List all ApiKey
    • Update an ApiKey
    • Delete an ApiKey
  • Groups
    • Creates a group
    • Lists groups
    • Gets group by id
    • Updates a group
    • Delete a group.
    • Creates a group role.
    • Deletes a group role.
    • Creates a group dependency.
    • Deletes a group dependency.
  • Generate Token
    • Generate a access token and a refresh token
  1. User Identities

Renew Token

Prod Env
https://api.serasaexperian.com.br
Prod Env
https://api.serasaexperian.com.br
POST
https://api.serasaexperian.com.br
/security/iam/v1/user-identities/renew-token

Responsibilities#

This endpoint must be used to update a token with any changes in the roles.

Usage#

Attention to change business roles when businessId changed.
If one is using this method after login through Identity Provider (Okta), it's only required the user id and the client id.

Requirements#

To access this endpoint, the client (application) must have one of the following sets of roles:
CLI-AUTH-IDENTIFIED and CLI-1STPARTY
CLI-AUTH-IDENTIFIED and CLI-1STPARTY and AUTH-BASIC and USER
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://api.serasaexperian.com.br/security/iam/v1/user-identities/renew-token?token&remember-me'
Response Response Example
200 - Example 1
{
    "accessToken": "eyJhbGciOiJSUzUxMiJ9.eyJqdGkiOiI1Y2ZlMzUxQ...",
    "tokenType": "Bearer",
    "refreshToken": "78e58fba-7282-4f99-a2da-d37eefc1ab12",
    "expiresIn": "1612483680",
    "scope": [
        "READ, WRITE"
    ]
}

Request

Query Params

Responses

🟢200OK
application/json
Token Updated Succesfully
Body

🟠400Bad Request
🟠401Unauthorized
🟠403Forbidden
🟠412412
🔴500Server Error
🔴500Server Error
Modified at 2025-04-11 12:00:41
Previous
Generates an Access token
Next
Create password
Built with