CorebanqCorebanq Developer Docs
Rolesv1User Roles

Update user-role assignment

Handler: UpdateUserRole → UpdateUserRoleSrv. Updates user_id and/or role_id on the link.

PUT
/v1/user-roles/{id}

Authorization

bearerAuth
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

models.UpdateUserRoleInput

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PUT "https://example.com/v1/user-roles/497f6eca-6276-4993-bfeb-53cbbbba6f08" \  -H "Content-Type: application/json" \  -d '{}'
{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "user_id": "a169451c-8525-4352-b8ca-070dd449a1a5",
  "role_id": "ac4e70c8-d5be-48af-93eb-760f58fc91a9",
  "created_at": "2019-08-24T14:15:22Z",
  "created_by": "ee824cad-d7a6-4f48-87dc-e8461a9201c4",
  "modified_at": "2019-08-24T14:15:22Z",
  "modified_by": "e8d4374d-93a1-4e98-a6c6-fdcf00c5059f",
  "active": true,
  "metadata": {}
}
{
  "status": 400,
  "message": "Role name cannot be empty"
}
{
  "status": 401,
  "message": "Unauthorized"
}
{
  "status": 403,
  "message": "Forbidden"
}
{
  "status": 404,
  "message": "Role not found"
}
{
  "status": 500,
  "message": "server_error"
}

GETList roles for a user

Handler: GetRolesByUserID. Returns []models.RoleResponse (NOT a single UserRole) for the user identified by the {id} path parameter. The authenticated (token) user is used only to scope RBAC visibility (ReadAll vs. permitted role IDs), not to select which user's roles are returned.

PUTSet user role in customer context

Handler: SetUserRole → SetUserRoleSrv / executeSetUserRole. Upserts the user's single role for a customer (updates existing customer role link or creates one). Body uses customer_id + role_basename; path {id} is the target user_id.