Introduction
This is a quick tutorial to help you make signed 2-legged OAuth 1.0 request using Apigee Console. This is a really convenient way to help you jump start development. You won't have to write any code, and you get very good visibility of your request (as it is sent to Factual) and a cleanly formatted version of the JSON response.
Specify your request
- Go to the Apigee console set up to work with Factual.
- Enter your request into the provided text input:
Provide your OAuth credentials
- Click on the lock icon
- select OAuth from the drop down menu
- Enter your Factual API Key and Factual API Secret into the provided inputs
- If you don't have a Factual API Key or Factual API Secret yet, you can get your API key here.
- Click OK
Send your request
- Click on the "GET" button
- You should see your response under the Response tab.
 | Be careful with ampersands... Very conveniently, Apigee will handle URL encoding for you in most cases. However, if you have a filters parameter with an ampersand in it, there's no way for Apigee to know if the ampersand was intended to be part of your filters param or the start of another GET param. For example: In this case, you'll need to properly URL encode the value being passed into filters first. You'll end up with: A helpful resource for doing your encoding is: http://meyerweb.com/eric/tools/dencoder/.` |