Those are the more common ways to pass an array via query string. The correct approach will depend on the framework used to implement the API. The second option works for me with Stripe’s API.
It could be that Bubble is de-duping the params before they’re sent - i.e. it might require each param to be unique. Did you actually try the second approach I suggested?
Well first off, the URL in your initial post suggests you’re not actually hitting the endpoint because it doesn’t have assets in it. The proper endpoint should look like…
https://api.opensea.io/api/v1/assets
…and then add the question mark and try the various query string configurations…
@sudsy - Totally yes. I just added the required part for simplicity in the question. I am using the whole URL when I am implementing it. Let me summarize so that you can replicate the issue.
What is want to query - https://api.opensea.io/api/v1/assets?owner=0x528e48bcb500518e78c1c8cccfc7275ed945cfb5&asset_contract_addresses=0xfa932d5cbbdc8f6ed6d96cc6513153afa9b7487c&asset_contract_addresses=0xc729ce9bf1030fbb639849a96fa8bbd013680b64
^ You can copy-paste this in your browser to see the response.
What I have tried in Bubble -
Adding two parameters with the same key and different values
All the suggestions that @sudsy gave in the thread above.
FWIW, you don’t need 0 and 1 there. You can use whatever key name you want - e.g. Addr 1 and Addr 2.
The square brackets in that context do not indicate array indexes. They’re just a Bubble construct for delimiting tokens that are replaced with the values of the corresponding keys below.
For future reference, always post a screenshot when you can. It often provides essential context that helps others help you.