Jaggaer iBuy Integration

@dynamic_static most 403 errors for enterprise integrations point to a permissions or authentication mismatch rather than Jaggaer itself, so confirm these common items on the Adobe Sign side: the service account must have API access enabled and a role that permits creating and sending agreements (preferably an account admin or an API-enabled user), the integration key or OAuth client you’re using must be active and granted the correct scopes for Agreements and Webhooks, the integration key must be associated with the same Adobe Sign account that Jaggaer is attempting to call, any IP allowlist or firewall rules for your Adobe Sign account must include Jaggaer’s outbound IPs, the callback/webhook URL configured in Jaggaer must exactly match what’s registered in Adobe Sign (including scheme and trailing slash), and if you’re using a service account in a grouped or delegated setup check that group-level permissions don’t block API calls; if all of the above look correct, collect the failing request details (timestamp, integration key/client id, request endpoint, and full error body) and escalate to Adobe Sign support so they can trace the 403 and confirm whether it’s an account-level policy, an invalid key, or an allowlist/firewall issue.