I know just recently Netflix announced they are longer issue new public API developer keys however I got my key two months ago for a proof of concept project in development.
I just started working on implementing Netflix API data and noticed in my account / application info that the status is disabled.
Any calls I make to the API return a '403 Developer Inactive' response.
I just emailed publicapi[at]netflix.com to see if they can enable it but also thought I should see if anyone has any info here as Netflix has recommended 'developers to continue their conversations at StackOverflow with the tag “netflixapi”'.
Any information would be much appreciated!
Thanks!
They don't answer emails so save your time. They will not issue or reactivate existing keys.
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.
Anyone having trouble building API's with the new Kimono Desktop app. When I click create API the browser just stays on create API screen loading but nothing happens.
I even tried building an API that is the same as one I built when Kimono was still in business and no luck.
My existing api's still run and pull data fine.
Working just fine here.
Just a shot in the blue...did you install the new extension specifically for the desktop app? The old one can't work anymore since Kimono disabled the online service.
You can't build new APIs I think - only existing ones. :( Said something like it was not the acquiring company's policy to provide this publiclu available service but since they did not know how many businesses depended on their APIs they decided to allow existing APis to run.
You can also use their software for replace the online API. But it's an abandonware.
It's working great but on some website I can create new API because of an error.
I just find a possible (free) product that can replace Kimono : Datascraping.co.
They will include an REST FULL API within few days / weeks, as they said here.
It's a good software, but comparing to Kimono Desktop it's a little much more complicated.
Kimono got bought out and it's not working anymore.
Import.io is good but it kinda expensive for me. I've tried the free trial before but see the price starts from $249, so... https://www.import.io/standard-plans/
I don't have any progamming skills so I know very little about some web scraping frameworks like Scrapy.
You may want to look at this new web scraping software called Octoparse.
In case you want to know, here is the link:http://www.octoparse.com/
It takes a little time to begin. But they have rich tutorials on the website. Plus it doesn't require programming skills.
They provide cloud-based scraping service and API access.
You can use it to create API but you have to pay for the service. Free version doesn't have the API and cloud service.
I've been using it for 2 month with the Standard plan $89, which a lot cheaper than import.io. So far so good.
Hope it would be helpful for you.
I'm new to Instagram API and my question is how to get complete access to Instagram's API without any limitations - like API's that any other Third-Party Client Apps Like (6tag /ink361.com/insta(X))uses .i want to give my users complete access so they can (like - repost - regram - Edit - ...).
and as I read in the official documentation there is a Sandbox / Live Permission/Condition that developers can get to have that kind of Access.
If I understood you correctly, you are trying to built an app similar to the core functionalities of Instagram (or most of it!).
As you have said, they have introduced Sandbox features post November 17th, so any app created after that date will be running in Sandbox mode until you give it for a review.
Few things to note here:
They are restructuring their APIs, meaning there are lot more restrictions and validations!
I'm not sure, but if you search on Google about their restructuring of APIs, it clearly states that Instagram is trying to block an app which has most of the core functionalities of it - likes/posts/feeds etc. This is to secure their users' data and prevent malicious activities.
Most of the endpoints are restricted and some of the old ones are slowly being deprecated.
So, I guess from now on you can't build an app on Instagram which is similar to theirs. Regarding the existing apps which does the same, they have to remove those deprecated endpoints as these new features will be imposed on them post 2016!
At the moment, you can the endpoints available to you are documented on http://instagram.com/developer/endpoints/.
Hope it answers all your queries!
I was wondering if it was possible to detect what song a user is listening to from his/her current active device via the spotify web api.
Thanks.
I know this is an old question, but there is a new beta API endpoint available that supplies this information. It does have some bugs that I've noticed though.
Stations only: If you change stations, you have to restart Spotify to get the API endpoint to update and continue updating.
According to bug reports, it lags behind 20 to 30 minutes at random. I haven't had that problem, so it may be fixed.
GET https://api.spotify.com/v1/me/player/currently-playing
Docs: https://developer.spotify.com/web-api/get-the-users-currently-playing-track/
This is not possible using the web API. If you're writing a Mac app, you can use the Spotify Desktop Client's AppleScript API to access the current track. If the user is scribbling to Last.fm, you can use Last.fm's APIs. Otherwise, this data is not accessible.
I am working on application in which i am implementing In-App-Purchase,On buying the product through my application i can fetch all the information regarding the products in my console, but the problems occurs where i am not getting the pop-up from App Store which shows all the information to buyers. I cannot figure out the problem. Please suggest some solution for this.
Thanks.
Apple's IAP backend (test mode) has been up and down over the last 5 days, mostly down, there's been no official confirmation of the outage, just check twitter for similar complaints.
need code.. or follow troy brant's awesome tutorial
http://troybrant.net/blog/2010/01/in-app-purchases-a-full-walkthrough/