Configure the Tax Credit Co. (TCC) WOTC Integration

The Tax Credit Co. (TCC) integration allows your organization to screen candidates for Work Opportunity Tax Credit (WOTC) eligibility directly within Bullhorn Onboarding. By connecting TCC's REST API, recruiters and candidates can complete the WOTC screening process in real time without leaving the platform.

Setting up this integration correctly ensures candidates move through the onboarding workflow smoothly and that your organization captures available tax credits.

Common Reasons You Might Use This Article

  • You want to enable WOTC screening for candidates during onboarding.

  • Candidates are unable to complete the Tax Credit step in their application.

  • The WOTC screening page is not loading or is displaying an error.

  • The "Next" button is not appearing after a candidate finishes the WOTC survey.

  • You need to confirm your TCC integration settings are configured correctly.

  • You recently made changes to your TCC settings and they do not seem to be taking effect.

What Is WOTC?

The Work Opportunity Tax Credit (WOTC) is a federal tax credit available to employers who hire individuals from certain groups that have faced significant barriers to employment. You can learn more on the U.S. Department of Labor WOTC page. The TCC integration automates the WOTC screening process by embedding TCC's questionnaire directly into the candidate's onboarding experience.

Enable the TCC WOTC Integration in Settings

Before configuring Blueprints and Forms, you must enable the integration and enter the correct API connection details. Incorrect values in these fields are the most common source of integration issues.

  1. Navigate to Settings > Integrations > Work Opportunity Tax Credit (WOTC).

  2. Toggle TCC WOTC to enabled.

  3. Open the drop-down and complete the following fields:

Field

Description

Partner Account Code

The Able Customer ID for the client. Confirm this value for each client, some accounts may use a different code.

API User

Provided by TCC. This value is the same across all integrations. Copy from an existing integration or ask a developer.

API Password

Provided by TCC. This value is the same across all integrations. Copy from an existing integration or ask a developer.

API Base URL

TCC's REST API endpoint. This value is the same across all integrations but differs by environment (see below).

Callback URL

The Able callback URL that receives status updates from TCC. This value differs by environment (see below).

Set the Correct API Base URL

Using the wrong API Base URL is one of the most common misconfigurations. Make sure the URL matches the environment you are configuring.

  • Production: https://applicanttrackingservices.taxcreditco.com/ApplicantRestService.svc/

  • Staging: https://uat-applicanttrackingservices.taxcreditco.com/ApplicantRestService.svc/

Set the Correct Callback URL

The Callback URL allows TCC to send screening status updates back to Bullhorn. Use the URL that matches your environment.

  • Production: https://app-api.employstream.com/api/v1/tcc/callback/

  • Staging: https://staging-api.employstream.com/api/v1/tcc/callback/

  • DevQA: https://dev-api.employstream-dev.space/api/v1/tcc/callback/

  • Test: https://app-api.test.ableteams.com/api/v1/tcc/callback/

Enable WOTC in System Settings (Optional)

This setting is only required if your organization delivers the WOTC screening as part of the online application. If you send the WOTC screening as a standalone form or as part of a package, you can skip this step.

  1. Navigate to Settings > System Settings > Online Application.

  2. Enable Enable Work Opportunity Tax Credit (WOTC).

When enabled, a Tax Credit step is added to the online application when a candidate creates an account, and a Tax Credit step appears in the candidate's ProfileClosed The Applicant’s self-service ability to add or update information about themselves (e.g., job preferences, references, education, work history).

Configure the TCC WOTC Blueprint

The BlueprintClosed A set of global document maintained by Bullhorn that client’s can enable as needed. This would include I9, Federal W-4 and State Withholding forms. controls how the TCC iframe behaves during the candidate's onboarding workflow. These settings determine polling behavior and whether candidates must complete the screening before continuing.

  1. Navigate to Settings > Blueprints > 3rd Party > Work Opportunity Tax Credit - TCC.

  2. Configure the following settings:

Setting Recommended Value Details

iFrame URL

:wotc_url_core:

Tells the platform to use the .NET Core API for this integration.

Must Complete to Continue

On

Requires the candidate to finish the WOTC screening before proceeding. Turn off only if the client does not want to require completion.

PollingClosed The automated check to see if any changes have been made in the ATS. If changes have been made, data is retrieved and updated in Onboarding Interval

10 seconds (default)

How often the system checks for a status update from TCC. Lowering this value creates a more real-time feel but increases server load.

Polling Resource

Leave blank

Not used for the TCC integration.

Require Confirmation Code

Off

Must remain off for TCC. Do not enable this setting.

Configure the TCC WOTC Form

The FormClosed Any document that needs to be completed and signed by a Candidate settings should generally match the Blueprint settings unless there is a client-specific reason to adjust them.

  1. Navigate to Settings > Forms > 3rd Party > Work Opportunity Tax Credit - TCC.

  2. Apply the same configuration as the Blueprint above.

Client-adjustable settings include Must Complete to Continue (can be turned off by request) and Polling Interval (can be lowered for a faster experience).

Troubleshooting

If the WOTC iframe does not load or returns an error

Verify the API Base URL matches the correct environment. Production and staging use different URLs. An invalid or mismatched URL is the most common cause of iframe failures. Also confirm the API User and API Password are entered correctly.

If the "Next" button does not enable after the candidate completes the survey

When Must Complete to Continue is on, the system polls for a status update from TCC. If the callback fails, it can take up to 60 seconds for the system to poll TCC directly as a fallback. Wait at least 60 seconds before escalating. If the issue persists, check the Callback URL for the correct environment value.

If the Partner Account Code appears incorrect

The Partner Account Code should match the client's Able Customer ID. Some accounts historically used a different value. Confirm the correct ID and update in both production and staging if needed.

If configuration changes are not taking effect

Clear the cache after making any updates to integration settings, URLs, or Partner Account Codes. Configuration changes may not apply until the cache is refreshed.

If candidates are stuck on the Tax Credit step

Check that Require Confirmation Code is set to Off. This must remain off for TCC integrations. Also verify that the Polling Interval is set appropriately and that the Callback URL is correct for the environment.

If a candidate cannot proceed after completing the WOTC screening as a standalone form

If the WOTC screening was sent as a standalone form and a candidate is blocked from continuing, contact Bullhorn Support to have the form removed so the candidate can proceed with onboarding.Internal Only — Support and SI Partner Reference

FAQs

What is the Partner Account Code, and where do I find it?

The Partner Account Code is typically the client's Able Customer ID. Confirm the correct value with your team before entering it — some legacy accounts may use a different code.

Is the API User and Password unique to each client?

No. The API User and API Password are the same across all TCC integrations. You can copy these values from an existing integration or request them from a developer.

Can I lower the Polling Interval for a faster candidate experience?

Yes, but keep in mind that TCC updates are asynchronous. Lowering the polling interval increases the frequency of server requests and may add load. A slight delay between survey completion and the "Next" button enabling is expected.

Do I need to configure anything beyond the UI settings?

Yes. There are additional database-level configurations required for authentication. Contact your implementation team or Bullhorn Support to confirm these values are in place.

What should I check before escalating a TCC issue?

Verify the API Base URL, Partner Account Code, Callback URL, and Blueprint/Form settings against this article. Clear the cache after any changes. Most TCC issues are caused by misconfigurations in these fields.