Package com.flagright.api.resources.consumeruserevents

Class AsyncRawConsumerUserEventsClient

  • public class AsyncRawConsumerUserEventsClient
extends java.lang.Object

    • Constructor Detail

      • AsyncRawConsumerUserEventsClient

        public AsyncRawConsumerUserEventsClient​(ClientOptions clientOptions)

    • Method Detail

      • create

        public java.util.concurrent.CompletableFuture<FlagrightHttpResponse<UserWithRulesResult>> create​(ConsumerUserEventsCreateRequest request)

        POST Consumer User Events

        /events/consumer/user endpoint allows you to operate on the Consumer User Events entity.

        User events are created after the initial POST /consumer/users call (which creates a user) and are used to:

        • Update the STATE and KYC Status of the user, using the userStateDetails or kycStatusDetails field
        • Update the user details, using the updatedConsumerUserAttributes field.

        If you have neither of the above two use cases, you do not need to use user events.

        Payload

        Each user event needs three mandatory fields:

        • timestamp- the timestamp of when the event was created or occured in your system
        • userId - The ID of the transaction for which this event is generated.

        In order to make individual events retrievable, you also need to pass in a unique eventId to the request body.

      • create

        public java.util.concurrent.CompletableFuture<FlagrightHttpResponse<UserWithRulesResult>> create​(ConsumerUserEventsCreateRequest request,
                                                                                                 RequestOptions requestOptions)

        POST Consumer User Events

        /events/consumer/user endpoint allows you to operate on the Consumer User Events entity.

        User events are created after the initial POST /consumer/users call (which creates a user) and are used to:

        • Update the STATE and KYC Status of the user, using the userStateDetails or kycStatusDetails field
        • Update the user details, using the updatedConsumerUserAttributes field.

        If you have neither of the above two use cases, you do not need to use user events.

        Payload

        Each user event needs three mandatory fields:

        • timestamp- the timestamp of when the event was created or occured in your system
        • userId - The ID of the transaction for which this event is generated.

        In order to make individual events retrievable, you also need to pass in a unique eventId to the request body.