Bullhorn REST API — Credential Tester

Runs the real Bullhorn OAuth2 + REST login flow (authorization code → access token → BhRestToken). The actual calls are made by the local Node server on your machine, not by your browser — so there's no CORS or iframe/X-Frame-Options blocking.

Active session

1. Data Center / Swimlane

▼

2. Credentials

▼
Already have a BhRestToken and restUrl — e.g. copied from a DevTools Network tab call? Skip to Quick Login below instead of the full OAuth flow.
Submitted to your own local server only (localhost) — which then talks to Bullhorn directly.

3. Explore Bullhorn Entities

▼
No active session — run a successful test login first
Browse what's available on your Bullhorn instance instead of memorizing entity names — pick a category, pick an entity, and its real fields load straight from your instance's /meta endpoint. See the entity reference for the full official list.
·
—
—

4. Record Lookup

▼
No active session — run a successful test login first
Pulls the full field list from /meta/{EntityType} once per session per record type (Bullhorn deprecated fields=* directly on /entity), then fetches the record with that list. Reuses the BhRestToken from your last successful login above — it will NOT refresh automatically. If it expires, click "Test Login" again.

  


  

    
5. Deleted / Duplicate Record Check
▼

    
No active session — run a successful test login first


    

      
      
    


    

      
      
    

    

    

      

        
        

          
          
        

        
        
By default this matches everything before the @ (e.g. searching jane.doe@example.com also catches jane.doe@othercompany.com). Check the box above to require the full address to match exactly instead.

      

    

    

      

        

          
          

            
            
          

        

        

          
          

            
            
          

        

      

    

    

      

        
        

          
          
        

      

    

    

      

        
        

          
          
        

      

    

    

      

        
        

          
          
        

      

    


    
    
Searches the Lucene index (/search), which is the only way to find soft-deleted records — a direct ID lookup won't show them. Results include both active and deleted matches, clearly flagged.