Callback Tester

Once you have configured your callbacks, you can start testing your endpoint using our Callback Tester. You can find it on Your App Name > Integration. When you are scrolling down, you will find a button that says "Open Callback tester":

Click on this button to open the Callback Tester modal:

Specifying the opening URL

The callback tester can be used for any integration type (iframe, SDK, API, and so on). However, it will still require an opening URL that is typically only used for iframe integrations. The opening URL is a link that will open the BitLabs offer wall. You can add additional custom query parameters to the URL that you would like to receive in the callbacks. One example of an opening URL would be:

https://web.bitlabs.ai?token=07ab2c56-af6a-4ee1-b96c-2c376b47bd51&UID=TestUser&mycustomparameter=123

In this example, we specify the token, UID (your user ID), and a custom query parameter, which you will receive in your callbacks. You can learn more about custom parameters here.

🚧

Please do not confuse the opening URL with the callback URL!

If you don't want to pass in custom parameters or a UID, then leave the URL as is.

Testing callbacks

We offer a variety of different callback test cases. Select a case you want to test, and then click on the button. BitLabs will then call your configured callback endpoint and show the response on the top of the modal. If the response shows an error, that means that your endpoint has an issue and it needs to be resolved from your end.

📘

The callback will include a debug=true parameter, so you can make sure that it won't impact your production environment.

When you make changes to your callback URLs, make sure to save the changes before testing callbacks again.

Frequently Asked Questions

Find a list of possible issues or questions that can come up.

I've added my callback URL to the callback tester. Why am I not receiving the correct callbacks?

You don’t need to add a callback URL to the callback tester. Instead, add the opening offer wall URL. The tester will automatically populate the correct callback URL by default. Unless you need to include a specific user ID or custom parameters, there's no need to modify it.

When you configure your callback URLs, make sure to save them before starting to test.

I'm receiving an error (40X, 404, or 50X). What is the cause of this?

The callback tester returns the HTTP status code it receives from your callback endpoint. If you see a 404 status, for example, it means your endpoint is returning a 404 error, which could indicate an incorrect setup on your end.

In general, any errors the tester shows come directly from your callback endpoint. Ensure your endpoint is a GET endpoint, not a POST one.