I am testing Identity Security Cloud V3 API through postman, and I notice below behavior:
I trigger Get Account Lists and receive list of account that is in ISC.
Prior to that, I have added 5 new accounts through flat file and the accounts has been populated in ISC and user is able to register and login fine.
I noticed that result for Get Account Lists API, there is 2 accounts not included.
I further compare for example Account A (present in ISC and Postman result) and Account B (only present in ISC), I don’t see any difference such as email, given name has been populated correctly.
Appreciate guidance on pointing correct direction on how to check further on this.
Thanks, but not sure what you meant by “wired”. The env is using tenant ID and PAT is generated (using sp:scopes:all). Under Variable Request, the domain is “identitynow-demo”, is this advisable to use?
Have you confirmed that there is no limit or filter set in your request headers? Also I believe the default limit is 250 for lists, so you may have hit that limit.
There is no limit or filter set but I notice that is default 250. Anyways, it seems this is the limit to retrieve the all the accounts using “GET {{baseUrl}}/accounts” and to retrieve all the accounts, I use “POST {{baseUrl}}/search” and set query under body, right? I did try and it works but want to further clarify if this is correct method.
The default limit 250 applies to most ISC APIs unless mentioned otherwise.
The POST method you suggested should work for the use case you are looking for as long as the actual query in the body is correct or filtering out the missing account.
What are the other parameters you are in your body?
Could you perhaps share a sample query you are using