Callbacks from the SDK

v2.x

The SDK provides callbacks that will help you to handle events from it. There are 4 types of events:

1. The SDK is ready.
2. A request was blocked.
3. A challenge was solved by the user.
4. A challenge was cancelled by the user.

The SDK is ready

This event means that the SDK was finished the start process successfully. When calling the PerimeterX/start(appId:delegate:enableDoctorCheck:completion:) function, you should provide a completion handler. Once the handler is called with success == true you know that the SDK is ready. In addition, you can register to this event in other places within your code, using the PerimeterX/addInitializationFinishedCallback(forAppId:callback:) function. Here is an example:

1
PerimeterX.addInitializationFinishedCallback(forAppId: nil) {
2
	print("PerimeterX is ready")
3
}

You can call the PerimeterX/addInitializationFinishedCallback(forAppId:callback:) when the SDK is already ready. In this case, the callback will be called immediately.

A request was blocked

This event occurred when a request was blocked by PerimeterX. Notice that this event is only for native URL requests. URL requests which are origin from web views won’t trigger this event.

There are two ways to receive this event:

1. PerimeterX’s delegate - The delegate object that conform to the PerimeterXDelegate protocol should implement the PerimeterXDelegate/perimeterxDidRequestBlocked(forAppId:) function.
2. Register to the event - you can register to this event in other places within your code, using the PerimeterX/registerCallbackForRequestBlockedEvent(forAppId:callback:) function. This function returns a Registration ID which can be used to unregister from this event with the PerimeterX/unregisterCallbackForRequestBlockedEvent(forAppId:registrationId:). Here is an example:

1
let requestBlockedEventRegistrationId = PerimeterX.registerCallbackForRequestBlockedEvent {
2
	print("Request Blocked Event")
3
}

A challenge was solved by the user

This event occurred when a challenge was solved by the user. Notice that this event is only for native URL requests. URL requests which are origin from web views won’t trigger this event.

There are two ways to receive this event:

1. PerimeterX’s delegate - The delegate object that conform to the PerimeterXDelegate protocol should implement the PerimeterXDelegate/perimeterxDidChallengeSolved(forAppId:) function.
2. Register to the event - you can register to this event in other places within your code, using the PerimeterX/registerCallbackForChallengeSolvedEvent(forAppId:callback:) function. This function returns a Registration ID which can be used to unregister from this event with the PerimeterX/unregisterCallbackForChallengeSolvedEvent(forAppId:registrationId:). Here is an example:

1
let challengeSolvedEventRegistrationId = PerimeterX.registerCallbackForChallengeSolvedEvent {
2
	print("Challenge Solved Event")
3
}

A challenge was cancelled by the user

This event occurred when a challenge was cancelled by the user. Notice that this event is only for native URL requests. URL requests which are origin from web views won’t trigger this event.

There are two ways to receive this event:

1. PerimeterX’s delegate - The delegate object that conform to the PerimeterXDelegate protocol should implement the PerimeterXDelegate/perimeterxDidChallengeCancelled(forAppId:) function.
2. Register to the event - you can register to this event in other places within your code, using the PerimeterX/registerCallbackForChallengeCancelledEvent(forAppId:callback:) function. This function returns a Registration ID which can be used to unregister from this event with the PerimeterX/unregisterCallbackForChallengeCancelledEvent(forAppId:registrationId:). Here is an example:

1
let challengeCancelledEventRegistrationId = PerimeterX.registerCallbackForChallengeCancelledEvent {
2
	print("Challenge Cancelled Event")
3
}