Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
← Back to post

Revisions 2

Retrieving complete list of online members through the Caliper APIs
Retrieving complete list of online members through the Caliper APIs
Hi Bradley — apologies for the delayed response, and thanks for reaching out. In general, we want to avoid using the Caliper API as a reporting or bulk data-export mechanism, particularly because API requests are subject to the AWS 29-second timeout and the API is designed for quick retrieval. Using the Lookup Customer endpoint with a `createdOnOrAfter` value may be a reasonable approach if you’re looking to retrieve customers created within a specific date range. If that doesn’t meet the use case, a custom endpoint may be another option. That said, pulling a very large volume of customer records through the API is discouraged, since Caliper is not designed for batch imports or large-scale reporting workloads. That's also a reason why we don't provide the ability of fetching all customers under a given group, as the number of customers would grow and the amount of data the API would need to pull could significantly increase. Let me know if you have additional questions! Feel free to open a ticket as well with your use case. Best, Solène
Hi Todd and Bradley — apologies for the delayed response, and thanks for reaching out. In general, we want to avoid using the Caliper API as a reporting or bulk data-export mechanism, particularly because API requests are subject to the AWS 29-second timeout and the API is designed for quick retrieval. Using the Lookup Customer endpoint with a `createdOnOrAfter` value may be a reasonable approach if you’re looking to retrieve customers created within a specific date range. If that doesn’t meet the use case, a custom endpoint may be another option. That said, pulling a very large volume of customer records through the API is discouraged, since Caliper is not designed for batch imports or large-scale reporting workloads. That's also a reason why we don't provide the ability of fetching all customers under a given group, as the number of customers would grow and the amount of data the API would need to pull could significantly increase. Let me know if you have additional questions! Feel free to open a ticket as well with your use case. Best, Solène
28 days ago
Retrieving complete list of online members through the Caliper APIs

Hi Todd and Bradley — apologies for the delayed response, and thanks for reaching out. In general, we want to avoid using the Caliper API as a reporting or bulk data-export mechanism, particularly because API requests are subject to the AWS 29-second timeout and the API is designed for quick retrieval. Using the Lookup Customer endpoint with a `createdOnOrAfter` value may be a reasonable approach if you’re looking to retrieve customers created within a specific date range. If that doesn’t meet the use case, a custom endpoint may be another option. That said, pulling a very large volume of customer records through the API is discouraged, since Caliper is not designed for batch imports or large-scale reporting workloads. That's also a reason why we don't provide the ability of fetching all customers under a given group, as the number of customers would grow and the amount of data the API would need to pull could significantly increase. Let me know if you have additional questions! Feel free to open a ticket as well with your use case. Best, Solène