Package com.flagright.api.resources.businessusers

Class AsyncBusinessUsersClient

java.lang.Object

com.flagright.api.resources.businessusers.AsyncBusinessUsersClient

public class AsyncBusinessUsersClient
extends java.lang.Object

Field Summary

Fields

Modifier and Type	Field	Description
protected ClientOptions	clientOptions

Constructor Summary

Constructors

Constructor	Description
AsyncBusinessUsersClient(ClientOptions clientOptions)

Method Summary

Modifier and Type	Method	Description
java.util.concurrent.CompletableFuture<BusinessUsersCreateResponse>	create(BusinessUsersCreateRequest request)	POST Business User
java.util.concurrent.CompletableFuture<BusinessUsersCreateResponse>	create(BusinessUsersCreateRequest request, RequestOptions requestOptions)	POST Business User
java.util.concurrent.CompletableFuture<BusinessWithRulesResult>	get(java.lang.String userId)	GET Business User
java.util.concurrent.CompletableFuture<BusinessWithRulesResult>	get(java.lang.String userId, RequestOptions requestOptions)	GET Business User
AsyncRawBusinessUsersClient	withRawResponse()	Get responses with HTTP metadata like headers

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

clientOptions

protected final ClientOptions clientOptions

Constructor Detail

AsyncBusinessUsersClient

public AsyncBusinessUsersClient(ClientOptions clientOptions)

Method Detail

withRawResponse

public AsyncRawBusinessUsersClient withRawResponse()

Get responses with HTTP metadata like headers

create

public java.util.concurrent.CompletableFuture<BusinessUsersCreateResponse> create(BusinessUsersCreateRequest request)

POST Business User

/business/user endpoint allows you to operate on the Business user entity.

In order to pass the payload of a User to Flagright and verify the User, you will need to call this endpoint with the User payload. Not all fields are mandatory, you will only need to pass in the fields that you have and are relevant for your compliance setup.

Payload

Each business user needs three mandatory fields:

• userId - Unique identifier for the user
• legalEntity - Details of the business legal entity (CompanyGeneralDetails, FinancialDetails etc) - only legalNamein CompanyGeneralDetails is mandatory
• createdTimestamp - UNIX timestamp in milliseconds for when the User is created in your system

create

public java.util.concurrent.CompletableFuture<BusinessUsersCreateResponse> create(BusinessUsersCreateRequest request,
                                                                                  RequestOptions requestOptions)

POST Business User

/business/user endpoint allows you to operate on the Business user entity.

In order to pass the payload of a User to Flagright and verify the User, you will need to call this endpoint with the User payload. Not all fields are mandatory, you will only need to pass in the fields that you have and are relevant for your compliance setup.

Payload

Each business user needs three mandatory fields:

• userId - Unique identifier for the user
• legalEntity - Details of the business legal entity (CompanyGeneralDetails, FinancialDetails etc) - only legalNamein CompanyGeneralDetails is mandatory
• createdTimestamp - UNIX timestamp in milliseconds for when the User is created in your system

get

public java.util.concurrent.CompletableFuture<BusinessWithRulesResult> get(java.lang.String userId)

GET Business User

/business/user endpoint allows you to operate on the Business User entity.

Calling GET /business/user/{userId} will return the entire User payload and rule execution results for the User with the corresponding userId

get

public java.util.concurrent.CompletableFuture<BusinessWithRulesResult> get(java.lang.String userId,
                                                                           RequestOptions requestOptions)

GET Business User

/business/user endpoint allows you to operate on the Business User entity.

Calling GET /business/user/{userId} will return the entire User payload and rule execution results for the User with the corresponding userId