to get a personalized navigation.
to get a personalized navigation.
We want to retrieve all our debtors (customers) with an API call. We can retrieve 1000 records (PageSize) at a time and we have more than 25.000 costumers. That means we will have to retrieve 25 pages. The first page takes about 25 seconds, but after that it increases per page. The API call is: https://integration.visma.net/API/controller/api/v1/customer?pageSize=1000&pageNumber=X
Where X is the page number:
24 | 03:49 | |
23 | 04:05 | |
22 | 03:41 | |
21 | 03:20 | |
20 | 03:19 | |
19 | 03:02 | |
18 | 02:39 | |
17 | 02:35 | |
16 | 02:28 | |
15 | 02:18 | |
14 | 02:11 | |
13 | 02:03 | |
12 | 02:20 | |
11 | 01:48 | |
10 | 01:42 | |
9 | 01:24 | |
8 | 01:14 | |
7 | 01:11 | |
6 | 01:01 | |
5 | 00:47 | |
4 | 00:37 | |
3 | 00:32 | |
2 | 00:22 |
The problem is that if it takes longer than 5 minutes, our API environment in Azure gives up and sometimes this happens with pages over 20. How can we retrieve all costumers with an API call without taking so much time? The amount of data is not the problem because that is about 1 MB per page.
Kind Regards,
Frank Schimmel
Could you please send us the following details ? (mailto: developersupport@visma.com)
-Financials ERP Company ID <ipp-company-id>
-API Client ID (Token generated & used with )
-Approximate TimeStamp/s of the request/s
Thanks.
Hello Frank,
Thank you for the information you've provided.
As it's mentioned, the amount of the data is relatively small and chunked into separate pages but It'd be also worth to try narrowing your data scope down by using
?lastModifiedDateTime=YYYY-MM-DDT00:00:00&lastModifiedDateTimeCondition=>
parameters. (Visma.net API Pagination Explained)
We'll convey this case to our infrastructure team to check why subsequent calls have a higher response time and how this can be improved.
Copyright © 2022 Visma.com. All rights reserved.