Create Open Finance Session
POST/v1/open-finance/sessions
Create a new Open Finance session.
Request
Header Parameters
- If there's no value: The default protection checks that the values in this request are equal: { method, params, path, query, body, userId }. This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and { method, params, path, query, body, userId } value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and { method, params, path, query, body, userId } value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and { method, params, path, query, body, userId } are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
The replay-protection-schema allows the user to choose between 3 options:
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
- application/json
Body
required
Client logged user document. In case of the user is a business entity, it is the document of the business entity representative.
Client logged user document when the user is a business entity.
Payment amount. In BRL cents.
device_risk_signal objectrequired
Client logged user device ID.
Client logged user OS version.
Client logged user elapsed time since boot in milliseconds.
Client logged user is rooted device.
Client logged user user time zone offset.
Client logged user language ISO 639-1 code.
Client logged user device screen width in pixels.
Client logged user device screen height in pixels.
Client logged user screen brightness in percentage. Examples: 0.5 for fractional format and 50 for percentage format.
Client logged user device latitude. The application must ask the user for permission to access their geolocation data.
Client logged user device longitude. The application must ask the user for permission to access their geolocation data.
Possible values: [COARSE, FINE, INFERRED]
Client logged user device geolocation type. The application must ask the user for permission to access their geolocation data.
Client logged user device is call in progress.
Client logged user device is dev mode enabled.
Client logged user device is mock GPS enabled.
Client logged user device is emulated.
Client logged user device is monkey runner enabled.
Client logged user device is charging.
Client logged user device antenna information.
Client logged user device is USB connected.
Client logged user device app integrity verdict.
Client logged user device integrity verdict.
Responses
- 201
- 400
- 401
- 422
The session created successfully.
- application/json
- Schema
- Example (from schema)
Schema
Session URL.
{
"url": "https://app.example.com/session?v=encrypted_data"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.