How can we help you?

How do I set up my Job Board URLs?

Greenhouse generates unique links to each of your live job posts. These links are added to your job board and will redirect candidates to the application form for a specific job. For Greenhouse to successfully link to the careers page on your website, you’ll first need to configure your URLs within your Greenhouse account.

How do I set up my Job Board and Job Post URLs in Greenhouse?

To configure your Job Board URLs in Greenhouse, navigate to your  Configure Job Board page. Here, you’ll see two URL fields: the Job Board URL field and the Job Posts URL field.


The Job Board URL will be the URL for your job board (your list of open jobs). For example, the URL to a list of jobs for may look like this: 


In the above configuration, Greenhouse would set the URLs to your job board to be, so that if you were to post that URL on an external site (e.g. Glassdoor or Indeed), candidates clicking that link would be taken to your job board at that URL.

The Job Posts URL is the URL to individual job posts (the job description and application form). This URL needs to have a specific structure in order to link properly to your job posts. There are two main elements that need to be included in this URL:

  1. The Base URL (e.g. “”)
  2. The Job ID

The Base URL will be the same for all of your job posts. The only difference between the URLs for different job posts should be the job’s unique Job ID.

Greenhouse will automatically add the Job ID to the Base URL entered in the Job Posts URL field. If there is no URL configured in the Job Posts URL field, Greenhouse will construct your Job Posts URL by appending the Job ID to the URL entered in the Job Board URL field.  

For example, if you only had the Job Board URL configured and you left the Job Post URL field blank, Greenhouse would generate the link to the job board as Greenhouse would generate the URL to your job posts by adding the Job ID to that URL with a parameter called “gh_jid=”. For example, the full job post URL for a job with ID “130142” would look like this: “”.   

It’s also possible to configure your Job Posts URL to use a different Base URL than the one configured in the Job Board URL field. For example, if you want your job board to live on the URL, but you want your job posts to use the Base URL, you would configure that by adding the Job Posts URL to the Configure Job Board page:


With this configuration, the URL for a job with ID “130142” would look like this:

You can also include the Job ID a second time in the URL by adding the text “:id” to the Job Posts URL. For example, to include the ID of the job in another place in the URL, add the text “:id” where you’d like the job ID to appear in the URL.



With this configuration, the URL for a job with ID “130142” would look like this:  

Is it possible to use a more customized Job Posts URL?

To work properly with Greenhouse, your URLs need to follow the convention of using a Base URL plus the Job ID. This means that you can configure whatever Base URL you would like, but that URL needs to be the same across all job posts. Greenhouse will automatically append the Job ID to that URL.

For example, if you had a highly customized URL that included a job’s department and name (e.g., that URL would not be configurable in Greenhouse. As Greenhouse can only generate new job post URLs by adding the Job ID to one standard Base URL, it would not be possible for Greenhouse to automatically generate links that include other details specific to the job, such as the job’s name or department.

If you notice that your Greenhouse links aren’t pointing to the right location, please make sure that the links on your careers page match the Greenhouse-supported URL format. If your URLs contain textual information that is specific to the job, Greenhouse will not be able to link to that URL directly.

Are there any workarounds?

Greenhouse won’t be able to link automatically to URLs that use an unsupported format, but it may be possible for your developers to set up a redirect from the Greenhouse-supported URLs to the URLs on your careers page.

For example, if the URL for your job post in Greenhouse is, but you’d prefer for it to be, your developers would need to set up a redirect from the Greenhouse URL to the URL on your careers page. With a redirect in place, when candidates click the Greenhouse URL, they should automatically be redirected to the URL on your careers page.

There are some things to be aware of if you’d like to take the redirect approach:

  1. Maintenance: When you post a new job in Greenhouse, we’ll automatically create a URL for that job and add it to your job board. However, if you’d like to set up a redirect for all of your URLs, you would need to create a new redirect path for all new jobs posts in your account.

    For example, once you created a new job post, Greenhouse would automatically create the link to the post using the supported format (e.g. If this link is different from the link on your careers page (e.g., the links generated in Greenhouse wouldn’t work until your developers set up a redirect from the Greenhouse link ( to your careers page link (
  2. Source tracking: Greenhouse tracks candidates’ sources through a source token parameter that we append to your job board URL and job posts URL. The format of that parameter us “gh_src=”. When the candidate applies on a page that includes the source token in the URL path, we’ll recognize the token and will to attribute the candidate to a specific source in Greenhouse.

    Here’s an example of a tracking link from Greenhouse that includes the candidate’s source token: In order for Greenhouse to track the candidate’s source, that token needs to be present in the URL of the application page when the candidate applies.

    This means that you would need to maintain the source token when the page redirects from the Greenhouse-supported URL to the URL on your careers page. For example, to effectively track the source of the candidate who began on the above link, your page would need to redirect to the correct URL while keeping the source token intact:

Please reach out to with any questions!