I am attempting to use n8n to query the Okta API and having trouble with pagination via the HTTP Request node.
Okta’s API returns the next page URL in the $response.headers.link as a string type with both the self and next links embedded
https://example.okta.com/api/v1/users?limit=200; rel=“self”, https://example.okta.com/api/v1/users?after=200uai9nhfsweDMx731t7&limit=200; rel=“next”
Welcome to the community
Best I can think of without playing with the API would be to use some regex to get the next url.
I ended up with this as a working model. I feel like it might be a little dirty as my regex-fu is novice.
That looks like what I would do, Maybe we should change it to automatically extract the next if it exists