BeenVerified User Flow & Java Library

[Jason Amster]

Questions:

1. After a user authorizes an application with one or more pieces of
information, what does the application need to do to receive the same
information back in future?
2. Are you planning to release code in Java as well? I need a java
library.

Answers:
Once a user authorizes the Consumer application (your app), they get
redirected to your callback URL (the one your registered with us when
you signed up for your API key) with an oauth_token parameter. Your
callback URL should handle the back-end processing of exchanging that
oauth (request) token with the access token. This second (access)
token & secret you receive should be stored in your database and
linked to the user.

Once this occurs, you need to send signed OAuth requests to the API
end points using your consumer key and secret as well as the access
token and secret. The response you get will be based upon the user’s
authorization level.

This all requires a bit of understanding from the OAuth standpoint.
So, if you need any help wrapping your head around that a bit more
let's keep this dialogue going. I also highly suggest reading the
OAuth spec a few times (http://oauth.net/core/1.0/). It’s not too
long.

As far as a Java library, I don’t have the developer resources right
now to get one up and running but we are looking for any help in that
area. The next best thing would be for you to open up the OAuth Java
library which can be found here:

http://oauth.googlecode.com/svn/code/java/core/
http://oauth.googlecode.com/svn/code/java/example/

From that you should be able to build the necessary calls without
having to do much work in the OAuth realm. Our Ruby and PHP libraries
will just be wrappers around the already existing OAuth libraries as
well so it would follow the same pattern.

We are encouraging our developers to also write libraries and share
them with the community as well so if you make any headway with a Java
library, I'll be happy to publish your code in our code library on
BeenVerified.com. Otherwise we’ll be publishing it on our own in the
future.