Guide to Business Intelligence Connector – Greenhouse Support

Permissions: —

Product tier: Available to Expert subscription tier

Business Intelligence Connector delivers a daily ETL of your organization's Greenhouse Recruiting and Greenhouse Onboarding data, dating from the time of your environment's creation. The data is comprehensive. This article provides a guide to the data, with a brief description of each table and what each row represents, as well as what to expect for each column.

Tip: Use your browser's Find feature (CMD + F on Mac | CTRL + F on Windows) to search for the data point you're interested in, like "custom candidate fields."

Application data

The applications table

The applications table represents a snapshot of application data. Each row represents the latest status of a single application.

Note: This table doesn't contain any historical records.

Column	What to know
`id`	The application ID. This appears as `application_id` on other tables.
`candidate_id`	The candidate ID.
`coordinator`	The coordinator's name.
`coordinator_id`	The candidate's coordinator's ID. A candidate might not have the same coordinator assigned to the hiring team of the candidate's job if their application has been added to another job or if their profile has been merged.
`applied_at`	The date and time the candidate applied, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`status`	The application's current status and is one of `active`, `converted`, `rejected`, or `hired`. Converted applications represent prospect applications that were converted to candidate applications.
`prospect`	Boolean. Results are either `true` or `false`, indicating whether the application is for a prospect.
`stage_id`	The stage ID of the application.
`source_id`	The source ID for the application.
`recruiter`	The recruiter's name.
`recruiter_id`	The candidate's recruiter's ID. A candidate might not have the same recruiter assigned to the hiring team of the candidate's job if their application has been added to another job or if their profile has been merged.
`referrer_id`	The referrer ID for the application. This appears as 'Who Gets Credit' on the application under Details > Source & Responsibility.
`rejected_at`	The date and time the application was rejected, if applicable, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`rejected_by_id`	The user ID of the person who rejected the application, if applicable.
`rejection_reason_id`	The rejection reason ID for a rejected application, if applicable.
`pipeline_percent`	The percentage that an application has advanced through a job's stages, not including the application's current stage. For an application in a job's first stage, the pipeline percent is `0`. For an application in a job's last stage, the pipeline percent is `{number of stages} - 1 / {number of stages}`. For a hired application, the pipeline percent is `[NULL]`. For prospects, the pipeline percent is `0`.
`migrated`	Boolean. Results are either `true` or `false`, indicating whether the application was migrated from a different ATS.
`rejected_by`	The name of the Greenhouse Recruiting user who rejected the application, if applicable.
`stage_name`	The application's current stage name.
`job_post_id`	The job post ID associated with the application.
`prospect_pool`	The name of the prospect pool, for prospect applications.
`prospect_pool_stage`	The current prospect pool stage, for prospect applications.
`prospect_owner_id`	The Greenhouse Recruiting user who owns the prospect pool, for prospect applications, if applicable.
`created_at`	The date and time the application was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The last time the application was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`event_id`	The event ID associated with a prospect application, if applicable.
`converted_prospect_application_id`	This represents a converted prospect application ID for applications that were converted from prospects.
`sent_demographic_questions`	Boolean. Results are either `true` or `false`, indicating whether the application was sent demographic questions.
`organization_id`	Your organization's unique Greenhouse Recruiting organization ID.

The application custom fields table

The application_custom_fields table represents custom application fields associated with an application. Each row represents a single value of a single custom field for a single application.

Column	What to know
`application_id`	The application ID.
`custom_field`	The custom application field name.
`float_value`	These are number values entered in the custom application field, if applicable.
`date_value`	The date entered in the custom application field, if applicable.
`display_value`	How the custom application field value appears on the candidate profile.
`unit`	The currency type entered in the custom application field, if applicable.
`min_value`	This column isn't used here, so a `NULL` value is shown.
`max_value`	This column isn't used here, so a `NULL` value is shown.
`user_id`	The Greenhouse Recruiting user ID for custom application fields with user field types.
`created_at`	The date and time the custom application field was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom application field was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom application field.
`text_value`	The text value as it appears on the application's custom application field.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The application question answers table

The application_question_answers table represents questions and answers that candidates submitted in response to job posts with their applications. Each row represents a single job post application question and answer from a single application.

Column	What to know
`job_post_id`	The job post ID.
`application_id`	The application ID.
`question`	The application question from the job post.
`answer`	The applicant's answer to the application question.
`created_at`	The date the application was received, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date the application was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The application stages table

The application_stages table represents the historical activity of all stages an application has been on, as well as each stage that an application could be on, taken from the job stage setup. Each row represents a single stage that an application can be in and the timestamp that the application entered and exited the stage.

Note: Some applications may show rows for stages that an application has yet to reach, or will never reach if the application was rejected, in which case a NULL value is shown.

Column	What to know
`application_id`	The application ID.
`stage_id`	The stage ID.
`entered_on`	The date the application entered the stage, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC). Some applications may show rows for stages that an application has yet to reach, or will never reach if the application was rejected, in which case a `NULL` value is shown.
`exited_on`	The date the application exited the stage, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC). Some applications may show rows for stages that an application has yet to reach, or will never reach if the application was rejected, in which case a `NULL` value is shown.
`stage_name`	The job stage name.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The applications jobs table

The applications_jobs table represents applications for jobs. Each row represents one application to one job.

Column	What to know
`application_id`	The application ID.
`job_id`	The job ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The referral question custom fields table

The referral_question_custom_fields table represents custom referral questions associated with an application. Each row represents a single value of a single custom referral question for a single application.

Column	What to know
`candidate_id`	The candidate ID.
`custom_field`	The custom referral question.
`float_value`	These are numbers entered in the custom referral question answer, if applicable.
`date_value`	A date entered in the custom referral question answer, if applicable.
`display_value`	The candidate's response to the custom referral question as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom referral question answer, if applicable.
`min_value`	This column isn't used here, so a `NULL` value is shown.
`max_value`	This column isn't used here, so a `NULL` value is shown.
`user_id`	The Greenhouse Recruiting user ID for custom referral questions with user answer field types.
`created_at`	The date and time the custom referral question was answered, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom referral question answer was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom referral question.
`text_value`	The answer as it appears on the application's custom referral question.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The rejection question custom fields table

The rejection_question_custom_fields table represents custom rejection questions associated with an application. Each row represents a single value of a single custom rejection question for a single application.

Column	What to know
`application_id`	The application ID.
`custom_field`	The custom rejection question.
`float_value`	These are numbers entered in the custom rejection question answer, if applicable.
`date_value`	The date entered in the custom rejection question answer, if applicable.
`display_value`	The response to the custom rejection question as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom rejection question answer, if applicable.
`min_value`	This column isn't used here, so a `NULL` value is shown.
`max_value`	This column isn't used here, so a `NULL` value is shown.
`user_id`	The Greenhouse Recruiting user ID for custom rejection questions with user answer field types.
`created_at`	The date and time the custom rejection question was answered, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom rejection question answer was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom rejection question.
`text_value`	The answer as it appears on the application's custom rejection question.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The agency question custom fields table

The agency_question_custom_fields table represents custom agency questions associated with an application. Each row represents a single value of a single custom agency question for a single application.

