Why when I access developer.teleport.org it shows a 403 error? - http-status-code-403

I was about to use the teleport api to get some city pictures. Suddenly, I was having trouble getting the images. When I access the website, I get this.
Is it just me or is there something going on with teleport org?

Related

Instagram API throwing OAuthAccessTokenException 400 error using client id

I was using the following api to get the latest 3 posts from public accounts to show on the website:
https://api.instagram.com/v1/users/{user-id}/media/recent/?client_id={client-id}&count=3
I had created an app to get the client-id.
However from today, this API has started throwing the following exception:
{
meta: {
error_type: "OAuthAccessTokenException",
code: 400,
error_message: "The access_token provided is invalid."
}
}
Could you please let me know as how to resolve this?
Based on the date, you probably have an older app that got hit by the API migration today, like mine. In short, Instagram decided to make developing for their platform WAY more annoying by requiring all API requests to be authenticated per user, even for data that users shares publicly. So you (like me) will likely be redesigning you app entirely.
To tell, log in to instagram.com/developer and click manage clients; then hit edit next to the set of keys your're trying to use. Up near the top, it will have a section called 'Client Status' -- if yours reads 'Sandbox Mode', fun times ahead! Hopefully you interact with less than 10 users and can stay in sandbox mode, otherwise you'll have to write an essay, film a video, and basically plead to get your permissions back (probably in a few months, when some Instagram intern finally digs his way down to you in the pile of applications). If it reads something eles, you've got another problem altogether and should thank your lucky stars.
In the meantime, I guess I'll get back to sending out dozens of emails to the maintainers of our many, many affiliated Instagram accounts to explain the issue and try to get permissions, so provided we get approved by then, all our social media displays aren't broken during a huge event Saturday. Another option might be to use the OAuth-less json response available here, but that might break terms of service.
I have a solution to this. If you are using the same code I am, which appears likely. I was pulling the last two images using this.
https://api.instagram.com/v1/users/{user-id}/media/recent/?client_id={client-id}&count=3
What I did to get this working is the following.
Login to your Instragram account you are using as the application.
Go to the developer (API) area. https://www.instagram.com/developer/clients/manage/
Manage clients. Make sure your website URL is the same as your valid redirect URL.
Add new Sandbox User. Put in the account of the IG photos you want to reach.
Hit this URL: https://api.instagram.com/oauth/authorize/?client_id=CLIENTID&redirect_uri=REDIRECT_URI&response_type=token where the client ID is the same one you used in your previous app above.
You should get back and access token URL. Copy your access token.
Login as your account that you want the IG photos of. The account you added as a sandbox user and go to developer and approve the Sandbox Invites.
Change your original URL above from https://api.instagram.com/v1/users/{user-id}/media/recent/?client_id={client-id}&count=3 to https://api.instagram.com/v1/users/self/media/recent/?access_token=ACCESS_TOKEN with your access token.
This is the IG API Media endpoint documentation: https://www.instagram.com/developer/endpoints/users/
After that, it all worked for me and while you are in the sandbox, you should be able to pull the last 3 photos or at this point, figure out how to read the JSON to do so.
Has your app been approved after the June 1st Instagram platform changes?
http://developers.instagram.com/post/145262544121/instagram-platform-update-effective-june-1-2016
If you want to retrieve the user media file then try this, It's working for me
https://graph.instagram.com/me/media?fields=id,caption,media_url,media_type&access_token=ACCESS_TOKEN
For some reason the token is no more valid. Request it again.
Possible reasons why a token is no more valid:
changed password
verified the account
logged-in from a different country

Browser Said Invalid Request When I Tried to Access a Picture of Instagram

Recently, I wrote an app to synchronize photos in my Instagram to another platform. The GET /v1/users/self/media/recent?access_token=ACCESS_TOKEN result should contains the links to my pictures, like
https://scontent.cdninstagram.com/hphotos-xaf1/t51.2885-15/s640x640/e35/sh0.08/11330602_751572388302808_972254350_n.jpg,
and it went very well. But today after clicking the link, it told me Invalid Request. I'm not sure what happened to this cdn link. Any hints would be appreciated.

Why does the Spotify Web API throw a 500 error when getting playlists from a specific user?

This endpoint on Spotify's Web Api throws a 500 error for the username "spotify":
GET https://api.spotify.com/v1/users/{user_id}/playlists
Is this intentional on Spotify's end? Does Spotify not wants developers to access its playlists.
Note - All other usernames work fine
A 500 error should always be treated as being unintentional. If the server side wants to limit access a response code in the 400 range should be used instead, like 403 or possibly 401. It is likely that there are so many different public playlists for the Spotify account that one of them has triggered a bug. If for some reason the error code 500 is intentional, it is still a bug, but in the API, which should be fixed.
I work at Spotify, but don't have direct access to this system. I will let people know.

Lync UIsupressed Client: No Photo of contacts

I've asked this question on the MSDN forums a week ago, but unfortunately I don't get a reply. This functionality is so basic that I can't imagine this can't be done.
http://social.msdn.microsoft.com/Forums/en-US/c6aaaefe-92e1-45b3-8b41-8edbc9866058/cannot-get-picture-of-contacts?forum=communicatorsdk
We are developing a Lync SupressedUI Client with the Lync Client SDK.
We want to show the photo of contacts of the logged in user.
When we turn off UISupression we do get a photo.
When we turn on UISupression we do not get a photo.
There are 3 ContactInformationTypes that could be relevant:
- ContactInformationType.Photo
- ContactInformationType.IconStream
- ContactInformationType.IconUrl
When using Photo it does work when UISupression is turned off.
But not when UISupression is turned on.
The exception that we get is: ItemNotFoundException
When using IconStream we get the exception: FileNotFound Exception.
The exception does not tell which file. This is part of the message: Exception from HRESULT: 0x80070002
When calling ContactInformationType.IconUri we are getting an ItemNotFoundException.
Showing the photo of the logged in user is not a problem at all.
Strange enough when contacts are in the frequently used contacts group we do get a photo.
Has anybody made it work to show photos of contactpersons when UISupression is turned on?
By accident we have a solution that does show the photos of the contacts.
it's needed to start a conversation for every contact in the contactlist.
after that the Photo can be obtained.

Spotify Web API call throws 502 Bad Gateway Error

I am building a web application using the Spotify Web API. The calls are pretty straight forward and I don't understand if it is me doing something wrong, or if there is something wrong with the Spotify service.
I implemented the lookup call (works fine) and then add track IDs to my database when a button is clicked next to one of the results. I then do an ajax call to display that track in the "Play Button" iframe.
Instead of showing my playlist now, I very often get a 502 Bad Gateway error. (This error also appears on the Spotify website where the example is supposed to be shown.)
Is this something I cause? My browser / system causes?
Thanks a lot in advance!
(This error also appears on the Spotify website where the example is supposed to be shown.)
This suggests that the problem is on Spotify's side, assuming you're giving the Play Button a valid Spotify URI. Hang tight for a while and it should sort itself out.

Resources