Indeed API

Documentation contains content from the official LinkedIn Documentation. Credit goes to LinkedIn.

Demo: https://razorpay.bubbleapps.io/indeed

LinkedIn Application Page: https://secure.indeed.com/account/apikeys

Get a Client ID and Secret

Your client ID and secret identify your application. These are also called API keys or API credentials. You only need to get these once for your app.

One-time Steps

  1. Navigate to the Indeed Application Registration page.

  2. Log in to your Indeed account.

  3. Click the Register new application button.

  4. Enter your Application Name. For example, Ace Recruiters LLC.

  5. Select OAuth 2.0.

  6. Client Credentials.

  7. Click the Register button.

  8. The page displays the Client ID and Client Secret generated for your application.

Update Your Application Registration

  • Go to the Indeed Application Registration page, and review your application’s information

  • Make sure you add at least one redirect URL. A redirect URL is a page on your website where Indeed redirects a user after attempting to authorize the user. If authorization is successful, then we pass an authorization code to your redirect URL. If you would like to test your OAuth application on your local machine, you can set one of your redirect URLs to http://localhost.

Request an Authorization Code

Use the workflow Indeed - Authenticate to redirect your Users to the Indeed Authentication page. Make sure you fill in all the required details.

Workflow is executed by Bubble on a server-side level, data is not being exposed on the Client Side.

Receive the Authorization Code

  • The user clicks on the authorization link and logs in to Indeed’s site.

  • The OAuth consent page asks the user to give your application access.

  • We redirect the user to your redirect_uri with the following parameters appended:

Name

Description

Example

code

The authorization code. It is valid for 10 minutes.

rXZSMNyYQHQ

state

An optional value that is returned only if you pass it in the request.

employer1234

Random Tips & Tricks

  • When using 3-legged-auth make sure to pass in offline_access scope and email to retrieve the User's email along with a refresh token

  • Tokens expire after one hour, make sure you refresh the token using a refresh token or by redirecting the user back to LinkedIn if you don't wish to work with offline_access

  • The plugin also supports 2-legged-auth, checkout the demo editor to see how I have configured an easy approach of handling it, make sure you pass in the scope employer_access should you need it

  • In the 2-legged auth flow, your application acts only on behalf of the Indeed account that registered your app and obtained the client ID and secret. That means you're not interacting with other user's LinkedIn accounts.