Column	What to know
`application_id`	The application ID.
`custom_field`	The custom agency question.
`boolean_value`	Boolean. Results are either `true` or `false`, indicating whether the custom agency question is a yes / no question.
`float_value`	These are numbers entered in the custom agency question answer, if applicable.
`date_value`	The date entered in the custom agency question answer, if applicable.
`display_value`	The response to the custom agency question as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom rejection question answer, if applicable.
`min_value`	This column isn't used here, so a `NULL` value is shown.
`max_value`	This column isn't used here, so a `NULL` value is shown.
`user_id`	This column isn't used here, so a `NULL` value is shown.
`created_at`	The date and time the custom agency question was answered, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom agency question answer was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom rejection question.
`text_value`	The answer as it appears on the application's custom rejection question.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Candidate data

The candidates table

The candidates table represents a snapshot of candidate data. Each row represents a single candidate. A candidate is a person. A candidate may have multiple applications for multiple jobs.

Column	What to know
`id`	The candidate ID. This appears as `candidate_id` on other tables.
`first_name`	The candidate's first name.
`last_name`	The candidate's last name.
`preferred_name`	The candidate's preferred name.
`migrated`	Boolean. Results are either `true` or `false`, indicating whether the candidate was migrated from a previous ATS.
`company`	The candidate's current company, if applicable.
`title`	The candidate's current title, if applicable.
`created_at`	The date and time the candidate was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the candidate was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`private`	Boolean. Results are either `true` or `false`, indicating whether the candidate is private.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The candidate custom fields table

The candidate_custom_fields table represents custom candidate fields associated with a candidate. Each row represents a single value of a single custom field for a single candidate.

Column	What to know
`candidate_id`	The candidate ID.
`custom_field`	The custom candidate field.
`float_value`	These are numbers entered in the custom candidate field, if applicable.
`date_value`	The date entered in the custom candidate field, if applicable.
`display_value`	The value entered into the custom candidate field as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom candidate field, if applicable.
`min_value`	This column isn't used here, so a `NULL` value is shown.
`max_value`	This column isn't used here, so a `NULL` value is shown.
`user_id`	The Greenhouse Recruiting user ID entered for custom candidate fields with user field types.
`created_at`	The date and time the custom candidate field value was entered, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom candidate field value was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom candidate field.
`text_value`	The answer as it appears on the application's custom candidate field.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The candidate tags table

The candidate_tags table represents all candidate tags associated with a candidate. Each row represents a single tag on a single candidate.

Column	What to know
`candidate_id`	The candidate ID.
`tag_id`	The candidate tag ID.
`created_at`	The date and time the candidate tag was created for the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the candidate tag was updated on the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The educations table

The educations table represents all structured education fields associated with a candidate. Each row represents a single structured education for a single candidate.

Note: Data is only collected in this table when education is added to candidate profiles in a structured method in Greenhouse Recruiting.

Column	What to know
`candidate_id`	The candidate ID.
`school_name`	The school name associated with the candidate.
`degree`	The degree associated with the candidate.
`discipline`	The school discipline associated with the candidate.
`start`	The date the candidate started the education, if applicable, like`2024-01-01`.
`end`	The date the candidate ended the education, if applicable, like`2024-01-01`.
`latest`	Boolean. Results are either `true` or `false`, indicating whether the education is the latest the candidate has experienced.
`created_at`	The date and time the education was associated with the candidate profile, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the education for the candidate profile was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The employments table

The employments table represents all structured employment fields associated with a candidate. Each row represents a single structured employment record for a single candidate.

Note: Data is only collected in this table when employment is added to candidate profiles in a structured method in Greenhouse Recruiting.

Column	What to know
`candidate_id`	The candidate ID.
`company_name`	The company name associated with the candidate.
`title`	The title associated with the candidate.
`start`	The date the candidate started the employment, if applicable, like`2024-01-01`.
`end`	The date the candidate ended the employment, if applicable, like`2024-01-01`.
`latest`	Boolean. Results are either `true` or `false`, indicating whether the employment is the latest the candidate has experienced.
`created_at`	The date and time the employment was associated with the candidate profile, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the employment for the candidate profile was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Candidate PII data

The candidate email addresses table

The candidate_email_addresses table represents a list of email addresses by candidate. Each row represents a single email address and the associated candidate.

Note: This table is opt-in only. You can enable this table in your ETL.

Column	What to know
`candidate_id`	The candidate ID.
`value`	The candidate's email address.
`created_at`	The date and time the email address was associated with the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the email address for the candidate was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The candidate mailing addresses table

The candidate_mailing_addresses table represents a list of mailing addresses by candidate. Each row represents a single mailing address and the associated candidate.

Note: This table is opt-in only. You can enable this table in your ETL.

Column	What to know
`candidate_id`	The candidate ID.
`value`	The candidate's mailing address.
`created_at`	The date and time the mailing address was associated with the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the mailing address for the candidate was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The candidate phone numbers table

The candidate_phone_numbers table represents a list of phone numbers by candidate. Each row represents a single phone number and the associated candidate.

Note: This table is opt-in only. You can enable this table in your ETL.

Column	What to know
`candidate_id`	The candidate ID.
`value`	The candidate's phone number.
`created_at`	The date and time the phone number was associated with the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the phone number for the candidate was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Demographic data

The demographic answers table

The demographic_answers table represents responses to U.S. standard or custom demographic questions. Each row represents a single application's response to a custom demographic question. You can join this table with the demographic questions and demographic answer options table.

Note: This table doesn't contain EEOC responses. Custom demographic questions are only available to Expert subscription tier.

Column	What to know
`id`	The demographic question answer ID.
`application_id`	The application ID.
`demographic_question_id`	The demographic question ID.
`demographic_answer_option_id`	The demographic question answer option ID.
`created_at`	The date and time the demographic answer was associated with the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the demographic answer for the candidate was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The demographic answer options table

The demographic_answer_options table represents answer options to U.S. standard or custom demographic questions. Each row represents a single custom demographic question answer option. You can join this table with the demographic questions and demographic answers table.

Note: This table doesn't contain EEOC responses. Custom demographic questions are only available to Expert subscription tier.

Column	What to know
`id`	The demographic question answer option ID.
`demographic_question_id`	The demographic question ID.
`active`	Boolean. Results are either `true` or `false`, indicating whether the demographic answer option is currently active.
`free_form`	Boolean. Results are either `true` or `false`, indicating whether the answer option allows for free-text answers.
`name`	The demographic question answer option.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The demographic answer option translations table

The demographic_answer_option_translations table represents translated answer options to U.S. standard or custom demographic questions. Each row represents a single translated custom demographic question answer option. You can join this table with the demographic questions and demographic answers table.

Note: This table has been deprecated. Only English en is currently supported. Custom demographic questions are only available to Expert subscription tier.

Column	What to know
`id`	The demographic question answer option ID.
`demographic_answer_option_id`	The demographic question answer option ID.
`language`	The demographic question answer option language. This table has been deprecated. Only English `en` is currently supported.
`name`	The demographic question answer option.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The demographic free form answers table

The demographic_free_form_answers table represents free-text answer options to U.S. standard or custom demographic questions. Each row represents a single application's response to free-text custom demographic questions. You can join this table with the demographic questions and demographic answers table.

Note: This table doesn't contain EEOC responses. Custom demographic questions are only available to Expert subscription tier.

