I'm pulling data using the API Query component (yes that old thing)!
The API in question returns the "next" page in a full uri link in the response, params and all.
When I setup the API profile I selected “full path pagination”.
When I sample the API Query component it is successful.
When I run the full API Query component (which causes pagination) it fails.
When I check the debug logs it shows that the paginated request (2nd request after initial request) is appending the Query Params to the end of the full path link.
Any suggestions?
I’m pretty sure I’ve used full path pagination before but I don’t remember it behaving like this before.
Thanks
To answer my own question (sort of)...
I had to use Advanced Mode in the API Query component to "unset" the query params on each subsequent API request (the pagination).
In order to do this, I needed to select "cursor based pagination" so that the baseline code had the conditional block that I needed. (I'm not an export on cdata but getting there thanks to Matillion!)
It ended up looking like this:
Whew!
I would still appreciate an expert response or someone else who has solved it without using Advanced Mode.
This is why we still need something with the flexibility of the API Query component - are you listening @MatillionProductTeam ? You can't do this in the newer API Extract component nor in the Data Productivity Cloud version. :(
