Quickbooks API v3 release - quickbooks

We are trying to use QB API for java (ipp-java-devkit 2.0.9) but we are not able to fetch refunds....there is no support to know whether an invoice is a refund or not.
I've read in some posts that v3 will have such support but it is not available yet. Do you know whether QB intends to release this version or will they stop their development? (I read months ago v3 release was planned for 2012 but we are in 2013 and it has not been released yet).
v2 is very incomplete, its documentation (javadoc) is really really bad (it contains many errors on fields availability for QBD or QBO) so v3 is our last hope for an usable product that matches our needs as well.
Regards

QB desktop allows small business owners to enter a negative quantity to return merchandise (inventory will be adjusted accordingly). So as long as the total of the invoice is positive, users can have as many lines with negative quantity to mimic merchandise that has been returned (aka refunded)

Related

Can a group of 3 researchers share/pool Twitter API tokens to accelerate/improve data collection on a sentiment analysis project?

Our group is working on a sentiment analysis research project. We are trying to use the Twitter API to collect tweets. Out aimed dataset involves a lot of query terms and filters. However, since each of us has a developer account, we were wondering if we can pool API access tokens to accelerate the data collection. For example, we will make an app that allows us to define a configuration file that contains a list of our access tokens that the app will try to use to search for a tweet. This app will be run on our local computer. Since the app uses our individual access tokens, we believe that we are not actually not bypassing or changing any Twitter limit as the record is kept for each access token. Are there any problems legal/technical that may arise from this methodology? Thank you! =D
Here is a pseudocode for what we are trying to do:
1. define a list of search terms such as 'apple', 'banana'
and 'oranges' (we have 100 of these search terms, we are okay
with the 100 limit per tweet)
2. define a list of frequent emotional adjectives such as 'happy', 'sad', 'crazy', etc. (we have have 100 of these) using TF-IDF
3. get the product of the search terms and emotional adjectives,
in total we have 10,000 query terms and we have computed
through the rate limit rules that we would need at least
55 runs of 15-minute sessions with 180 tweets per 15-minute.
55 * 15 = 825 minutes or ~14 hours to collect this amount of tweets.
4. we were thinking of improving the data collection by
pooling access tokens so that we can trim down the time
of collection from 14 hours to ~4 hours, e.g. by dividing the query items into subsets and letting a specific access token work on a subset
We were pushing for this since we just think it's efficient if it's possible and permitted since why not and it might help future researches as well?
The question is, are we actually breaking any Twitter rules or policies by doing this? By sharing one access token per each of us three and creating an app that we name as clones of the research project, we believe that in turn we are also losing something which is the headroom for one more app that we fully control.
I can't find specific rule in Twitter so far about this. Our concern is that we will publish a paper and will publish the app we will program and use for documentation and the app we plan to build. Disclaimer: Only the app's source code will be published and not the dataset because of Twitter's explicit rules about datasets.
This is absolutely not allowed under the Twitter Developer Policy and Agreement.
Twitter developer policy 5a:
Do not do any of the following:
Use a single application API key for multiple use cases or multiple application API keys for the same use case.
Feel free to check with Twitter directly via the developer forums. StackOverflow is not really the best place for this question since it is not specifically a coding question.

youtube data api pricing [duplicate]

Is there a way to (paid or unpaid) to increase the 5,000,000 units/day quota limit imposed when using version 3 of the YouTube API?
I have read that a video upload alone uses 16,000 units - this equates to only ~312 videos a day.
I have signed up for 'billing' but still don't get an option to increase from the "courtesy limit" of 5 million.
Yes, there is an elaborate form for applying for higher quota.
It is linked in the developer console for example at: http://console.developers.google.com/apis/api/youtube-json.googleapis.com/quotas?project=YOURPROJECTID
The form starts off with some statements:
This Application will ask you detailed questions about:
(i) your business, (ii) your use of each YouTube API (current and
proposed use, as applicable), and (iii) each of your website or
software application that uses or will use YouTube API(s) (each an
“API Client”).
This application also requires you to submit screenshots and design
documents relating to your API Client(s) and your use of YouTube
API(s). If you do not have these ready, please apply once these are
available.
We will strive to respond to your application as soon as possible,
provided that, all required supporting materials are submitted and
sufficient, and all questions are thoroughly answered.
Note: Please do not apply for more quota unless you are actually close to hitting your current limit.
There is a Form but they do not approve extra quota at the moment. Maybe in the future. Best would be to contact your Google Account Manager (If you have one assigned)
https://docs.google.com/spreadsheet/viewform?formkey=dDdnNVF3aGpuLXV1R2V2Nzg3QjJoZWc6MQ

Uber api number of nearby drivers

I was wondering if the current api can tell the number of drivers near a given location. It would be more interesting if i can see how close they are to location.
We currently don't expose this granularity of data through the Rides API. The closest to this feature would be the estimates related to Uber products. For instance, you can get the ETA (in seconds) for available Uber products, which is an indicator of how close driver partners are to the given location.
Thanks for raising the question and expressing your interest in such a feature. It helps us to understand what the community is looking for so we can prioritize what gets built and released in the future!
Keep an eye on the Uber Developers blog for news around current and upcoming APIs.

Is there any way to increase the YouTube API v3 Quota Limits?

Is there a way to (paid or unpaid) to increase the 5,000,000 units/day quota limit imposed when using version 3 of the YouTube API?
I have read that a video upload alone uses 16,000 units - this equates to only ~312 videos a day.
I have signed up for 'billing' but still don't get an option to increase from the "courtesy limit" of 5 million.
Yes, there is an elaborate form for applying for higher quota.
It is linked in the developer console for example at: http://console.developers.google.com/apis/api/youtube-json.googleapis.com/quotas?project=YOURPROJECTID
The form starts off with some statements:
This Application will ask you detailed questions about:
(i) your business, (ii) your use of each YouTube API (current and
proposed use, as applicable), and (iii) each of your website or
software application that uses or will use YouTube API(s) (each an
“API Client”).
This application also requires you to submit screenshots and design
documents relating to your API Client(s) and your use of YouTube
API(s). If you do not have these ready, please apply once these are
available.
We will strive to respond to your application as soon as possible,
provided that, all required supporting materials are submitted and
sufficient, and all questions are thoroughly answered.
Note: Please do not apply for more quota unless you are actually close to hitting your current limit.
There is a Form but they do not approve extra quota at the moment. Maybe in the future. Best would be to contact your Google Account Manager (If you have one assigned)
https://docs.google.com/spreadsheet/viewform?formkey=dDdnNVF3aGpuLXV1R2V2Nzg3QjJoZWc6MQ

Is data from past dates on the YouTube Analytics API guaranteed not to change?

Can Google guarantee that data pulled from YouTube Analytics API for any arbitrary date (e.g. March 20th, 2013) will not change in future? For example we pull all kind of reports for March 20th, 2013 today and tomorrow - is it possible to see difference in numbers?
If changes are possible - how frequent such changes could be (all time, once per month, once per year) and how big are they (numbers can get change significantly by 100%-1000%, numbers can get change slightlty by 1%-2%)?
There's no such guarantee made, and we can't offer the level of detail you're asking about regarding potential variations.
The YouTube Analytics API uses the same backend data source that the web interface uses. In general, help material that covers questions about data from the web interface also applies to data from the API.

Resources