Column	What to know
`id`	The demographic free form answer ID.
`demographic_answer_id`	The demographic answer ID.
`text`	The free-text answer from the candidate.
`created_at`	The date and time the demographic answer was associated with the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the demographic answer for the candidate was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The demographic questions table

The demographic_questions table represents U.S. standard or custom demographic questions. Each row represents a single U.S. standard or custom demographic question. You can join this table with the demographic answers and demographic questions table.

Note: This table doesn't contain EEOC responses. Custom demographic questions are only available to Expert subscription tier.

Column	What to know
`id`	The demographic question ID. This appears in other tables as `demographic_question_id`.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`active`	Boolean. Results are either `true` or `false`, indicating whether the demographic question is currently active.
`demographic_question_set_id`	The demographic question set ID. An organization can have multiple demographic question sets.
`name`	The text of the demographic question as it appears in Greenhouse Recruiting.
`required`	Boolean. Results are either `true` or `false`, indicating whether the demographic question is required.
`answer_type`	The answer type and is one of `Single select` or `Multi select`.

The demographic question set table

The demographic_question_sets table represents U.S. standard or custom demographic question sets. Each row represents a single group of custom demographic questions. You can join this table with the demographic answers and demographic questions table.

Note: This table doesn't contain EEOC responses. Custom demographic questions are only available to Expert subscription tier.

Column	What to know
`id`	The demographic question set ID. This appears in other tables as `demographic_question_set_id`.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`title`	The demographic question set title, as shown in Greenhouse Recruiting.
`description`	The demographic question set description, as shown in Greenhouse Recruiting.
`active`	Boolean. Results are either `true` or `false`, indicating whether the demographic question is currently active.

The demographic question translations table

The demographic_question_translations table represents translated U.S. standard or custom demographic questions. Each row represents a single translated custom demographic question. You can join this table with the demographic questions and demographic answers table.

Note: This table has been deprecated. Only English en is currently supported.

Custom demographic questions are only available to Expert subscription tier.

Column	What to know
`id`	The demographic question ID.
`demographic_answer_option_id`	The demographic question ID.
`language`	The demographic question answer option language. This table has been deprecated. Only English `en` is currently supported.
`name`	The text of the demographic question as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The EEOC responses table

The eeoc_responses table represents responses to EEOC questions. Each row represents a single application's responses to EEOC questions.

Note: Data is only collected in this table when a candidate responds to EEOC questions on an application, or when a request is sent to a candidate to respond to EEOC questions. Data isn't collected for candidates who didn't respond to questions on the job post or didn't receive a request to respond to the questions afterward.

Column	What to know
`application_id`	The application ID.
`status`	The EEOC response status and is one of `responded` or `pending response`.
`race`	The application response to the EEOC questions `Are you Hispanic/Latino?` and `Please identify your race`.
`gender`	The application response to the EEOC question `Gender`.
`disability_status`	The application response to the EEOC question `Disability Status`.
`veteran_status`	The application response to the EEOC question `Veteran Status`.
`submitted_at`	The date and time the EEOC response was submitted, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Greenhouse Onboarding data

Note: Greenhouse Onboarding data is opt-in only and is only available to Greenhouse Onboarding subscribers.

The Greenhouse Onboarding assigned tasks table

The gho_assigned_tasks table represents a list of assigned tasks from Greenhouse Onboarding. Each row represents a single assigned task and the associated Greenhouse Onboarding employee.

Column	What to know
`id`	The task ID.
`task_name`	The task name.
`task_description`	The task description.
`task_category`	The task category and is one of `Build Relationships`, `Job Training`, `Know the Company`, or `Logistics`.
`assigned_for_id`	The ID of the person to whom the task was assigned.
`assigned_by_id`	The ID of the person who assigned the task.
`completed_at`	The date and time the task was completed, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`due_date_relative_days`	The number of days before or after the employee's start date that the task was due, if applicable.
`assign_days_before`	The number of days before the employee's start date that the task was due.
`calculated_due_date`	The calculated due date for the task based on the new hire's start date, like `2024-01-31`.
`calculated_assign_date`	The calculated due date for the task based on the new hire's start date, like `2024-01-31`.
`attachment_required`	Boolean. Results are either `true` or `false`, indicating whether the task requires an attachment.
`created_at`	The date and time the task was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the task was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`assigned_employee_id`	The ID of the person assigned to complete the task.
`third_party_system_email`	The system email ID, if you're using a third-party system for a task.
`assigned_custom_field_id`	The custom field assigned to complete the task.
`assigned_coworker_employee_id`	The coworker employee ID assigned to complete the task.
`completed_by_employee_id`	The ID of the person who completed the task.
`completed_by_third_party_system`	The third-party task system that completed the task, if applicable.
`assignee_updated_at`	The date and time the task assignee was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`assigned_at`	The date and time the task was assigned, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`company_id`	Your organization's unique Greenhouse Onboarding ID.

The Greenhouse Onboarding custom fields table

The gho_custom_fields table represents a list of your custom fields in Greenhouse Onboarding. Each row represents a single Greenhouse Onboarding custom field.

Column	What to know
`id`	The custom field ID.
`permanent_field_id`	The permanent field ID.
`name`	The custom field name as it appears in Greenhouse Onboarding.
`field_type`	The field type and is one of `text`, `long_text`, `multiple_choice`, `multiple_select`, `contact`, `team`, `date`, `employee`, `address`, `legal_name`, `preferred_name`, `image`, `country`, or `masked`.
`created_at`	The date and time the custom field was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom field was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`company_id`	Your organization's unique Greenhouse Onboarding ID.

The Greenhouse Onboarding custom field values table

The gho_custom_field_values table represents a list of available values associated with employees from your custom fields in Greenhouse Onboarding. Each row represents a single Greenhouse Onboarding custom field value and the associated employee.

Column	What to know
`id`	The custom field value ID.
`employee_id`	The employee ID.
`custom_field_id`	The custom field ID.
`custom_field_permanent_field_id`	The custom field's permanent field ID.
`custom_field_field_type`	The custom field type and is one of `text`, `long_text`, `multiple_choice`, `multiple_select`, `contact`, `team`, `date`, `employee`, `address`, `legal_name`, `preferred_name`, `image`, `country`, or `masked`.
`value`	The value entered on the employee's profile for the custom field.
`value_date`	The date entered in the custom field, if applicable.
`created_at`	The date and time the custom field was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom field was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`company_id`	Your organization's unique Greenhouse Onboarding ID.

The Greenhouse Onboarding employees table

The gho_employees table represents a list of employees in Greenhouse Onboarding. Each row represents a single Greenhouse Onboarding employee.

Column	What to know
`id`	The employee ID.
`created_at`	The date and time the employee profile was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the employee profile was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`personal_email`	The employee's personal email address.
`work_email`	The employee's work email address.
`start_date`	The employee's start date, like `2024-01-31`.
`termination_date`	The employee's termination date, like `2024-01-31`, if applicable.
`employment_status`	The employee's employment status, like `full_time`.
`manager_id`	The employee's manager's ID.
`hr_manager_id`	The employee's HR manager's ID.
`title`	The employee's job title.
`global_role`	The employee's role and is one of `owner`, `coordinator`, or `employee`.
`n_direct_reports`	The number of the employee's direct reports.
`department`	The employee's office.
`location`	The employee's location.
`legal_name_first_name`	The employee's legal first name.
`legal_name_middle_name`	The employee's legal last name.
`legal_name_last_name`	The employee's legal middle name.
`legal_name_suffix`	The employee's legal name suffix.
`preferred_first_name`	The employee's preferred first name.
`preferred_last_name`	The employee's preferred last name.
`company_id`	Your organization's unique Greenhouse Onboarding ID.

