bullhorn.com REST API Client
Dependencies:
requests - HTTP for Humans
Quick Example:
auth = dict(
client = "Bullhorn OAuth Client ID",
secret = 'Bullhorn OAuth Client Secret',
usr = "Bullhorn Username",
pwd = "Bullhorn Password")
bhr = BHRest(**auth)
# If in the sandbox environment - update URLs
bhr._auth_url = "https://auth9.bullhornstaffing.com/oauth"
bhr._rest_url = "https://rest9.bullhornstaffing.com/rest-services"
print bhr.access_token
print bhr.find(query="+12345678")
Features:
Automatically refresh rest_token/url if access_token has expired.
Search the following entity types given a string containing search terms:
ClientContact
JobOrder
Candidate
ClientCorporation
Lead (if leadsAndOpportunitiesEnabled = true)
Opportunity (if leadsAndOpportunitiesEnabled = true)
To search through the phone numbers start query with the “+” and append last 8 digits.
Metadata
Release files for bh_oauth 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bh_oauth-2.0.0.tar.gz | 4.2 kB | Without provenance | Details for bh_oauth-2.0.0.tar.gz |
Release files / bh_oauth-2.0.0.tar.gz
| Download URL | bh_oauth-2.0.0.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90a1ea888cf49eaf7b1c6fbcc84bf472409dcca27c0097fc4170b1a806ea3773
|
|
BLAKE2b-256 checksum How to use checksums |
e8ca470da6fdd0769a6135caab79170dd5719e1269440044cac9b3894d7ce6b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bh_oauth 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.