In an effort to get music-related events for an app we're building, we've mulled through Myspace's decidedly clunky authentication process and managed to set up a subscription and endpoint.
Using all this fun stuff:
http://wiki.developer.myspace.com/index.php?title=Category:Real_Time_Stream
http://wiki.developer.myspace.com/index.php?title=Stream_Subscription_API
http://wiki.developer.myspace.com/index.php?title=Stream_Subscription_Example_Walkthrough
The Myspace GET request verifies the existence of our subscription. So all we were hoping to do was sit back and wait...
...but even with no query filtering set whatsoever (i.e. we should get EVERYTHING that happens!), we seem to get no data pushed our way.
Most worrisome is that I don't see anyone talking about this on the web anytime recently. Does it still exist? It's still on Myspace's Developer homepage. Did they forget to take it down? Is their sense of self-esteem so low at this point (for obvious reasons) that they've stopped caring about whether their services work?
A boolean answer with conclusive supporting evidence would be most appreciated.
Links to resources and discussions less than a year old would be an awesome bonus.
Myspace has a very inactive MySpace Developer Team News and Announcements that lists various API modules designed to work with the ActivityStrea.ms standard and has a dedicated Activities API webpage with examples.
Once you view that page, you'll see they work within the depreciated OpenSocial API v1 Platform.
In reference to the Stream Subscription method your using, the History Log has the last entry at January 2010. It's safe to say that method has been abandoned. Reference screenshot:
I visited Wikipedia Myspace Page to discover what Developer API is currently used and was greeted with the same outdated information that you already have. The last API used was in 2010.
There still is hope for your goal of getting music related events via a current API method: The above Wikipedia page has a section titled Decline: 2008–present which links to footnote 71 for a January 2012 article: MySpace is Reborn at Panasonic Press Conference, Unleashes Justin Timberlake
That Wikipedia announcement reads:
In January 2012, the company announced at CES that it would introduce MySpace TV with Panasonic.
While Myspace is currently under the radar for developers and your goal is to get Music Related Events (from music artists?) via API, consider using YouTube API that has a powerful search feature to find such events from artists with legitimate YouTube ID's.
If that's not an option perhaps Myspace TV / Panasonic venture will come into fruition soon.
As this is not a happy answer, it's only fitting to Cry Me A River until a new API is realized.
Edit: As your looking for a Boolean Answer, MySpace API is false.
To complement that Boolean state, these other JavaScript values are considered false too: 0 -0 null "" undefined NaN.
WordPress for MySpace API is abandoned with last blog entry April 2010.
The MySpace Stream Subscription API is a component of MySpace RESTful API that is abandoned.
Finally, the MySpace Developer Home Page was last updated on December 2010.
Even to this day, Google Groups for MySpace API has no activity since July 2010.
The above links is Further Evidence that the MySpace API is dead.
Related
So, I stepped once at this problem. I had offered a website that used the SoundCloud API. Everything worked properly. Content was extracted from the JSON and placed in the layout of the website. However, I received an email one day from the owner of the website, which indicated that the website did not work properly. I then came out to investigate and came to the conclusion that the "problem" was not on my side, but at SoundCloud's side. I studied on the API page of SoundCloud and came to the conclusion that the API had received a major update, making the link with SC and the site no longer worked.
Lately I'm trying many new APIs to, including those from Instagram and Dribbble. I was therefore wondering if it is at all possible to ensure that such problems can be reduced in the future or it might be appropriate API pages of this third-party APIs to monitor?
There's no "right" answer. After many years of using and maintaining many APIs here are some of the conclusions I've come to:
The best providers let you work with a specific version of their API whose interface and expected behavior never changes. They might release bug fixes and new endpoints, but you can be confident that as long as the API is supported it will not break your system.
A good provider will provide an end-of-life date for each version of their API. It's up to you to keep track of when you need to update.
Paid services will often be supported longer than free services. Plus the contract / SLA will guarantee it remains available for a specific amount of time.
The most popular APIs often have mailing lists and/or blogs. For those that offer it, sign up to be notified of updates. For those that don't you'll have to monitor their blogs or news posts. And I suggest not using any service that would drop support for an API version without warning.
I built a module for my company's marketing team to fetch all the photos based on a hashtag. Such as #nofilter.
I was using the URL https://api.instagram.com/v1/tags/nofilter/media/recent with no problems until Instagram decided to change their API authentication to OAuth.
I followed the new guidelines but my client is still in sandbox mode and the API call doesn't return anything anymore. All it returns is:
{"pagination": {"deprecation_warning": "next_max_id and min_id are deprecated for this endpoint; use min_tag_id and max_tag_id instead"}, "meta": {"code": 200}, "data": []}
It seems like I need to submit my application to be reviewed before going live. But this doesn't seem possible, based on what i found from their submission guideline below. Is there any workaround for this?
====== UPDATE July 8th, 2016
I have found one of those 3rd parties that instagram mentioned, but the pricing is awful https://www.dialogfeed.com/pricing/
189 euros per month seem a bit steep
I had to deal with this. Their documentation is pretty unhelpful and doesn't seem to offer any solution for someone just wanting to collect relevant links, which should be no prob.
Fortunately, the script on an Instagram page provides easy access to their structured data. In my rails app I create a headless browser and just hit their url. I provided my solution as an answer to another question:
https://stackoverflow.com/a/38572893/4888422
I just started developing an Intuit App yesterday and was really getting going on integrating with QuickBooks Desktop. Then today I logged in to continue work and was greeted by several missing pages on Intuit's IPP site and a link that says "Deprecated QBO V2 and QBD V2,V3". The only API that appears to not be deprecated is QBO V3.
I cannot find any announcement from Intuit about any upcoming deprecation. Does anybody have any info on whether I am safe to continue developing my app to connect to QBD or do I need to talk to our accountant to move over to QBO instead?
EDIT: I have marked Jarred's answer as the accepted answer because he associated with Intuit and answers my specific situation. Also check Charlie's answer for additional details specific to other scenarios.
I interviewed several people from Intuit at the Sleeter Accounting Solutions Conference this week, including (amongst others) Dan Wernikoff, Senior VP.
I'll have an article in my blog on this (http://www.sleeter.com/blog/) next week - I'm transcribing my recordings and clarifying points.
There are a LOT of points here, but to address what you are looking at -
If you are writing an IPP app using V3 for QBO - no problem (and in fact, some good news there).
If you are already published with IPP using V3 and Sync Manager for the Desktop, you will get continued support but don't expect any advancement there (unless you are someone big like American Express).
If you are NOT already published with IPP for the Desktop - the SDK is your option.
And there is a lot more info about this coming out
MINOR EDIT AT A LATER DATE: If you have been working with IPP for the desktop you MIGHT get approved to continue - no guarantees on that (but it seems they might be lenient). But In my opinion you can't expect any significant new features (as in, more data access) moving forward unless you are a significant partner with a contract with them (such as, American Express).
Intuit will not prevent you from going live with your application that you have spent the last 6 months working on. We have a set of guidelines for grandfathering in developers who have invested in using the v2 REST API for QuickBooks Desktop.
feel free to contact me directly if you have more questions.
#Charlie if you could correct your statement regarding if you are NOT published then you need to use the QBXML SDK. That is too generic, we will evaluate each developer on a case by case basis.
regards,
Jarred
My writeup on this subject is available at http://www.sleeter.com/blog/2013/11/quickbooks-software-integration/
Note that Dan Wernikoff, Senior VP at Intuit, has been leaving comments in several of my articles in the blog.
Blair, you have a reasonable concern. However, given the REASONS that they made this change, I would SPECULATE that Intuit won't be pulling the SDK. What isn't clear, at this time, is HOW MUCH support they will give the SDK moving forward.
And, as we have seen for several years now, things can change...
I've googles about it, yet couldn't understand it properly.. Not sure if it's a library or intra-server communicator..
Can someone explain me in a high-level /low-level what is meant by an API.??
http://en.wikipedia.org/wiki/Application_programming_interface
Read it from here , will hopefully clear most of your doubts.
An API stands for Application Programming Interface, which means using and existing program or code and accessing it with your code.
===
Example, Search Engine:
Search engine 1: offers search and api (if you want this can be google)
Search engine 2: uses googles api to get results (this is your one)
To get results you basically search the other search engine and get their results to yours
====
An API can be used in many ways, to access others data or code, ect
An in-depth explination can be found here: http://en.wikipedia.org/wiki/Application_programming_interface
An application-programming interface (API) is a set of programming instructions and standards for accessing a Web-based software application or Web tool. A software company releases its API to the public so that other software developers can design products that are powered by its service.
For example, Amazon.com released its API so that Web site developers could more easily access Amazon's product information. Using the Amazon API, a third party Web site can post direct links to Amazon products with updated prices and an option to "buy now."
An API is a software-to-software interface, not a user interface. With APIs, applications talk to each other without any user knowledge or intervention. When you buy movie tickets online and enter your credit card information, the movie ticket Web site uses an API to send your credit card information to a remote application that verifies whether your information is correct. Once payment is confirmed, the remote application sends a response back to the movie ticket Web site saying it's OK to issue the tickets.
As a user, you only see one interface -- the movie ticket Web site -- but behind the scenes, many applications are working together using APIs. This type of integration is called seamless, since the user never notices when software functions are handed from one application to another.
This article shows an example
http://www.codeproject.com/Tips/127316/Integrate-FB-javascript-API-to-your-asp-net-app-to
I have been using the Google Websearch API for over 1 year now. The service was deprecated in Nov 2010 but continues to provide results to date. More recently, google has started to enforce the 1,000 queries (?) per day limit on this deprecated service. I swear, last month I made over 10,000 API calls in one day without any errors from the service (same IP, same API key).
So I guess my question is has anyone found an alternative yet? I know yahoo boss is pretty good but I am working exclusively on Google for my projects. I do not mind spending money for for this service either as long as i can get 64 results from Google.
On that thought, how are services like Zoomrank able to bypass all Google limits? I have a subscription with Zoomrank and I can get daily rankings for all my keywords. Do they have a tie-up with Google or are they just accessing some secret service I don't know about.
Some people have suggested the new Google custom search, but i dont know how does that help me search the web? Google CS is limited to the CSE you create and searches within those engines. If I am looking for web results for Pizza, Google CS doesnt help me.
Thanks for your input. Much appreciated
UPDATE: #ggez44 points to some official Google documentation of the solution described below here: http://support.google.com/customsearch/bin/answer.py?hl=en&answer=1210656
You can use the Google Custom Search Engine to search the entire web.
In brief:
Create a CSE that searches a single site (e.g. google.com)
In the CSE control panel's Basics section, set to "Search the entire web but emphasize certain sites"
In the Sites section, delete the single site that you added when you created the CSE
Full details here:
http://www.google.com/support/forum/p/customsearch/thread?tid=56c0bd92dda351b7&hl=en&fid=56c0bd92dda351b7000495e3f500d83f
Once that's implemented, you can enable billing in the Google API Console at a CPM of $5, to a total of 10,000 queries.
Google API Console: https://code.google.com/apis/console/
Pricing: https://code.google.com/apis/customsearch/v1/overview.html#Pricing