The Greenhouse Onboarding employee roles table

The gho_employee_roles table represents a list of employee roles in Greenhouse Onboarding. Each row represents a single Greenhouse Onboarding role and the associated Greenhouse Onboarding employee.

Column	What to know
`role_id`	The employee's role ID. This ID comes from the `gho_roles` table.
`employee_id`	The employee ID.
`company_id`	Your organization's unique Greenhouse Onboarding ID.

The Greenhouse Onboarding roles table

The gho_roles table represents a list of roles in Greenhouse Onboarding. Each row represents a single Greenhouse Onboarding role.

Column	What to know
`id`	The role ID.
`name`	The name of the role as it appears in Greenhouse Onboarding.
`company_id`	Your organization's unique Greenhouse Onboarding ID.

The Greenhouse Onboarding user activities table

The gho_user_activities table represents a list of all user activities in Greenhouse Onboarding. Each row represents a single activity from Greenhouse Onboarding and the associated employee.

Column	What to know
`employee_id`	The employee ID.
`hourly_last_sign_in_at`	The date and time the employee last signed in, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`company_id`	Your organization's unique Greenhouse Onboarding ID.

Greenhouse Sourcing Automation (GHSA) data

Greenhouse Sourcing Automation (GHSA) data helps subscribers analyze how their team connects with and converts prospects.

The GHSA actions table

The gsha_actions table captures each interaction a prospect has with your outreach. You can also distinguish between manual and AI-assigned sentiments like interested or bad fit.

Column	What to know
`id`	The GHSA action ID.
`application_id`	The application’s ID.
`campaign_detail_id`	The campaign detail's ID.
`verb`	The type of action was taken on the prospect: `viewed` , `visited` , `replied`, `messaged` , `booked`, `bounced`, `unsubscribed` , `reply_removed` , `booked_removed`, `sentiment_updated`, `sentiment_removed`
`created_at`	The date and time the tag was created for the prospect, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`manual_user_id`	The Greenhouse Recruiting user ID for custom application fields with user field types.
`auto_assigned`	Boolean. Results are either true or false. True indicates that a sentiment has been auto-assigned to a prospect.
`sentiment`	The sentiment assigned to a prospect: `interested`, `not interested`, `bad fit`, `wrong contact`, `timing`, `bad data`
`organization_id`	Your organization's unique Greenhouse Recruiting organization ID.

The GHSA campaign pool performance table

The gsha_campaign_pools table breaks down the structure, type (engage or nurture), and timing of your campaigns. You can also track which users created and managed each campaign pool.

Column	What to know
`id`	The GHSA campaign pool ID.
`prospect_pool_id`	The GHSA prospect pool ID.
`campaign_detail_id`	The GHSA campaign pool ID.
`user_id`	The Greenhouse Recruiting user ID for GHSA campaign pools.
`campaign_type`	Your campaign type: `nurture` or `engage`
`created_at`	The date and time the campaign pool was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the campaign pool was updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting organization ID.

The GHSA message activity table

Understand your delivery and engagement metrics using the ghsa_messages table. This table includes timestamps for when a message was sent, viewed, replied to, or clicked, which gives you visibility into every step of a prospect’s journey.

Column	What to know
`id`	The Greenhouse Recruiting user ID for GHSA messages.
`campaign_step_id`	The campaign step’s ID.
`campaign_detail_id`	The GHSA campaign pool ID.
`application_id`	The application’s ID.
`requires_personalization`	Indicates that a GHSA message requires personalization.
`created_at`	The date and time the message l was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`sent_at`	The date and time the message was sent to the prospect, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`viewed_at`	The date and time the message was viewed by the prosepect, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`visited_at`	The date and time a link in the message was visited by the prospect, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC). If the message doesn't have a `viewed_at` value when the prospect clicks this link, `viewed_at` will inherit the `visited_at` date and time.
`replied_at`	The date and time the prospect replied to a message, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC). If the message doesn't have a `viewed_at` value when the prospect replies to the message, `viewed_at` will inherit the `replied_at` date and time.
`organization_id`	Your organization's unique Greenhouse Recruiting organization ID.

The GHSA outreach steps table

The ghsa_campaign_steps table allows you to audit campaign design. See subject lines, message content, delays between steps, and whether a step used personalization, AI contribution, or a Gmail aliases.

Column	What to know
`id`	The Greenhouse Recruiting user ID for campaign steps.
`campaign_detail_id`	The GHSA campaign detail ID.
`step_number`	Where a selected step appears in a campaign’s sequence of steps: 1, 2, 3 etc.
`sent_on_behalf_of_user_id`	The step sender’s ID, if different from the campaign owner.
`subject`	The campaign step’s message.
`wait_days`	The length of time your campaign pool will pause before automatically moving to the next step (note: 0 means 10 minutes)
`gmail_sent_as`	The name and address of the Gmail alias, if using.
`ai_contribution_status`	The status of an AI-generated step: `created` or `approved`
`requires_personalization`	Boolean. Results are either `true` or `false`. True indicates that step requires personalization.
`step_type`	The step type: `task` or `message`
`task_type`	The task type: `manual` or `inmail`
`organization_id`	Your organization's unique Greenhouse Recruiting organization ID.

The GHSA task table

The ghsa_tasks table helps monitor task-based steps like InMails or manual outreach. Track task types and completion timing to understand how work is distributed and executed across your team.

Column	What to know
`id`	The Greenhouse Recruiting task ID.
`campaign_step_id`	The GHSA task’s campaign step ID.
`campaign_detail_id`	The GHSA task’s campaign detail ID.
`application_id`	The GHSA task’s application ID.
`task_type`	The task type: `manual` or `inmail`
`complete_at`	The date and time a task was completed, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting organization ID.

The GHSA lookups table

Understand lookup activity with the ghsa_lookups table. See when your team searched for work or personal email addresses and whether a lookup was successful.

Column	What to know
`id`	The GHSA lookup’s ID.
`user_id`	The Greenhouse Recruiting user ID for GHSA lookups.
`lookup_type`	The type of lookup: `work` or `personal`
`campaign_detail_id`	The campaign detail’s ID.
`application_id`	The application's ID.
`created_at`	The date and time a lookup was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`successful`	Boolean. Results are either `true` or `false`. True indicates that a lookup was successful.
`organization_id`	Your organization's unique Greenhouse Recruiting organization ID.

Job data

The jobs table

The jobs table represents a list of jobs and their statuses in Greenhouse Recruiting. Each row represents the status of a single job.

Column	What to know
`id`	The job ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The job's internal name as it appears in Greenhouse Recruiting.
`requisition_id`	The job's requisition ID.
`status`	The job status and is one of `open`, `closed`, or `draft`.
`opened_at`	The date and time the job was opened, if applicable, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`closed_at`	The date and time the job was closed, if applicable, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`department_id`	The job's department ID.
`level`	The job's level.
`confidential`	Boolean. Results are either `true` or `false`, indicating whether the job is confidential.
`created_at`	The date and time the job was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`notes`	These are notes entered on the job.
`updated_at`	The date and time the job was updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`is_template`	Whether or not the associated job is a template job.

