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
 
Answered
Stuck on Q2 APIs: Need Advice on Client Transaction Retrieval

We are in the very early stages of evaluating and utilizing the Q2 APIs to support real-time transaction alerts based on transaction status and our established cutoff times.

As we've reviewed the available APIs, we have not identified an endpoint that allows us to retrieve transactions for a specific client, or even all transactions across clients, without first providing a transaction ID. Based on our research so far, each endpoint appears to require a transaction ID as a prerequisite for retrieving transaction details.

I wanted to reach out to the developer community to see if anyone has successfully identified a way to retrieve all transactions for a specific client, or obtain a list of transactions without already having the transaction IDs. Any insights, recommendations, or experiences would be greatly appreciated.

Posted 16 days ago
Votes Newest

Answers


I haven't used the Caliper API in production before, but if you have access to the SDK, you can deploy an extension as a custom endpoint and then query the DB as needed for transactions.

Here's a decent writeup for Transactions in the SDK docs: https://docs.q2developer.com/guides/database/transactions.html

When I needed to pull transaction data, I had an extension that queried the Backoffice API - Generated Transactions endpoint (via the DB object in my SDK extension). It was a periodic job that ran every night and pulled an entire days worth of Generated Transactions (trans that originated in the Q2 system, not the core) and analyzed them for certain properties. However, to instantiate the DB object, I needed to pass in HQ credentials which needed to be setup by another employee at my FI. Then they needed to be rotated every so often.

Backoffice API docs: https://docs.q2developer.com/guides/online_integration/backoffice_calls.html
Generated Transactions docs: https://docs.q2developer.com/api_references/q2_sdk/db/db_objects/generated_transactions.html#module-q2_sdk.hq.db.generated_transactions

Hopefully something here is helpful!

Posted 6 days ago
137 Views
1 Answer
16 days ago
6 days ago
Tags