How can a 403 Forbidden error be resolved when testing the GET Candidate Detail API in Oracle Recruiting Booster?

 A 403 Forbidden error usually indicates an authorization, permission, IP access, account configuration, or environment-related issue.

Follow the steps below to identify and resolve the issue.

Step 1: Check API Credentials and Token Validity

Verify the API credentials and token.

• Confirm that the API key is correct.
• Confirm that the API token is active and has not expired.
• Regenerate the API token if required.
• Retest the API with the updated credentials.

Step 2: Verify Permission Scope

Check the permissions and scopes assigned to the API credentials.

Required access should include:

• GET Candidate Detail
• Candidate List

If required permissions are missing, update the API credentials or Oracle role configuration and retest the API.

Step 3: Review IP Whitelisting

Verify that the public IP address used for the API request is allowed.

• Identify the public IP address used for the request.
• Check the allowed IP list.
• Add the IP address to the whitelist if it is missing.
• Retest the API after the IP address is added.

Step 4: Check Account-Level Configuration

Open MyAccount settings and verify the integration configuration.

Confirm that:

• Oracle Recruiting Booster is configured correctly.
• API access is enabled.
• No account-level restriction is blocking API access.
• The correct Userkey and integration credentials are configured.

Step 5: Check Environment-Level Access

Confirm that the API request is being sent to the correct environment.

Common environments include:

• Production
• Sandbox

The API credentials, endpoint, and integration configuration must belong to the same environment.

Step 6: Review API Logs

If the 403 error continues:

• Check API request and response logs.
• Review available error details.
• Confirm that the request is reaching the expected environment.
• Check for temporary access restrictions or system-wide issues.

Step 7: Escalate the Issue

After completing all checks, test the GET Candidate Detail API again.

If the error remains, escalate the issue to the RChilli Support Team with the following information:

• API endpoint
• Environment name
• Request timestamp
• HTTP status code
• Request and response details
• Relevant API logs

Related Documentation

• Oracle API Details
• Create a Custom Role in Oracle
• RChilli Oracle Client ID for Recruiting Booster
• RChilli AI Agents for Oracle Recruiting Cloud
   

Note

Regular checks of API credentials, permission scopes, IP whitelisting, account configuration, and environment access can help prevent authorization errors in Oracle Recruiting Booster integrations.

For more information, contact RChilli Support.