The job custom fields table

The job_custom_fields table represents custom job fields associated with a job. Each row represents a custom job field associated with a single job.

Column	What to know
`job_id`	The job ID.
`custom_field`	The custom job field name as it appears in Greenhouse Recruiting.
`float_value`	These are numbers entered in the custom job field, if applicable.
`date_value`	The date entered in the custom job field, if applicable.
`display_value`	The value entered into the custom job field as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom job field, if applicable.
`min_value`	The minimum value entered in the custom job field for number range and currency range field types.
`max_value`	The maximum value entered in the custom job field for number range and currency range field types.
`user_id`	The Greenhouse Recruiting user ID entered for custom job fields with user field types.
`created_at`	The date and time the custom job field value was associated with the job, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom job field value was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom job field.
`text_value`	The value entered on the custom job field as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The job snapshots table

The job_snapshots table represents a daily snapshot of job activity. Each row represents job-level metrics for a single day.

Column	What to know
`job_id`	The job ID.
`date`	The date of the snapshot, like `2024-01-31`.
`hired_count`	The count of new hires in the day.
`prospect_count`	The count of new prospects in the day.
`new_today`	The count of new applications in the day.
`rejected_today`	The count of rejected applications in the day.
`advanced_today`	The count of applications advanced in the day.
`interviews_today`	The count of interviews in the day.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The jobs attributes table

The jobs_attributes table represents a list of scorecard attributes on jobs. Each row represents a single scorecard attribute on a single job.

Column	What to know
`id`	The scorecard attribute ID.
`job_id`	The job ID.
`attribute_id`	The scorecard attribute ID.
`active`	Boolean. Results are either `true` or `false`, indicating whether the scorecard attribute is active.
`created_at`	The date and time the scorecard attribute was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the scorecard attribute was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`name`	The name of the scorecard attribute as it appears in Greenhouse Recruiting.
`category`	The category of the scorecard attribute as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The jobs departments table

The jobs_departments table represents a list of departments by job. Each row represents a single department on a single job. Tiered departments will show a row for each parent and child department a job is associated with.

Column	What to know
`id`	The primary key to this table.
`job_id`	The job ID.
`department_id`	The department ID associated with the job.
`created_at`	The date and time the department was associated with the job, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the department on the job was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The jobs interviews table

The jobs_interviews table represents a list of interviews by job. Each row represents a single interview on a single stage for a single job.

Column	What to know
`id`	The interview ID.
`job_id`	The job ID.
`stage_id`	The stage ID.
`interview_id`	The interview ID.
`order`	The order of the interview on a stage with multiple interviews.
`estimated_duration`	The estimated duration of the interview in minutes.
`created_at`	The date and time the interview was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the interview was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`interview_name`	The interview name as it appears in Greenhouse Recruiting.
`stage_name`	The stage name as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The jobs offices table

The jobs_offices table represents a list of offices by job. Each row represents a single office on a single job. Tiered offices will show a row for each parent and child office a job is associated with.

Column	What to know
`id`	The primary key to this table.
`job_id`	The job ID.
`office_id`	The office ID associated with the job.
`created_at`	The date and time the job was associated with the office, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the job's office was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The jobs posts table

The job_posts table represents a list of job posts by job. Each row represents details of a job post associated with a job.

Column	What to know
`id`	The job post ID.
`job_id`	The job ID.
`title`	The job post title.
`live`	Boolean. Results are either `true` or `false`, indicating whether the job post is live on your job board.
`job_board_name`	The job board name associated with the job post.
`language`	The language the job post was published in, like `en` for English.
`created_at`	The date and time the job post was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the job post was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`eeoc_enabled`	Boolean. Results are either `true` or `false`, indicating whether the job post includes EEOC questions.
`indeed_feed`	Boolean. Results are either `true` or `false`, indicating whether the job post was published on Indeed. This shows a `NULL` value for internal job posts.
`linked_in_feed`	Boolean. Results are either `true` or `false`, indicating whether the job post was published on LinkedIn.
`glassdoor_feed`	The Glassdoor free job post integration has been deprecated, so a `NULL` is shown.
`first_published`	The date and time the job post was first published, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The job post locations table

The job_post_locations table represents a list of job locations and their statuses in Greenhouse Recruiting. Each row represents the status of a single job.

Column	What to know
`id`	The job location ID.
`name`	The job location name as it appears in Greenhouse Recruiting.
`type`	The type of job location.
`job_post_id`	The job post ID.
`created_at`	The date and time the job post location was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the job post location was updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The job post questions table

The job_post_questions table represents a list of job post questions by job post. Each row represents a single job post question associated with a single job post.

Column	What to know
`job_post_id`	The job post ID.
`question`	The job post question.
`created_at`	The date and time the job post question was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the job post question was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The jobs stages table

The jobs_stages table represents a list of stages by job. Each row represents a single stage on a single job.

Column	What to know
`job_id`	The job ID.
`stage_id`	The stage ID.
`order`	The order the stage appears on the job.
`name`	The name of the stage as it appears in Greenhouse Recruiting.
`stage_alert_setting`	The number of days set for a stage alert setting, if applicable.
`created_at`	The date and time the job stage was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the job stage was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`milestones`	The milestone associated with the stage.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The hiring team table

The hiring_team table represents a list of hiring teams by job. Each row represents a single Greenhouse Recruiting user on a hiring team role on a single job.

Column	What to know
`job_id`	The job ID.
`user_id`	The user ID of the person associated with the hiring team role.
`role`	The hiring team role associated with the person.
`responsible`	Boolean. Results are either `true` or `false`, indicating whether the person holds a responsible role on the hiring team.
`created_at`	The date and time the hiring team role was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the hiring team role was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The openings table

The openings table represents a list of openings by job. Each row represents a single opening for a single job.

Column	What to know
`id`	The primary key to this table.
`job_id`	The job ID.
`opening_id`	The opening ID.
`opened_at`	The date and time the opening was opened, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`closed_at`	The date and time the opening was closed, if applicable, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`hired_application_id`	The hired application's ID, if applicable.
`close_reason`	The close reason selected, if applicable.
`created_at`	The date and time the opening was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the opening was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`target_start_date`	The opening's target start date.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`status`	Whether or not the job opening is currently active.

The opening custom fields table

The opening_custom_fields table represents a snapshot of custom opening fields. Each row represents a single value of a single custom opening field for a single opening.

Column	What to know
`opening_id`	The opening ID.
`custom_field`	The custom opening field.
`float_value`	These are numbers entered in the custom opening field, if applicable.
`date_value`	The date entered in the custom opening field, if applicable.
`display_value`	The value entered into the custom opening field as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom opening field, if applicable.
`min_value`	The minimum value entered in the custom opening field for number range and currency range field types.
`max_value`	The maximum value entered in the custom opening field for number range and currency range field types.
`user_id`	The Greenhouse Recruiting user ID entered for custom opening fields with user field types.
`created_at`	The date and time the custom opening field value was associated with the opening, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom opening field value was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom opening field.
`text_value`	The value entered on the custom opening field as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Offer data

The offers table

The offers table represents all offers. Each row represents the details of a single version of an offer for a single application. Each new version of an offer generates a new row of data.

