2025-12-03

 

GraphQL schema change log: 2025-12-03

📘 Documentation: Updated the GraphQL schema and the GraphQL API Reference with these changes:

• Removed type HideFromIndeedSearchInput

• Removed field actionUrl from object type JobPostCallToAction

• Removed input field visibility from input object type SourcedJobPostingMetadataInput

• Removed type SourcedJobPostingVisibilityInput

• Changed the description of input field DateQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field DateQuestionInput.format from:

  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.

  To:

  Screener question type that requires either the `dd/MM/yyyy` format or a locale-specific format that meets Unicode CLDR formatting.
  
  Indeed uses the `SimpleDateFormat`. Format the month as `MM`. The `mm` format 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 enters the date based on their locale and not the specified format. Validation error messages are in their locale’s format. To prevent confusion, use the `yyyy` format rather than the `yy` format.

• Changed the description of input field DateQuestionInput.maxDate from:

  The date the answer must be on or before.

  To:

  Answer must be on or before this date.

• Changed the description of input field DateQuestionInput.minDate from:

  The date the answer must be on or after.

  To:

  Answer must be on or after this date.

• Changed the description of input field DateQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field DateQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field DecimalTextQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field DecimalTextQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field DecimalTextQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field DemographicQuestionsBodyInput.date from:

  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.

  To:

  Question that has a date as an answer. Appears as a text field that accepts a date.
  
  Screener question type that requires either the `dd/MM/yyyy` format or a locale-specific format that meets Unicode CLDR formatting.
  
  Indeed uses the `SimpleDateFormat`. Format the month as `MM`. The `mm` format 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 enters the date based on their locale and not the specified format. Validation error messages are in their locale’s format. To prevent confusion, use the `yyyy` format rather than the `yy` format.

• Changed the description of input field DemographicQuestionsBodyInput.multiselect from:

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

  To:

  Question that has multiple answers. Appears as a list of checkboxes that accepts multiple answers. 

• Changed the description of input field DemographicQuestionsBodyInput.select from:

  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.

  To:

  A question with multiple choice answers. Appears as a list that accepts 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 list.

• Changed the description of input field DemographicQuestionsBodyInput.text from:

  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`.

  To:

  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`.

• Changed the description of input field DemographicQuestionsBodyInput.textarea from:

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

  To:

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

• Changed the description of input field FileQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field FileQuestionInput.format from:

  The supported file formats for the file upload. Omitting this field will allow any file format.

  To:

  Supported file formats for the file upload. Omit this field to support all file formats.

• Changed the description of input field FileQuestionInput.max from:

  The maximum number of files that can be uploaded.

  To:

  Maximum number of files that applicant can upload.

• Changed the description of input field FileQuestionInput.min from:

  The minimum number of files that can be uploaded.

  To:

  Minimum number of files that applicant can upload.

• Changed the description of input field FileQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field FileQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field FindEmployerJobsPartnerFilterInput.jobFeedType from:

  Filters jobs by their feed type, or source.
  
  If feed type is `UNKNOWN`, you can specify two feed types. Otherwise, you can specify only one feed type.
  
  Jobs before June 1, 2025 may have unknown feed type - include `UNKNOWN` to include jobs that could not be classified.
  
  If you omit this value, default is `INTEGRATED_FROM_PARTNER`.

  To:

  Filters jobs by their feed type, or source.
  
  If feed type is `UNKNOWN`, you can specify two feed types. Otherwise, you can specify only one feed type.
  
  Jobs before June 1, 2025 might have the `UNKNOWN` feed type. To list only jobs that were not classified, specify `UNKNOWN`.
  
  If you omit this value, default is `INTEGRATED_FROM_PARTNER`.

• Changed the description of input field FindEmployerJobsPartnerFilterInput.legacySourceId from:

  Primarily intended for ad agency partners.
  
  `legacySourceId` is an alphanumeric source ID that the Sponsored Jobs API returns.
  
  [`findEmployerJobsPartner`](/api/job/queries/findEmployerJobsPartner) returns a list of job postings that share this ID.
  
  If you omit the `legacySourceId` field, [`findEmployerJobsPartner`](/api/job/queries/findEmployerJobsPartner) lists job postings for the employer associated with the access token with which you call the API.

  To:

  Intended primarily for ad agency partners.
  
  `legacySourceId` is an alphanumeric source ID that the Sponsored Jobs API returns.
  
  [`findEmployerJobsPartner`](/api/job/queries/findEmployerJobsPartner) returns a list of job postings that share this ID.
  
  If you omit the `legacySourceId` field, [`findEmployerJobsPartner`](/api/job/queries/findEmployerJobsPartner) lists job postings for the employer associated with the access token with which you call the API.

• Changed the description from:

  <!--
  NOTE: the following fields should be added in the future as part of the 1.1, 1.2 and 1.3 IA update
  
  # The minimum amount of characters accepted for the answer.
  minCharCount: Int @Min(value: 0)
  -->

  Removed from object type FreeformTextQuestionInput.

• Changed the description of input field FreeformTextQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field FreeformTextQuestionInput.maxCharCount from:

  The maximum character limit for the answer.

  To:

  Maximum character limit for the answer.

• Changed the description of input field FreeformTextQuestionInput.minCharCount from:

  The minimum character limit for the answer.

  To:

  Minimum character limit for the answer.

• Changed the description of input field FreeformTextQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field FreeformTextQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field HierarchicalOptionInput.condition from:

  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. 

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field HierarchicalOptionInput.options from:

  The list of options available.

  To:

  List of options.

• Changed the description of input field HierarchicalQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field HierarchicalQuestionInput.hierarchicalOptions 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

  To:

  Question that displays additional questions and responses based on previously selected answers. For example, you might ask an applicant to choose a state. Based on their selection, offer them a list of cities within that state. Each hierarchical question is limited to three levels.

• Changed the description of input field HierarchicalQuestionInput.options from:

  The list of available options.

  To:

  List of options.

• Changed the description of input field HierarchicalQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field HierarchicalQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field IndeedApplyScreenerQuestionsDefinitionInput.screenerQuestions from:

  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.

  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 questions 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.

• Changed the description of input field InformationQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field IntegerTextQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field IntegerTextQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field IntegerTextQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of enum value JobFeedType.INTEGRATED_FROM_PARTNER from:

  Jobs integrated from partner systems (XML feeds, Job API).

  To:

  Jobs integrated from XML feeds or Job Sync API integrations.

• Changed the description of enum value JobFeedType.UNKNOWN from:

  Unknown or unclassified job feed type.
  
  Includes jobs that may not immediately have source data that can be bucketed into a feed type.

  To:

  Unknown or unclassified job feed type.
  
  Includes jobs that might not immediately have source data that identifies a feed type.

• Added field isIndeedApplyActive to object type JobPostGlobalStatus

• Changed the description of type JobPostStatus from:

  the status of a job post including searchability, sponsorship requirements, messaging tags, etc.

  To:

  External status type definitions from JobPost

• Object type JobPostStatusInput has description:

  Input parameters for JobPost status - required for federation compatibility
  
  This input type must match the signature defined in the job-audit-api subgraph

• Changed the description of input field MultiselectQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field MultiselectQuestionInput.maxSelectionCount from:

  If set, configures the maximum amount of options that can be selected.

  To:

  Defines the maximum number of options that the applicant can select.

• Changed the description of input field MultiselectQuestionInput.minSelectionCount from:

  If set, configures the minimum amount of options that can be selected.

  To:

  Defines the minimum number of options that the applicant can select.

• Changed the description of input field MultiselectQuestionInput.options from:

  The list of options available.

  To:

  List of options.

• Changed the description of input field MultiselectQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field MultiselectQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field NumericTextQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field NumericTextQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field NumericTextQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field ScreenerQuestionBodyInput.date from:

  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.

  To:

  Question that has a date as an answer. Appears as a text field that accepts a date.
  
  Screener question type that requires either the `dd/MM/yyyy` format or a locale-specific format that meets Unicode CLDR formatting.
  
  Indeed uses the `SimpleDateFormat`. Format the month as `MM`. The `mm` format 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 enters the date based on their locale and not the specified format. Validation error messages are in their locale’s format. To prevent confusion, use the `yyyy` format rather than the `yy` format.

• Changed the description of input field ScreenerQuestionBodyInput.file from:

  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

  To:

  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

• Changed the description of input field ScreenerQuestionBodyInput.hierarchical from:

  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.

  To:

  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 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 but they are better suited to question types where an initial selection defines potential answers to subsequent questions. The hierarchy functionality reduces the number of questions needed to get related information.

• Changed the description of input field ScreenerQuestionBodyInput.multiselect from:

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

  To:

  Question that has multiple answers. Appears as a list of checkboxes that accepts multiple answers.

• Changed the description of input field ScreenerQuestionBodyInput.select from:

  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.

  To:

  Question that has multiple-choice answers. Appears as a select menu that accepts 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 list.

• Changed the description of input field ScreenerQuestionBodyInput.text from:

  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`.

  To:

  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 these 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`.

• Changed the description of input field ScreenerQuestionBodyInput.textarea from:

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

  To:

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

• Changed the description of input field SelectQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field SelectQuestionInput.options from:

  The list of options available.

  To:

  List of options.

• Changed the description of input field SelectQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field SelectQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field SourcedJobPostingMetadataInput.photos from:

  Photos for the job.

  To:

  Photos for the job.
  
  Supported image formats:
    - image/png
    - image/jpeg
    - image/gif
    - image/webp
  
  Supported image resolution:
    - Width:
      - Min in API spec: 250 px
      - Max: 20000 px
    - Height:
      - Min in API spec: 250 px
      - Max: 20000 px
  
  File Size (Bytes):
    - Max: 20971520 ( = 20MB)
    - Min in API Spec: 10240 ( = 10KB)

• Changed the description from:

  <!--
  NOTE: the following fields should be added in the future as part of the 1.1, 1.2 and 1.3 IA update
  
  # The minimum amount of characters accepted for the answer.
  minCharCount: Int @Min(value: 0)
  -->

  Removed from object type TextAreaQuestionInput.

• Changed the description of input field TextAreaQuestionInput.condition from:

  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.

  To:

  Marks a question as conditional. The 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.

• Changed the description of input field TextAreaQuestionInput.maxCharCount from:

  The maximum character limit for the answer.

  To:

  Maximum character limit for the answer.

• Changed the description of input field TextAreaQuestionInput.minCharCount from:

  The minimum character limit for the answer.

  To:

  Minimum character limit for the answer.

• Changed the description of input field TextAreaQuestionInput.question from:

  The question text that applicants see.

  To:

  Question text that applicants see.

• Changed the description of input field TextAreaQuestionInput.required from:

  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 ".

  To:

  If `true`, defines the question as required. If the applicant does not answer an optional question, Indeed sends an answer value of ".

• Changed the description of input field TextQuestionInput.decimal from:

  A question that expects an decimal / floating-point number answer.

  To:

  Question that has a decimal or floating-point number answer.

• Changed the description of input field TextQuestionInput.freeform from:

  A question that expects an freeform text answer.

  To:

  Question that has a freeform text answer.

• Changed the description of input field TextQuestionInput.integer from:

  A question that expects an integer answer.

  To:

  Question that has an integer answer.

• Changed the description of input field TextQuestionInput.numeric from:

  A question that expects an numeric text answer, such as numeric identifiers with leading zeros.

  To:

  Question that has a numeric text answer, such as numeric identifiers with leading zeros.

• Changed the description of input field TextScreenerQuestionInput.integer from:

  This question accepts only integers as answers, does not allow for decimals or leading zeroes 

  To:

  Question that accepts only integers as answers. Does not allow for decimals or leading zeroes.

 

Was this page helpful?