Custom loader generates a snippet without apiKey parameter

Custom Loader
1

Hi, recently I created 3 containers for a client, and noticed that a custom loader generates a snippet for one container withour the &apiKey= parameter in the end. Instead, it generates a snippet with &page=3 parameter. Is this okay? Why is that?

page=3 parameter

image
image1279×521 34 KB

apiKey parameter:

image
image1273×524 34.1 KB

2

Hey @Gasper_Cerar w/o saying too much - that is intended. You may find other parameters surface there if you try enough variations. All of them will work and this is a designed part of the loader

3

Hi, Dan,

Great. I thought so, but was just making some double checking :slight_smile: Thanks for the information.