Column	What to know
`id`	The offer ID.
`application_id`	The application ID.
`status`	The status of the offer and is one of `created`, `accepted`, `rejected`, or `deprecated`.
`created_at`	The date and time the offer was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`sent_at`	The date and time the offer was sent to the candidate, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`resolved_at`	The date and time the offer was accepted or rejected, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`start_date`	The date and time of the new hire's start date, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`created_by`	The Greenhouse Recruiting user who created the offer.
`updated_at`	The date and time the offer was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The offer custom fields table

The offer_custom_fields table represents all custom offer fields associated with an offer. Each row represents a single value of a single custom field for a single offer.

Column	What to know
`custom_field`	The custom offer field.
`float_value`	These are numbers entered in the custom offer field, if applicable.
`date_value`	The date entered in the custom offer field, if applicable.
`display_value`	The value entered into the custom offer field as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom offer field, if applicable.
`min_value`	The minimum value entered in the custom offer field for number range and currency range field types.
`max_value`	The maximum value entered in the custom offer field for number range and currency range field types.
`user_id`	The Greenhouse Recruiting user ID entered for custom offer fields with user field types.
`created_at`	The date and time the custom offer field value was associated with the offer, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom offer field value was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom offer field.
`text_value`	The value entered on the custom offer field as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`offer_id`	The unique identifier for the offer.

Organization data

The organizations table

The organizations table represents the name and ID of your organization. Each row represents a single organization and ID.

Column	What to know
`id`	Your organization's unique Greenhouse Recruiting ID. This appears in other tables as `organization_id`.
`name`	Your organization's name.

The attributes table

The attributes table represents a list of all scorecard attributes ever used on a scorecard. Each row represents a single scorecard attribute.

Column	What to know
`id`	The scorecard attribute ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the scorecard attribute as it appears in Greenhouse Recruiting.
`category`	The scorecard attribute category.
`created_at`	The date and time the scorecard attribute was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the scorecard attribute was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The departments table

The departments table represents a list of all departments. Each row represents a single department. This table can be joined to any table that has a department_id to get the name of the department.

Column	What to know
`id`	The department ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the department as it appears in Greenhouse Recruiting.
`parent_id`	The department's parent department ID, if applicable.
`created_at`	The date and time the department was created, like `2024-01-31 06:00:00.000`.
`updated_at`	The date and time the department was last updated, like `2024-01-31 06:00:00.000`.

The events table

The events table represents a list of all your organization's events. Each row represents a single event.

Column	What to know
`id`	The event ID.
`name`	The name of the event as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The interviews table

The interviews table represents a list of all your organization's interviews. Each row represents a single interview.

Column	What to know
`id`	The interview ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the interview as it appears in Greenhouse Recruiting.
`created_at`	The date and time the interview was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the interview was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The interviewer tags table

The interviewer_tags table represents a list of all your organization's interviewer tags. Each row represents a single interviewer tag for a single user.

Column	What to know
`user_id`	The user ID associated with the interviewer tag.
`tag`	The interviewer tag as it appears in Greenhouse Recruiting.
`created_at`	The date and time the interview was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the interview was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The offices table

The offices table represents a list of all offices. Each row represents a single office. This table can be joined to any table that has a office_id to get the name of the office.

Column	What to know
`id`	The office ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the office as it appears in Greenhouse Recruiting.
`parent_id`	The office's parent office ID, if applicable.
`created_at`	The date and time the office was created, like `2024-01-31 06:00:00.000`.
`updated_at`	The date and time the office was last updated, like `2024-01-31 06:00:00.000`.

The referrers table

The referrers table represents a list of all referrers. Each row represents a single referrer. This table can be joined to any table that has a referrer_id to get the name of the referrer.

Column	What to know
`id`	The referrer ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the referrer as it appears in Greenhouse Recruiting.
`user_id`	The user ID associated with the referrer, if applicable.
`created_at`	The date and time the referrer was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the referrer was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The rejection reasons table

The rejection_reasons table represents a list of all rejection reasons. Each row represents a single rejection reason.

Column	What to know
`id`	The rejection reason ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the rejection reason as it appears in Greenhouse Recruiting.
`type`	The type of the rejection reason.
`created_at`	The date and time the rejection reason was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the rejection reason was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The sources table

The sources table represents a list of all sources. Each row represents a single source. This table can be joined to any table with a source_id to get the name of the source.

Column	What to know
`id`	The source ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the source as it appears in Greenhouse Recruiting.
`type`	The type of the source.
`created_at`	The date and time the source was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the source was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The stages table

The stages table represents a list of stages by job, whether they are active or not.

Column	What to know
`id`	The stage ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the stage as it appears in Greenhouse Recruiting.
`order`	The order the stage appears on the job.
`active`	Boolean. Results are either `true` or `false`, indicating whether the stage is active.
`created_at`	The date and time the stage was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the stage was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The tags table

The tags table represents a list of all candidate tags. Each row represents a single candidate tag.

Column	What to know
`id`	The tag ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`name`	The name of the tag as it appears in Greenhouse Recruiting.
`created_at`	The date and time the tag was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the tag was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The users table

The users table represents a list of all users. Each row represents a single Greenhouse Recruiting user. This table can be joined to any other table that has a user_id to get the name of a user.

Column	What to know
`id`	The user ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`first_name`	The user's first name.
`last_name`	The user's last name.
`email`	The user's Greenhouse Recruiting email address.
`status`	The user's current status in Greenhouse Recruiting and is one of `active` or `disabled`.
`full_name`	The user's full name.
`employee_id`	The user's employee ID.
`created_at`	The date and time the user was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the user was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).

The user attribute custom fields table

The user_attribute_custom_fields table represents a list of all custom user fields. Each row represents a single value from a single custom user field for a single user.

Column	What to know
`user_id`	The user ID associated with the custom user field.
`custom_field`	The custom user field.
`float_value`	These are numbers entered in the custom user field, if applicable.
`date_value`	The date entered in the custom user field, if applicable.
`display_value`	The value entered into the custom user field as it appears in Greenhouse Recruiting.
`unit`	The currency type entered in the custom user field, if applicable.
`min_value`	The minimum value entered in the custom user field for number range and currency range field types.
`max_value`	The maximum value entered in the custom user field for number range and currency range field types.
`user_id_value`	The Greenhouse Recruiting user ID entered for custom user fields with user field types.
`created_at`	The date and time the custom user field value was associated with a user, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the custom user field value was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`key`	The immutable field key for the custom user field.
`text_value`	The value entered on the custom user field as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The user candidate links table

The user_candidate_links table represents a list of all user candidate links. Each row represents a single user linked to a single candidate.

Column	What to know
`user_id`	The user ID.
`candidate_id`	The candidate ID linked to the user.
`created_at`	The date and time the user candidate link was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the user candidate link was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Process data

The audit log table

The audit_log table represents a list of audit log results in Greenhouse Recruiting. Each row represents a single audit log result.

Note: Audit log is only available to Expert subscription tier.

