OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Recruiting entities such as Candidate and JobOrder are structured REST records.
Bullhorn REST API reference ↗
API Operations · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Query/search interfaces support bounded pages and field selection.
Bullhorn REST API reference ↗
query; search; start and count parameters · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
JPQL query and Lucene search predicates are documented.
Bullhorn REST API reference ↗
API Operations · Checked 2026-10-16
Access cost barrier -
-
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
Bullhorn REST API reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Customer credentials require support provisioning; partners obtain registered client keys.
Bullhorn credential provisioning FAQ ↗
How do I obtain REST API credentials · Checked 2026-10-16
Downstream permission -
-
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
Bullhorn REST API reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
PUT creates and POST updates entity records.
Bullhorn REST API reference ↗
PUT /entity; POST /entity · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Customer/partner applications use provisioned OAuth clients and fixed REST interfaces.
Bullhorn credential provisioning FAQ ↗
Customer and partner API credentials · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Entity subscriptions announce ongoing changes.
Bullhorn REST API reference ↗
PUT /event/subscription · Checked 2026-10-16
Limit visibility 7.5/10
Numeric usage or polling guidance
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
The reference publishes request-level result-count and association limits.
Bullhorn REST API reference ↗
General GET request options; count · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Entity subscriptions include INSERTED/UPDATED/DELETED and entity identity.
Bullhorn REST API reference ↗
PUT /event/subscription; GET /event/subscription · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
requestId permits regetting events; durable retention/checkpoint guarantees are unverified.
Bullhorn REST API reference ↗
GET /event/subscription requestId · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Authorized selected fields return as JSON records.
Bullhorn REST API reference ↗
General GET request options · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
No retrieval window or export charge at cancellation is established by these technical sources.
Bullhorn REST API reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Portable entity records; nested association limits and independent file/history scope remain.
Bullhorn REST API reference ↗
Entity fields; to-many association limits · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
The developer OAuth route enables external recruiting integrations.
Bullhorn OAuth flow ↗
Registering your application · Checked 2026-10-16
Rights to custom logic -
-
Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded.
Rights to native workflow artifacts and independent execution are not established.
Bullhorn REST API reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
OAuth produces an access token, then REST login returns BhRestToken and a corporation-specific base URL. Customer and partner client provisioning follow distinct paths.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Entity, query and search interfaces return selected fields. Metadata describes the schema; paged top-level queries do not guarantee complete nested associations, which have separate limits.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Support-provisioned customer OAuth client | OAuth 2.0 | Customer | Yes | customer requests oauth credentials through support; authorizing user then rest login | 2026-10-16 |
| Registered partner OAuth client | OAuth 2.0 | Integration provider | Yes | partner client registration and customer oauth authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
API pricing and the lowest entitled package were not established. The reference documents per-request counts and search constraints; a current universal throughput allowance was not verified.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
PUT entity creates and POST entity updates a named entity such as Candidate. Validate fieldmap requirements, permissions and associations; safe replay of ambiguous creates is unresolved.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Subscriptions include INSERTED, UPDATED and DELETED entity events. A requestId can reget events, but retention and resnapshot guarantees were not established.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Entity subscriptions include INSERTED/UPDATED/DELETED and entity identity. | Bullhorn REST API reference ↗PUT /event/subscription; GET /event/subscriptionChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. requestId permits regetting events; durable retention/checkpoint guarantees are unverified. | Bullhorn REST API reference ↗GET /event/subscription requestIdChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Selected entity records are portable JSON. Excluded nested relationships, file content, audit history and complete product reconstruction require separate manifests and checks.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
The API supports external recruiting integrations. Subscription request identifiers are a recovery aid (they do not establish durable historical custody or portable native workflows).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Recruiting entities such as Candidate and JobOrder are structured REST records. | Bullhorn REST API reference ↗API OperationsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Query/search interfaces support bounded pages and field selection. | Bullhorn REST API reference ↗query; search; start and count parametersChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. JPQL query and Lucene search predicates are documented. | Bullhorn REST API reference ↗API OperationsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Customer credentials require support provisioning; partners obtain registered client keys. | Bullhorn credential provisioning FAQ ↗How do I obtain REST API credentialsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | Bullhorn REST API reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | Bullhorn REST API reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. PUT creates and POST updates entity records. | Bullhorn REST API reference ↗PUT /entity; POST /entityChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Customer/partner applications use provisioned OAuth clients and fixed REST interfaces. | Bullhorn credential provisioning FAQ ↗Customer and partner API credentialsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Entity subscriptions announce ongoing changes. | Bullhorn REST API reference ↗PUT /event/subscriptionChecked 2026-10-16 |
| How are integration limits disclosed? | Numeric usage or polling guidanceBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. The reference publishes request-level result-count and association limits. | Bullhorn REST API reference ↗General GET request options; countChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Authorized selected fields return as JSON records. | Bullhorn REST API reference ↗General GET request optionsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. No retrieval window or export charge at cancellation is established by these technical sources. | Bullhorn REST API reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. The developer OAuth route enables external recruiting integrations. | Bullhorn OAuth flow ↗Registering your applicationChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Bullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Rights to native workflow artifacts and independent execution are not established. | Bullhorn REST API reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedBullhorn ATS/CRM REST entity/query/meta APIs and subscriptions, using customer-provisioned OAuth or registered partner clients; other Bullhorn products excluded. Portable entity records; nested association limits and independent file/history scope remain. | Bullhorn REST API reference ↗Entity fields; to-many association limitsChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest-plan API entitlement and fixed access fees
- Complete attachments/history and deletion recovery
- Native workflow rights and cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.