2025-07-13

 

GraphQL schema change log: 2025-07-13

• 📘 Documentation: Added these GraphQL schema changes:

  • ✔ Input field DateQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in. 

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field DateQuestionInput.format description, changed from:

    Format is required when using this screener question type. The format must be dd/MM/yyyy or another locale specific format that meets Unicode CLDR formatting.
    
    Indeed uses the SimpleDateFormat, so month must be formatted as MM. Using mm results in misconfiguration.
    
    The format of type=date impacts how the application is passed to the ATS and the parsing of minimum and maximum values. The job seeker still enters the date based on their locale, not the specified format, and validation error messages are in their locale’s format. Use yyyy instead of yy in the format to prevent confusion. 

    To:

    This screener question type requires either the dd/MM/yyyy format or a locale-specific format that meets Unicode CLDR formatting.
    
    Indeed uses the `SimpleDateFormat`. You must format the month as MM. Using mm results in misconfiguration.
    
    The format of `type=date` impacts how the application is passed to the ATS and how the minimum and maximum values are parsed. The job seeker still enters the date based on their locale, not the specified format, and validation error messages are in their locale’s format. To prevent confusion, use yyyy instead of yy in the format.

  • ✔ Input field DateQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ". 

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field DecimalTextQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field DecimalTextQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ". 

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field DemographicQuestionsBodyInput.date description, changed from:

    A question that displays a text field that only accepts date entry. Used for questions that must be answered with a date.
    
    Format is required when using this screener question type. The format must be dd/MM/yyyy or another locale specific format that meets Unicode CLDR formatting.
    
    Indeed uses the SimpleDateFormat, so month must be formatted as MM. Using mm results in misconfiguration.
    
    The format of type=date impacts how the application is passed to the ATS and the parsing of minimum and maximum values. The job seeker still enters the date based on their locale, not the specified format, and validation error messages are in their locale’s format. Use yyyy instead of yy in the format to prevent confusion. 

    To:

    A question that has a date as an answer. Appears as a text field that accepts a date.
    
    This screener question type requires either the dd/MM/yyyy format or a locale-specific format that meets Unicode CLDR formatting.
    
    Indeed uses the `SimpleDateFormat`. You must format the month as MM. Using mm results in misconfiguration.
    
    The format of `type=date` impacts how the application is passed to the ATS and how the minimum and maximum values are parsed. The job seeker still enters the date based on their locale, not the specified format, and validation error messages are in their locale’s format. To prevent confusion, use yyyy instead of yy in the format.

  • ✔ Input field DemographicQuestionsBodyInput.information description, changed from:

    A text display that does not require a response. Creates explanatory text or provide section headings.
    See [documentation](https://docs.indeed.com/indeed-apply/screener-questions#information) for more details.

    To:

    A text display that does not require a response. Appears as explanatory text or section headings.
    For details, see [information](https://docs.indeed.com/indeed-apply/screener-questions#information).

  • ✔ Input field DemographicQuestionsBodyInput.multiselect description, changed from:

    A question that displays a list of checkboxes that enables the applicant to select multiple answers. Used for questions with multiple answers.

    To:

    A question that has multiple answers. Appears as a list of checkboxes that enables the applicant to select multiple answers. 

  • ✔ Input field DemographicQuestionsBodyInput.pageBreak, changed from:

     Groups questions on a page. All questions included between two pagebreak types appear on the same page. You can group up to 20 questions on the same page. Indeed defaults to 3 questions per page on desktop and groups all questions onto a single page for mobile.

    To:

    Groups questions on a page. Questions defined between two pagebreak types appear on the same page. You can group up to 20 questions on a page. By default, Indeed shows three questions on a page on desktop and groups all questions on a page for mobile.

  • ✔ Input field DemographicQuestionsBodyInput.select description, changed from:

    A question that displays a dropdown menu that allows the applicant to select a single answer. Used for questions with multiple choice answers.
    
    If you include from one to five answer options, they appear with radio buttons. If you include from six or more answer options, they appear in a dropdown menu. 

    To:

    A question with multiple choice answers. Appears as a dropdown list that enables the applicant to select a single answer.
    
    If you include from one to five answers, each answer appears with a radio button. If you include more than five answers, they appear in a dropdown list.

  • ✔ Input field DemographicQuestionsBodyInput.text description, changed from:

    A question that displays a single-line text entry field. Used for questions with shorter answers.
    
    For more information on the different formats available for text questions, see the following examples and the JSON screener questions parameters table. The formats are integer, decimal, numeric_text. 

    To:

    A question that requires a short answer. Appears as a single-line text entry field.
    
    For more information on the available formats for text questions, see the following examples and the [JSON questions parameters](https://docs.indeed.com/indeed-apply/screener-questions#json-questions-parameters). The formats are `integer`, `decimal`, and `numeric_text`.

  • ✔ Input field DemographicQuestionsBodyInput.textarea description, changed from:

    A question that displays a multi-line text entry field. Used for questions with long-form answers.

    To:

    A question that requires a long-form answer. Appears as a multi-line text entry field.

  • ✔ Input field FileQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in. 

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field FileQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ". 

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field FreeformTextQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field FreeformTextQuestionInput.required, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ".

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field HierarchicalOptionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field HierarchicalQuestionInput.condition, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field HierarchicalQuestionInput.options description, changed from:

    The list of options available.

    To:

    The list of available options.

  • ✔ Input field HierarchicalQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ".

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field IndeedApplyScreenerQuestionsDefinitionInput.demographicQuestions description, changed from:

    The demographic questions should be a list of specific, well-formatted questions pertaining to the job applicants protected class. That is, ethnicity, gender, disability, and so on. These sorts of questions are regulated in certain jurisdictions, meaning they must be handled in special ways in Indeed systems, and potentially yours. Do not mix general screener questions, such as those pertaining to work experience, skills, or certifications, into this list. Instead place them in the screenerQuestions list above.
    
    Today, these questions are limited to U.S.-based jobs for EEO compliance.

    To:

    The demographic questions are a list of specific, well-formatted questions that pertain to the job applicants *protected class*. That is, ethnicity, gender, disability, and so on. Certain jurisdictions must regulate these questions. Indeed systems, and potentially your systems, must handle these questions in special ways. 
    
    These questions are limited to U.S.-based jobs for EEO compliance.
    
    Do not include general screener questions, such as those that pertain to work experience, skills, or certifications, in this list. Instead place them in the `screenerQuestions` list.

  • ✔ Input field IndeedApplyScreenerQuestionsDefinitionInput.screenerQuestions description, changed from:

    The screener questions should be a list of general, well formatted questions pertaining to the underlying job such as work experience, skills, certifications, etc. It should NOT contain demographic questions such as question about ethnicity, gender, or disability. Questions related to protected classes of people are regulated in certain jurisdictions meaning they must be handled in special ways inside Indeed systems (and potentially yours).

    To:

    The screener questions are a list of general, well-formatted questions that pertain to the underlying job, such as work experience, skills, certifications, and so on. This list cannot contain demographic questions, such as question about ethnicity, gender, or disability. Certain jurisdictions regulate questions related to *protected classes* of people. Indeed systems, and potentially your systems, must handle these questions in special ways.

  • ✔ Input field InformationQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field IntegerTextQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field IntegerTextQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ".

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field MultiselectQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field MultiselectQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ".

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field NumericTextQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field NumericTextQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ".

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field ScreenerQuestionBodyInput.date description, changed from:

    A question that displays a text field that only accepts date entry. Used for questions that must be answered with a date.
    
    Format is required when using this screener question type. The format must be dd/MM/yyyy or another locale specific format that meets Unicode CLDR formatting.
    
    Indeed uses the SimpleDateFormat, so month must be formatted as MM. Using mm results in misconfiguration.
    
    The format of type=date impacts how the application is passed to the ATS and the parsing of minimum and maximum values. The job seeker still enters the date based on their locale, not the specified format, and validation error messages are in their locale’s format. Use yyyy instead of yy in the format to prevent confusion.

    To:

    A question that has a date as an answer. Appears as a text field that accepts a date.
    
    This screener question type requires either the dd/MM/yyyy format or a locale-specific format that meets Unicode CLDR formatting.
    
    Indeed uses the `SimpleDateFormat`. You must format the month as MM. Using mm results in misconfiguration.
    
    The format of `type=date` impacts how the application is passed to the ATS and how the minimum and maximum values are parsed. The job seeker still enters the date based on their locale, not the specified format, and validation error messages are in their locale’s format. To prevent confusion, use yyyy instead of yy in the format.

  • ✔ Input field ScreenerQuestionBodyInput.file description, changed from:

    A question that displays a file upload interface. Used for questions that require a file upload as an answer, such as certifications, portfolios, or example work. As detailed in Application data reference, the answer data returned in the JSON POST request contains three fields: contentType, data, and fileName.
    
    Valid files types are:
    doc
    docx
    gif
    jfif
    jif
    jpe
    jpeg
    jpg
    pdf
    png
    rtf
    tif
    tiff
    txt

    To:

    A question that requires a file upload as an answer, such as certifications, portfolios, or example work. Appears as a file upload interface. The answer returned in the JSON `POST` request contains these fields: `contentType`, `data`, and `fileName`.
    
    Valid files types are:
    doc
    docx
    gif
    jfif
    jif
    jpe
    jpeg
    jpg
    pdf
    png
    rtf
    tif
    tiff
    txt

  • ✔ Input field ScreenerQuestionBodyInput.hierarchical description, changed from:

    A question that displays additional questions and responses based on previously selected answers. For example, you might ask an applicant to choose a state. Then, depending on what they select, you could offer them a dropdown list of cities within that state. Each hierarchical question is limited to three levels. For example: state/city/county.
    
    Hierarchical questions are similar to conditional questions. However, hierarchical questions may be better suited to certain question types where an initial selection defines potential answers for subsequent questions. Using the hierarchical functionality reduces the total number of questions needed to obtain related information.

    To:

    A question that shows additional questions and answers based on previously selected answers. For example, you might ask an applicant to choose a state. After they choose a state, you can show a dropdown list of cities within that state. Each hierarchy of questions is limited to three levels. For example: state, city, and county.
    
    A hierarchy of questions are similar to conditional questions. However, a hierarchy of questions are better suited to question types where an initial selection defines potential answers to subsequent questions. Using the hierarchy functionality reduces the number of questions needed to get related information.

  • ✔ Input field ScreenerQuestionBodyInput.information description, changed from:

    A text display that does not require a response. Creates explanatory text or provide section headings.
    See [documentation](https://docs.indeed.com/indeed-apply/screener-questions#information) for more details.

    To:

    A text display that does not require a response. Appears as explanatory text or section headings.
    For details, see [information](https://docs.indeed.com/indeed-apply/screener-questions#information).

  • ✔ Input field ScreenerQuestionBodyInput.multiselect description, changed from:

    A question that displays a list of checkboxes that enables the applicant to select multiple answers. Used for questions with multiple answers.

    To:

    A question that has multiple answers. Appears as a list of checkboxes that enables the applicant to select multiple answers. 

  • ✔ Input field ScreenerQuestionBodyInput.pageBreak description, changed from:

    Groups questions on a page. All questions included between two pagebreak types appear on the same page. You can group up to 20 questions on the same page. Indeed defaults to 3 questions per page on desktop and groups all questions onto a single page for mobile.

    To:

    Groups questions on a page. Questions defined between two pagebreak types appear on the same page. You can group up to 20 questions on a page. By default, Indeed shows three questions on a page on desktop and groups all questions on a page for mobile.

  • ✔ Input field ScreenerQuestionBodyInput.select description, changed from:

    A question that displays a select menu that allows the applicant to select a single answer. Used for questions with multiple choice answers.
    
    If you include from one to five answer options, they appear with radio buttons. If you include from six or more answer options, they appear in a dropdown menu.

    To:

    A question that has multiple-choice answers. Appears as a select menu that enables the applicant to select a single answer.
    
    If you include from one to five answers, each answer appears with a radio button. If you include more than five answers, they appear in a dropdown list.

  • ✔ Input field ScreenerQuestionBodyInput.text description, changed from:

    A question that displays a single-line text entry field. Used for questions with shorter answers.
    
    For more information on the different formats available for text questions, see the following examples and the JSON screener questions parameters table. The formats are integer, decimal, numeric_text.

    To:

    A question that requires a short answer. Appears as a single-line text entry field.
    
    For more information on the available formats for text questions, see the following examples and the [JSON questions parameters](https://docs.indeed.com/indeed-apply/screener-questions#json-questions-parameters). The formats are `integer`, `decimal`, and `numeric_text`.

  • ✔ Input field ScreenerQuestionBodyInput.textarea description, changed from:

    A question that displays a multi-line text entry field. Used for questions with long-form answers.

    To:

    A question that requires a long-form answer. Appears as a multi-line text entry field.

  • ✔ Input field SelectQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field SelectQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ".

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

  • ✔ Input field TextAreaQuestionInput.condition description, changed from:

    Marks a question as conditional, depending on the answer to a previous select question. Specify the id of the previous question as well as the option value that activates this question.
    For example, you might ask the applicant if they served in the military. If they answer yes, you display a conditional question that asks what branch they served in.

    To:

    Marks a question as conditional. A conditional question depends on the answer to a previous question. Specify the ID of the previous question and the option value that activates this question.
    For example, if an applicant responds `yes` to the question of whether they served in the military, show a conditional question that asks in which branch they served.

  • ✔ Input field TextAreaQuestionInput.required description, changed from:

    If set to true, the question is required, which produces a non-empty text field or selection. Set it to false to define questions as optional. If a question is optional and the candidate chooses not to answer, Indeed sends an answer value of ".

    To:

    Set to `true` to define the question as required. Set to `false` to define the question as optional. If the candidate chooses not to answer an optional question, Indeed sends an answer value of ".

 

Was this page helpful?