Hoping someone might be able to direct me to some info on using the continuation uri and token when paginating results from the API. Wasn't able to see anything obvious in the documentation.
Cheers
This topic has been closed for comments
+9Hi @mcorb,
You can treat the continuation token just as any other key value pair, however it is only provided if the number of returned values exceeds your batch size. For example, if you look at this endpoint status request, you can set a batch size lower than the number of available results, which will provide you with a continuation token and URI at the end of the full response. The continuation URI contains both the request and token already combined, so the URI can be easily be passed to continue where the last batch left off.
Hope that helps. Please see the referenced documentation for additional details.
Best regards,
Joseph R.
Product Manager, Integrations
You can treat the continuation token just as any other key value pair, however it is only provided if the number of returned values exceeds your batch size. For example, if you look at this endpoint status request, you can set a batch size lower than the number of available results, which will provide you with a continuation token and URI at the end of the full response. The continuation URI contains both the request and token already combined, so the URI can be easily be passed to continue where the last batch left off.
Hope that helps. Please see the referenced documentation for additional details.
Best regards,
Joseph R.
Product Manager, Integrations
Product Manager, Integrations
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.