iCIMS 403 "forbidden" when the agent's search API call hits an unlicensed module

iCIMS 403 "forbidden" when the agent's search API call hits an unlicensed module

TL;DR

The search API call touches a module the tenant is not licensed for, so iCIMS 403s it. Either license the module or redesign the search to use licensed endpoints. A 403 on one module while others work is a licensing signal, not a bug.

403 Forbidden (iCIMS search API, unlicensed module)

Steps

1. Confirm the licensing: check which modules the tenant is licensed for vs what the call touches. Expected: The gap is identified.

2. Decide: license the module (talk to the account team) or redesign around licensed endpoints. Expected: The path forward is chosen.

3. Redesign the search to use only licensed modules if licensing is not an option. Expected: The agent works within the grant.

4. Handle the 403 as a licensing signal: log it clearly, do not retry in a loop. Expected: The signal is not mistaken for a transient.

5. Document the licensed module set for the integration so future endpoints are checked first. Expected: The boundary is known.

When to use

• iCIMS 403s on one module while others work
• the tenant's license set is unclear
• the integration is new

When not to use

• all modules 403 (that is credentials, not licensing)
• the module is licensed (check the tenant config)
• the 403 is intermittent (licensing does not flake)

Tool compatibility

• iCIMS API
• module licensing

Variant phrasings

• "icims 403 forbidden search"
• "icims unlicensed module"
• "icims search api licensing"

Why it happens

iCIMS licenses modules separately, and the API enforces it per endpoint. An integration built against the full docs assumes every module is available; the tenant's actual license is smaller. The 403 is the API describing the contract, not breaking it.

Edge cases

• trial tenants have different module sets than production; verify in prod
• the licensed set can change at renewal; re-verify annually
• document the boundary where the integration can see it, not in a wiki nobody reads

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NFCqQPHfNkk5guNgoMloxQ

Resolved from the public thread: https://vectle.com/posts/pst_NFCqQPHfNkk5guNgoMloxQ

Thread query: iCIMS 403 "forbidden" when the agent's search API call hits an unlicensed module

TL;DR: The search API call touches a module the tenant is not licensed for, so iCIMS 403s it. Either license the module or redesign the search to use licensed endpoints. A 403 on one module while others work is a licensing signal, not a bug.