Column	What to know
`request_id`	The ID of the audit log request, which can be used to link an event and its resulting changes across multiple audit log results.
`request_type`	The type of request.
`performer_meta`	The name and Greenhouse Recruiting email address of the person who performed the change or the exact type of API key that performed the event.
`performer_id`	The Greenhouse Recruiting user ID of the person who performed the change, or the API key name if performed via Greenhouse API.
`performer_ip_address`	The IP address of the performer of the change.
`performer_type`	The performer type and is one of `user`, `api_key`, or `greenhouse_internal`.
`event_time`	The date and time the event occurred, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`event_target_type`	The type of event that occurred.
`event_type`	The type of event that occured and is one of `data_change_update`, `data_change_create`, `data_change_destroy`, `harvest_access`, or `action`. `action` event types are defined in the audit log glossary.
`event_target_id`	The ID of the element that was created, edited, or accessed. This may be blank if the action doesn't target one particular ID.
`event_meta`	The before and after values from data change events, or other relevant data for the event such as the title of a report.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The scheduled interviews table

The scheduled_interviews table represents a list of scheduled interviews. Each row represents a single scheduled interview.

Note: Data is only collected in this table when an interview is scheduled with Greenhouse Recruiting, as evidenced by the presence of a Greenhouse Recruiting scheduling calendar on the scheduled interview's calendar invite. If an interview occurs or a scorecard is submitted on a meeting that was scheduled outside Greenhouse Recruiting, it won't appear in this table.

Column	What to know
`id`	The interviewer ID associated with the scheduled interview.
`application_id`	The application ID associated with the scheduled interview.
`interview_id`	The interview ID.
`status`	The interview's feedback status and is one of `complete` or `awaiting_feedback`.
`scheduled_by_id`	The original scheduler or organizer of the interview. If an interview is rescheduled, this field doesn't update.
`scheduled_at`	The date and time the interview was scheduled at, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC). If an interview is rescheduled, this timestamp doesn't update.
`starts_at`	The date and time the interview was scheduled to start, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`ends_at`	The date and time the interview was scheduled to end, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`all_day_start_date`	The start date for all-day interviews, like `2024-01-31`.
`all_day_end_date`	The end date for all-day interviews, like `2024-01-31`.
`stage_name`	The stage name associated with the scheduled interview.
`interview_name`	The interview name.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`location`	The location of the interview.

The interviewers table

The interviewers table represents a list of interviewers per scheduled interview. Each row represents a single interviewer for a scheduled interview.

Column	What to know
`interview_id`	The interview ID.
`user_id`	The user ID associated with the interview.
`scorecard_id`	The scorecard associated with the interview.
`user`	The user name associated with the interview.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The scorecards table

The scorecards table represents data on submitted scorecards. Each row represents a single submitted scorecard. Connect the scheduled_interviews table to the interviewers table, then connect the scorecards table to the interviewers table.

Note: Data only appears in this table when a scorecard is submitted in Greenhouse Recruiting.

Column	What to know
`id`	The scorecard ID.
`application_id`	The application ID.
`stage_id`	The stage ID.
`interview_id`	The interview ID.
`interviewer_id`	The interviewer ID.
`submitter_id`	The user ID of the person who submitted the scorecard.
`overall_recommendation`	The scorecard's overall recommendation and is one of `Yes`, `Strong Yes`, `No`, `Strong No` or `No Decision`.
`submitted_at`	The date and time the scorecard was submitted, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`scheduled_interview_ended_at`	The date and time the scheduled interview ended, like `2024-01-31 06:00:00.000`.
`total_focus_attributes`	The total count of scorecard focus attributes on the scorecard.
`completed_focus_attributes`	The total count of scorecard focus attributes completed on the scorecard.
`interviewer`	The interviewer's name.
`submitter`	The scorecard submitter's name.
`stage_name`	The stage associated with the scorecard.
`created_at`	The date and time the scorecard was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the scorecard was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`interview_name`	The interview name.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.
`key_takeaways`	The text included in the key takeaways field on the scorecard.

The scorecard attributes table

The scorecard_attributes table represents attribute-level data on submitted scorecards. Each row represents an attribute rating on a submitted scorecard.

Column	What to know
`scorecard_id`	The scorecard ID.
`attribute_id`	The scorecard attribute ID.
`rating`	The scorecard attribute rating.
`notes`	These are the notes associated with the attribute rating, if applicable.
`created_at`	The date and time the scorecard was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the scorecard was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`attribute_name`	The scorecard attribute name.
`attribute_category`	The scorecard attribute category.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The scorecard questions table

The scorecard_questions table represents a snapshot of your organization's scorecard questions. Each row represents a single scorecard question from a single job.

Column	What to know
`id`	The scorecard question ID.
`interview_kit_id`	The interview kit ID.
`question`	The scorecard question.
`answer_type`	The scorecard question answer type.
`active`	Boolean. Results are either `true` or `false`, indicating whether the scorecard question is active.
`priority`	The priority order of the question on the scorecard.
`required`	Boolean. Results are either `true` or `false`, indicating whether the scorecard question is required.
`created_at`	The date and time the scorecard question was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the scorecard question was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`focus_attributes`	These are the scorecard focus attributes associated with the scorecard question, if applicable.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The scorecard question answers table

The scorecard_question_answers table represents submitted scorecard questions and answers. Each row represents a single scorecard question and a single submitted scorecard answer.

Column	What to know
`scorecard_id`	The scorecard ID.
`application_id`	The application ID.
`question`	The scorecard question.
`answer`	The scorecard answer.
`created_at`	The date and time the scorecard was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the scorecard was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`scorecard_question_id`	The scorecard question ID.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The stage snapshots table

The stage_snapshots table represents a daily snapshot of stage-level activity. Each row represents the number of active applications in the stage at 4am ET on a given date for jobs that were open at that time.

Column	What to know
`stage_id`	The stage ID.
`date`	The date of the stage snapshot.
`active_count`	The number of active applications on the stage.
`job_id`	The job ID.
`stage_name`	The stage name as it appears in Greenhouse Recruiting.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Configurable candidate surveys

The survey_builder_surveys table contains a full list of candidate surveys configured for your organization.

Column	What to know
`id`	The candidate survey ID.
`key`	Identifies the survey type. The only option is `candidate_experience`.
`active`	Whether or not your organization is currently sending candidate surveys.
`activated_at`	When a survey was enabled. When the survey is deactivated, this value will be updated to null. The active field can be used to determine the current status of a survey.
`created_at`	When the survey was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	When the candidate survey was updated. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse identification number.

Configurable candidate survey questions

The survey_builder_questions contains a list of the different questions included in your configurable candidate surveys.

Column	What to know
`id`	The candidate survey question ID.
`survey_id`	The ID number for the survey.
`priority`	The order in which the questions are displayed in the survey.
`value`	The text of the question.
`active`	Deleted questions are marked as inactive.
`created_at`	When the question was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	When the candidate question was updated. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse identification number.

Delivered candidate surveys

The delivered_candidate_surveys table contains a list of survey responses. To tie the candidate's response to a specific office or department, the candidate's application is associated with a specific hiring plan based on their job application. That hiring plan is connected with a department and office based on your organization's setup.

Column	What to know
`id`	The delivered candidate survey ID.
`submitted_at`	The date and time the candidate survey response was submitted, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`department_id`	The unique ID of the department associated with the hiring plan where the candidate applied.
`department_name`	The name of the department associated with the hiring plan where the candidate applied.
`office_id`	The unique ID of the first office associated with the hiring plan where the candidate applied.
`office_name`	The name of the first office associated with the hiring plan where the candidate applied.
`created_at`	When the survey was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	When the candidate survey was updated. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse identification number.

