I need to fetch transactions of our users accounts (investment accounts, if it matters).
Now, my favorite method is "Approach 2", as mentioned in this official guide, as it requires using only one API method and generally, seems simpler to implement. But, I have a few questions on this approach:
Can I use this approach? I'm asking since the API method page doesn't remind it but rather mentions only 'approach 1'.
The numbering of transactions - when I request transactions shall I start from transaction number 0 or 1 ? The couple of pages linked above each uses different version :-)
Lastly - the page that details the approaches talks about setFirstCall parameter, yet the method API page doesn't mention it. I just wanted to verify that I need not care of this parameter.
Thanks!
1) Can I use this approach? I'm asking since the API method page
doesn't remind it but rather mentions only 'approach 1'.
Yes you can use approach 2 from this guide
2) The numbering of transactions - when I request transactions shall I
start from transaction number 0 or 1 ? The couple of pages linked
above each uses different version :-)
Please start from 1. We have updated the guide accordingly.
3) Lastly - the page that details the approaches talks about
setFirstCall parameter, yet the method API page doesn't mention it. I
just wanted to verify that I need not care of this parameter.
This parameter has to be passed to use approach 2.
it should be passed as transactionSearchRequest.firstCall = false
Related
I am working with React Native/Redux and an express/postgresql backend.
I have an api call to create a comment that returns the created comment as well as some of the information concerning the user.
Those are two different api calls.
Now I also need the updated comment count to send to the feed reducer so that the count is still correct when they close the comment tab.
I was wondering if it is still okay to have 3 queries in one API call and maybe more general/meta, if there might be a better solution to this if that isn't the case.
Kind regards
It's perfectly fine to do multiple queries in a single API call. You can do as many as are required to complete a single coherent interaction between the server and client.
I'm trying to add ~20 tracking category options programmatically and I've seen that calls to add the first two values returns in < 1 second, but after that calls timeout.
If I restart with a new session, I see the same behavior (first two calls are quick and then calls timeout).
My question is, is there rate limiting on the Xero API? Has anyone seen behavior similar to this? Workarounds or fixes?
UPDATE: I forgot to add that i did look at rate limits posted by Xero, I'm not anywhere close to any of those limits
I think xero API give you the option to save a bunch of tracking categories within one request
I'm using the twitter API and would like to get all tweets from a given time period where a given user was mentioned.
I tried the search API with the until parameter where I could get the tweets for the previous 7 days from the date which is not the best, but fine. However, in this case the API only returns the number of tweets without the details.
Any ideas how to do it or what I'm doing wrong?
Thanks!
Strange, https://dev.twitter.com/rest/reference/get/search/tweets says it should return tweet objects. Are you sure you implemented it correctly? Which library are you using? Maybe there is a fault in its implementation. Another library could therefore be the solution.
Don't know whether this satisfies your needs, but you could also try to use the GET statuses/mentions_timeline API . This API returns up to 800 tweets in which the user was mentioned.
EDIT, based on the comments on this post:
You are doing 2 things wrong, namely:
As stated in the documentation the until parameter has a 7 day limit. So you can only retrieve up to 7 days of tweets.
Furthermore, you are making incorrect use of the since parameter. The since parameter specifies since this tweet (so the id of the tweet), not since this date.
Please read the documentation carefully. It is written very precisely and contains all the answers you probably need.
I am stuck somewhere, I am building an application, where I want to total numbers of calls (stats) only, No Call Duration, No Number, No contact Name... Just total numbers of call, is there any way which doesn't breach apple development policy.
because accessing call history data is not allowed, is there any event which can tell us the call count, or any services which shows specific status at the time of call so we can get the status of active call and number of calls by adding them in sum.
Please have a look of my query and give me best possible answers on basis of the same.
Regards,
Andy
Unfortunately no. There is no API for that.
The information you seek is located in the Call History Database (call_history.db)see this wiki. This file is very useful in forensics but cannot be accessed on a non-jailbraked iphone using legit means. More information here and here.
It is however, under certain conditions, possible to detect the start of a call: see Detecting the call events in ios on SO. You can also check the Core Telephony Framework Reference. This will give you ways to access some call informations, such the unique identifier for the call. That may be enough for you to count calls.
I'm trying to pull from the API of story counts for the latest release, broken down by schedule state. There's a report that does that currently, but I don't see any exposed method in the API. Does anyone know if that's possible to obtain?
You should be able to do a query for each schedule state, and grab TotalResultCount from the body of the response. For example:
https://rally1.rallydev.com/slm/webservice/1.31/hierarchicalrequirement.js?query=(ScheduleState = "Defined")
https://rally1.rallydev.com/slm/webservice/1.31/hierarchicalrequirement.js?query=(ScheduleState = "In-Progress")
and so on. Since there are only four "built-in" schedule states, plus an optional one before Defined and an optional one after Accepted, it's at most 6 requests.
You can further filter down Alan's examples above with some release information as well by changing the query parameter:
query=((ScheduleState = Defined) AND (Release.Name = "My Release"))
Are you writing an app using the App SDK or using one of our other REST toolkits (ruby, .net, python)? You may be able to find some better code examples here:
http://developer.rallydev.com
You might also try the Batch Query approach that allows you to just return the size of the query instead of counting the results. See the
"Getting the Size of a Collection" example of the api doc:
https://rally1.rallydev.com/slm/doc/webservice/batch.jsp#example8