I was following the tutorial
https://codelabs.developers.google.com/add-to-wallet-web for building a generic pass over the api.
using https://github.com/google-pay/wallet-web-codelab as repo.
after some struggling with the 7 days test account (if someone gets 403 unauthorized requests check that you use the same iam email for the test account on the register page)
okay, all works well, i get the stored wallet object back but when i try to reach the URL
Test-URL with JWT there is always an undefined error coming back and I have no clue how to debug or check what is the problem.
anyone who could give hints on what is going wrong here?
thanks!
I am using CE 10.4 and this example from Stephen Ball:
https://github.com/DelphiABall/Azure-Cognitive-Services
From that example, I tried "Speech Service" and always get a 401:
Access denied due to invalid subscription key or wrong API endpoint. Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource.
Fiddler shows, that subscription-key is sent in the Body, not Header.
My Key works in other Application.
As the Code is published from an official Embarcadero Representative, I assume, the Code is right.
Can anybody confirm this behavior - and/or knows, how to change the Code?
Ciao Luigi
In the meantine, the issue is fixed.
Stephen updated the repository.
Today in the Bing the news search API response Json, I found that the url parameter is coming in a different way then it was coming previously.
As per the documentation at https://learn.microsoft.com/en-us/azure/cognitive-services/Bing-News-Search/quickstart#the-response
The url parameter should start with
"url" : "http://www.bing.com/cr?IG=CCE2F06CA.......www.abc.com/......"
But since today it is starting with
"url" : "www abc.com......"
It is omitting the "bing.com...." prefixes..
Please confirm if this was changed recently and any plans to support the original one ??
Please confirm if this was changed recently and any plans to support the original one .
It seems that it is changed recently. We could check the document history from GitHub.
Based on my experience, it seems that there is no plan to support the original one.
But I also recommend that you could report an Azure support request to get the help from Azure team directly.
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
Yesterday, I was doing some test with Instagram API. I want to design a web page where I show the lastest photos in our account (Some like social feed). Today, I'm recieving this error: "The client used for authentication is no longer active.".
Somebody knows if I did some wrong working with your API and How can I do to fix this problem.
Best regards.
Thanks.
I'm running into similar issues. Have not been able to successfully pull anything through the API for over 12 hours.
Check out this link for quick API testing:
http://instagram.com/developer/api-console/
Nothing seems to work.