Login
Environments
Section titled “Environments”| Environment | base_url | Description |
|---|---|---|
| Production | https://app.firmeasy.legal/api | Stable environment for end customers. |
| Test | https://staging.firmeasy.legal/api | Validation and testing environment before production. |
Authentication: Login
Section titled “Authentication: Login”The login endpoint allows you to obtain the access token needed to authenticate all subsequent calls to the Firmeasy API.
The user_integration_token is a unique identifier for each client integration (details about its provision and validity pending confirmation).
POST {{base_url}}/v1/auth/{{user_integration_token}}/loginHeaders
Section titled “Headers”To authorize access to the API, you must include the authentication token in the Authorization header using the Bearer scheme. Additionally, the Content-Type header must specify that the request body (if any) is sent in JSON format.
| Parameter | Type | Description | Limits |
|---|---|---|---|
Content-Type | string | Specifies the content type of the HTTP request body. For requests that include JSON data | 'application/json' |
Request body
Section titled “Request body”The request body contains the necessary parameters to perform the operation. Fields marked with * are required; the rest are optional depending on each integration’s needs.
| Parameter | Type | Description | Limits |
|---|---|---|---|
email* | string | Email address of the user who has access to the integration via API | Obligatorio |
password* | string | Password associated with the email | Obligatorio |
Request example
Section titled “Request example”{ "password": "contraseña_secreta"}Successful response
Section titled “Successful response”Upon successful authentication, a Bearer access token is returned which must be used in the Authorization header for all subsequent requests.
Response example
Section titled “Response example”{ "access": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwczovL2FwcCZWdhbC9hcGkvdjEvYXV0aC8xYzNmMTM4Yi0yMjAzLTQxOTMtOGQ1YyXQiOjE3NTA2ODgyODQsImV4cCI6MTcwibmJmIjoxNzUwNjg4Mjg0LCJqdGkiOiJoQ1lwic3ViIjoiMTAwIiwicHOWY2MDBhZGIzOWU3MDFjNDAwODcyZGI3YTU5NzZmNyJ9._W84a9SWmt9EiCOGh3S-oNY1QYI42rXVli1O-jUfDAg", "token_type": "bearer", "expires_in": 3600, "served_from_cache": false}Returned fields
Section titled “Returned fields”| Nombre | Type | Description |
|---|---|---|
access | string | Access Token that must be included in the Authorization header for future calls. |
token_type | string | Type of token returned (always `bearer`). |
expires_in | int | Token lifetime in seconds. |
served_from_cache | boolean | Indicates whether the response was served from cache. |
