-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 1002: Parameter has invalid value #6
Comments
@simon1tan, you might want to blank out your other key.… |
I'm having the same issue. It looks like the Bing API may have changed. |
thanks for pointing out the other key :) |
Yes, from the Bing API docs: AuthenticationWhy don't I need to specify an application ID?The Bing Search API 2.0 used an application ID to authenticate a Bing Search API request. With Windows Azure Marketplace, you must obtain an account key instead. The account key replaces the application ID as the mode of authentication. |
@sdball, even so, when using a newly acquired account key, the 1002 error still occurs. Basically, the Bing API 2.0 is not compatible with the new API. In order to do Bing searches, the gem needs to be modified to use the new Microsoft Azure Marketplace Bing API. |
having the same problem too, even when using my account key. any hint? |
I'm having the same issue with the newly acquired account key also! |
You can find a very basic example of how you can work directly with Bing Search new API in Ruby here -> https://gist.github.com/Sam-Serpoosh/6605527! Hope that helps! Hopefully I'll get some time to do a pull request on this gem soon! |
I am getting an error "Errors"=>[{"Code"=>1002, "Message"=>"Parameter has invalid value.", "Parameter"=>"SearchRequest.AppId", "Value"=>"--------------------------", "HelpUrl"=>"http://msdn.microsoft.com/en-us/library/dd251042.aspx"}] ", key blanked out. Any ideas?
My code is just like the example given.
require 'rubygems'
require 'rbing'
bing = RBing.new('aaaaaaaaaaaaaaaaaaaaaaaaaaa')
rsp = bing.web("tommy lee jones")
p rsp
The text was updated successfully, but these errors were encountered: