Sourcier Advanced icon

Sourcier Advanced

Full CRUD operations for Bullhorn CRM/ATS via Sourcier SDK

Job Submission → Get Many

AI-generated

Summary

Retrieve multiple Job Submission records from Bullhorn using a JPQL WHERE clause with optional field selection, result limit, and automatic exclusion of deleted or archived records.

Inputs

  • Authentication — Choose between 'User Credentials (Email & Password)' or 'Enterprise Credentials (API Key)' for authentication.
  • Enable Operations Log — Optionally emit an audit log row to a second output for each write operation; defaults to false and primarily for audit trailing.
  • Fields — Specify which Bullhorn fields to return for each job submission. You can rename fields in the output or leave empty to keep original names.
  • Limit — Maximum number of Job Submission records to return, up to 500; default is 20.
  • Where Clause (required) — JPQL WHERE clause to filter job submissions; for example, "id > 0" or "status = 'Open'". Note that not all entities support 'isDeleted' field.
  • Hide Deleted — Whether to automatically exclude deleted or archived job submissions by adding 'isDeleted=false' or excluding 'status=Archive' when applicable; defaults to true.
  • Output Fields — Extra fields or fixed values to merge into every output item, useful for enriching results with constant or input-derived data.

Output shape

a list of job submission records matching the provided WHERE clause and filters, each containing the requested fields.

The operation returns up to the specified limit of records (default 20, maximum 500). The 'Where Clause' must be provided; it is a JPQL syntax string for filtering records. If 'Hide Deleted' is true, the query automatically excludes deleted or archived records where supported. Optional field mappings allow renaming fields in the output. If enabled, a secondary output may emit audit log entries for write operations, but since this operation is read-only, it does not produce such logs.

Links

Discussion