SOLVED

REST API endpoint optimization

Go to solution
Will_Beeler
Level 1

REST API endpoint optimization

We could use assistance on optimizing our calls to the Get Lists API endpoint . Currently we are experiencing long wait periods or timeouts retrieving lists due to the number returned (over 20,000 in our case). We noted in the API documentation there are no filters to retrieve only active lists. Do you have any recommendations for optimizing this endpoint? In this situation, the list names returned are used in a UI, so keeping this endpoint synchronous (versus the bulk async option) is preferred. We have tried changing the batch sizes, but that has not improved performance. We do have that set to 300 as a default. 

1 ACCEPTED SOLUTION

Accepted Solutions
SanfordWhiteman
Level 10 - Community Moderator

Re: REST API endpoint optimization


... In this situation, the list names returned are used in a UI, so keeping this endpoint synchronous (versus the bulk async option) is preferred.

Don’t believe there even is a bulk extract option for this endpoint anyway, no?

 

In any case — not much you can do except (a) caching and (b) parallelization (of course you also need to stay under the overall concurrent request limit, so start with 2 threads).

View solution in original post

1 REPLY 1
SanfordWhiteman
Level 10 - Community Moderator

Re: REST API endpoint optimization


... In this situation, the list names returned are used in a UI, so keeping this endpoint synchronous (versus the bulk async option) is preferred.

Don’t believe there even is a bulk extract option for this endpoint anyway, no?

 

In any case — not much you can do except (a) caching and (b) parallelization (of course you also need to stay under the overall concurrent request limit, so start with 2 threads).

View solution in original post