Configurable candidate survey answers

The survey_builder_answers table contains a list of submitted responses for candidate surveys. This information can be combined with other configurable candidate survey tables to get a comprehensive view of the survey questions and responses.

Column	What to know
`id`	The candidate survey answer ID.
`survey_id`	The ID number for the survey.
`question_id`	The candidate survey question ID.
`submitted_at`	The date and time the candidate survey response was submitted, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`value`	The candidate's answer.
`comment`	Comments left in the survey's free text field.
`created_at`	When the answer was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	When the answer was updated. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse identification number.
`delivered_candidate_survey_id`	The identification number for the delivered survey.

The approvals table

The approvals table represents a list of approvals. Each row with an offer_id represents a specific job or offer approval associated with each approver. Any row in this table that doesn't contain an offer_id, is a reflection of the approval flow.

Column	What to know
`offer_id`	The offer ID.
`application_id`	The application ID.
`job_id`	The job ID.
`job_name`	The job name as it appears in Greenhouse Recruiting.
`candidate_id`	The candidate ID.
`candidate_name`	The candidate's name.
`approver_id`	The user ID of the approver.
`approver_name`	The approver's name.
`approval_type`	The approval type. Responses are either `Offer Candidate` for candidate offers, `Open Job` for one-stage approvals, and `Offer Job` for two-stage approvals.
`status`	The approval status and is one of `Due`, `Waiting`, `Approved`, or `Rejected`.
`version`	The approval version.
`version_final`	The final version of the approval.
`group_id`	The approval group ID.
`group_order`	The approver's order in the approval group.
`group_quorum`	The number at which group quorum is reached.
`assigned_at`	The date and time the approval was assigned, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`completed_at`	The date and time the approval was completed, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`created_at`	The date and time the approval was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the approval was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The GDPR consent requests table

The gdpr_consent_requests table represents a list of GDPR consent requests. Each row represents a timestamped GDPR request to a single candidate.

Column	What to know
`candidate_id`	The candidate ID.
`status`	The status of the GDPR consent request.
`token`	A token associated with the GDPR consent request.
`requested_at`	The date and time the GDPR consent was requested, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The GDPR consent decisions table

The gdpr_consent_decisions table represents a list of when candidates gave or denied GDPR consent. Each row represents a timestamped approval or denial of GDPR consent by a single candidate.

Column	What to know
`candidate_id`	The candidate ID.
`decision`	The candidate's decision for the GDPR consent request and is one of `given` or `denied`.
`decided_at`	The date and time the GDPR consent decision was submitted, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The GDPR office rules table

The gdpr_office_rules table represents a list of GDPR office rules. Each row represents a single office's GDPR retention period.

Column	What to know
`office_id`	The office ID associated with the GDPR rule.
`retention_period`	The retention period in days for the GDPR office rule.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The prospect pools table

The prospect_pools table represents a list of prospect pools. Each row represents a single prospect pool.

Column	What to know
`id`	The prospect pool ID.
`name`	The name of the prospect pool as it appears in Greenhouse Recruiting.
`active`	Boolean. Results are either `true` or `false`, indicating whether the prospect pool is active.
`description`	The prospect pool description, if applicable.
`created_at`	The date and time the prospect pool was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the prospect pool was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The prospect pool stages table

The prospect_pool_stages table represents a list of prospect pool stages. Each row represents a single prospect pool stage from a single prospect pool.

Column	What to know
`id`	The prospect pool stage ID.
`prospect_pool_id`	The prospect pool ID.
`name`	The name of the prospect pool stage.
`priority`	The order of the prospect pool stage.
`created_at`	The date and time the prospect pool stage was created, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the prospect pool stage was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The prospect pool transitions table

The prospect_pool_transitions table records when an application is moved from one prospect pool to another, or from one prospect pool stage to another. Each row represents a single prospect's movement from a single prospect pool to another prospect pool or stage.

Column	What to know
`application_id`	The prospect's application ID.
`user_id`	The user ID associated with moving the prospect.
`old_prospect_pool_id`	The ID of the prospect's former prospect pool, if applicable.
`old_prospect_stage_id`	The ID of the prospect's former prospect pool stage, if applicable.
`new_prospect_pool_id`	The ID of the prospect's new prospect pool, if applicable.
`new_prospect_stage_id`	The ID of the prospect's new prospect pool stage, if applicable.
`created_at`	The date and time the prospect pool transition occurred, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`updated_at`	The date and time the prospect was last updated, like `2024-01-31 06:00:00.000`. Timestamps are in Coordinated Universal Time (UTC).
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

Usage data

The Greenhouse usages table

The greenhouse_usages table represents a record of Greenhouse Recruiting usage by users. Each row represents a record of a user using Greenhouse Recruiting on a single date.

Column	What to know
`user_id`	The user ID.
`date`	The date of the Greenhouse Recruiting usage, like `2024-01-31`.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

The user actions table

The user_actions table represents a record of user actions in Greenhouse Recruiting. Each row represents a single action from a user on a single job.

Note: Not all actions in Greenhouse Recruiting are collected in this table. In general, it's better to look for a timestamped activity in another table.

Column	What to know
`id`	The user action ID.
`job_id`	The job ID.
`user_id`	The user ID of the person who performed the action.
`type`	The type of action and is limited to `advanced_candidate` which indicates a candidate was advanced to a different stage.
`organization_id`	Your organization's unique Greenhouse Recruiting ID.

GHSA...

Learn more

Business Intelligence Connector overview

Entity Relationship Diagram (ERD)

Frequently asked questions

Current schema

In this article

Application data

The applications table

The application custom fields table

The application question answers table

The application stages table

The applications jobs table

The referral question custom fields table

The rejection question custom fields table

The agency question custom fields table

Candidate data

The candidates table

The candidate custom fields table

The candidate tags table

The educations table

The employments table

Candidate PII data

The candidate email addresses table

The candidate mailing addresses table

The candidate phone numbers table

Demographic data

The demographic answers table

The demographic answer options table

The demographic answer option translations table

The demographic free form answers table

The demographic questions table

The demographic question set table

The demographic question translations table

The EEOC responses table

Greenhouse Onboarding data

The Greenhouse Onboarding assigned tasks table

The Greenhouse Onboarding custom fields table

The Greenhouse Onboarding custom field values table

The Greenhouse Onboarding employees table

The Greenhouse Onboarding employee roles table

The Greenhouse Onboarding roles table

The Greenhouse Onboarding user activities table

Greenhouse Sourcing Automation (GHSA) data

The GHSA actions table

The GHSA campaign pool performance table

The GHSA message activity table

The GHSA outreach steps table

The GHSA task table

The GHSA lookups table

Job data

The jobs table

The job custom fields table

The job snapshots table

The jobs attributes table

The jobs departments table

The jobs interviews table

The jobs offices table

The jobs posts table

The job post locations table

The job post questions table

The jobs stages table

The hiring team table

The openings table

The opening custom fields table

Offer data

The offers table

The offer custom fields table

Organization data

The organizations table

The attributes table

The departments table

The events table

The interviews table

The interviewer tags table

The offices table

The referrers table

The rejection reasons table

The sources table

The stages table

The tags table

The users table

The user attribute custom fields table

The user candidate links table

Process data

The audit log table