Yahoo BOSS Geo api Issue - yahoo-boss-api

I am new for OAuth and for yahoo apis. My problem detail is as follows:
In my current project, we have to implement one service class in which, when we pass address,
it should use yahoo boss geo apis and return longitude and latitude of this address. We are using java in our project.
Till now I have done below mentioned following things:
I have added project detail at https://developer.apps.yahoo.com/projects and got Consumer Key, Consumer Secret etc.
But till now I didn't submit Billing info.
I am trying to run this simple java example given at: http://developer.yahoo.com/boss/geo/docs/codeexamples.html .
I using Consumer Key, Consumer Secret which I got after adding my project detail. But when ever I am trying to run this example,
I am getting status code = 503 which means service unavailable. 2-3 time I have got response in XML also.
Please let me know if I am doing any thing wrong here. Also how can I implement my requirement.

This is issue is most likely caused by a set rate limit. The error documentation can be found here:
http://developer.yahoo.com/boss/search/boss_api_guide/BOSSv2_APDX.html

In the Yahoo Boss group many people reported receiving 503 errors immediately after opening the account and putting in billing information. After 24 hours the problem went a way.

Related

Can't get Google Chat messages with Gmail API

What are the details of your problem?
Until recently, in my own web application, I used the Gmail API to retrieve Google Chat messages as follows.
I was able to get it from "Label: CHAT" by executing as follows.
(1) Acquisition of thread ID belonging to CHAT label
https://gmail.googleapis.com/gmail/v1/users/me/messages?labelIds=CHAT
(2) Get message information from thread ID
https://gmail.googleapis.com/gmail/v1/users/me/threads/[Thread ID]
However, it seems that it has been impossible to obtain it since around December 2022, and when I searched for "in: chats" in Gmail, the messages after December 10th were not displayed.
Any method is fine, so I would like to be able to get Google Chat messages as before.
Anyone know the cause and solution?
Please check.
I also tried using the Google Chat API to see if it was possible to get messages, but I could only get messages in the space, and I couldn't get direct messages, so I wasn't able to use it.
I checked all the messages in the labels that can be obtained at "https://gmail.googleapis.com/gmail/v1/users/me/labels", but it seems that chat messages are not included.
Also, in another answer, there was a description that the state included in the Gmail API was a bug, so it is possible that this bug was adapted and it was not displayed, but in that case, there is another way to deal with it. Are you there?
Access CHATS label with Gmail API

Unexpected "Cannot call API on behalf of this user" after upgrading to graph api 2.10

We've allowed sign up/access to our website using Facebook Login for a long time. Two days ago, after upgrading to graph api 2.10, this stopped working for a portion of our users. Myself and most others are unaffected.
The error message received in the Access Token response reads "Cannot call API on behalf of this user".
I can't find anything in the 2.9 -> 2.10 changelog that mentions anything remotely connected to this problem, and I've found very little on this issue externally.
A few posts suggests that it might have something to do with insufficient privacy policy settings in our Facebook app settings, but everything is in place expect the non-mandatory Data Deletion Request URL. The fact that it also works perfectly fine for me as an EU citizen (affected by GDPR) says to me that it's something else. We do not have any country restrictions in place, and those who are affected by this comes from a variety of countries both inside and outside of the European Union.
Does anybody recognize this problem?
I ran into the same problem, also after an update (from 2.9 to 3.1). The fix for me was to remove location restrictions within the facebook console (Settings > Advanced > App Restriction > Contry Restricted):
I got this idea from a comment on this similar question, and this google group thread.
ref: https://developers.facebook.com/docs/audience-network/optimization/apis/FB-login-Reporting-API
sounds like the app type should be Business
today I meet this error, follow above document, I new create a business app, then error be resolved.

Not getting attachments from Nearby Messages API

I am using Nearby messages API for android. I was getting the attachments using API before, till end of January. However, it has abruptly stopped working. I can see the request calls my app making in the google cloud console. However, I am not getting any attachment. Is there anything that has been changed on the API end?
I work on the Nearby team. We've recently discovered and fixed a problem with the default message filter, which might be what's affecting you (e.g. if you don't provide a message filter at all). The fix is rolling out within the next day or two. Apologies!

Soundcloud Developer Key

I applied twice in the google forms for a developer key for soundcloud to use a widget on my website. It has been more than 3 weeks and I have still not got any reply from them. What do I do?
I'm afraid you just have to wait until they respond. I have applied 3 times now and keep getting rejected and the response is a generic answer not explaining why you were denied. For me I think it is the APP URL, yet they don't explain, it is so frustrating.
Did you try email api#soundcloud.com on my first rejection they were very friendly and replied with advice, however second time they did not.
You can also try calling help on +4930467247600 however they have not worked for me.
Lastly I read online that one person heard nothing from them for weeks and checked his SoundCloud developer page under 'YOUR APPS' and his app was there set up and with the client id and secret etc. He was just never informed that he got it. So hopefully that is the story in your case.
For me it took four weeks. I contacted them via Twitter and Email. They responded but all they said was:
"As mentioned previously, we’re currently working through applications
as quickly as possible, although there has recently been more requests
than usual lately causing delays.
You should receive confirmation soon though."

Some accounts in instagram API are not working properly with realtime

I believe this to be a bug and hopefully someone from facebook or instagram can confirm.
I am working with the real-time API from Instagram. I have one subscription which is working fine and my callbacks are working as intended. Images are been projected as they should.
The problem is that not all of the accounts work. For example i got an account xxx1 and xxx2 that take a picture and use the tag 'somethingnew', I am subscribed to this tag, they take a picture and it is not projected. In fact the callback url is not even getting information. Then I use an account xxx3 which I just created and everything works as it should; in real time. Since I query from last tag taken I get the pictures that account xxx1 and xxx2 took.
Any ideas? Is it a bug?
First check your subscription are taken into account using the following API:
https://api.instagram.com/v1/subscriptions?client_secret=xxx&client_id=xxx
Note that it's a common problem to get an error on subscription. There are plenty of AWS servers answering to that API and some are not working. Ping api.instagram.com and you'll see you get multiple and different IP for that domain name. There is a DNS round robin and you are not reaching the same server every time.
I've found one server (IP) which seems to be working for subscription and have configured my server to use that one (by editing the /etc/hosts file). Not a reliable solution ... but it's working.
Then, note also that "real time" is not really "real time". You could receive a callback request for a picture posted several minutes (and sometimes a couple of hours) ago. That's weird ... but we've to live with that.
I've already open tickets for all these problems but got no answer from Instagram.