UsersGet User by ID

Get User by ID

Returns details for a specific company user by their userId. Use this endpoint when you already know the user's identifier and want to look up or refresh a single user without paginating through the full list.

Rules:

  • The userId is the id field from GET /users/v1/users.
  • Returns 404 if the user does not belong to the authenticated company.
curl -X GET "https://api-sandbox.contasimples.com/users/v1/users/550e8400-e29b-41d4-a716-446655440000" \
  -H "Content-Type: application/json" \
  -H "Signature-Input: example_string" \
  -H "Signature: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "email": "joao.silva@empresa.com.br",
  "name": "João Silva",
  "phone": "11999999999",
  "role": {
    "id": "8a3f1b2c-4e5d-6f7a-8b9c-0d1e2f3a4b5c",
    "name": "Accountant"
  },
  "active": true
}
GET
/users/v1/users/{userId}
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN
path
userIdstring
Required

User ID (UUID v4) — use the id field value returned by GET /users/v1/users (e.g., 550e8400-e29b-41d4-a716-446655440000).

Format: uuid
header
Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

header
Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Path Parameters

userIdstring
Required

User ID (UUID v4) — use the id field value returned by GET /users/v1/users (e.g., 550e8400-e29b-41d4-a716-446655440000).

Example:
550e8400-e29b-41d4-a716-446655440000

Headers

Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Responses

idstring
Required

User ID.

emailstring
Required

User email.

namestring
Required

User’s name.

phonestring

User phone number.

roleobject
Required

Access profile assigned to the user in the company.

activeboolean
Required

Whether the user is active.