PSA: Error: "Web service callout failed: Unable to parse callout response. Apex type not found for element allowGuestPaymentsApi"Feb 24, 2025Knowledge
Content Standard GuideTitlePSA: Error: "Web service callout failed: Unable to parse callout response. Apex type not found for element allowGuestPaymentsApi"URL NamePSA-Error-Web-service-callout-failed-Unable-to-parse-callout-response-Apex-type-not-found-for-element-allowGuestPaymentsApiInformationProduct AreaHelp Product AreaIntegrations - PS CloudRelease VersionHelp Release VersionSymptomsHelp Symptoms Feature Console > PSA Direct for Jira> Create a site and configure settings to enable the connection between Jira with PSA > Perform Step 2. Create Certinia Integration Site: Error: "Web service callout failed: Unable to parse callout response. Apex type not found for element allowGuestPaymentsApi" EnvironmentHelp EnvironmentProfessional Services AutomationAll VersionsResolutionHelp ResolutionStep 1 - Manually Complete Step:To have reached this error, most of the step is complete. All that is needed to do is update the profile for the guest user to add a single Apex classAdd the Apex class 'psaj__IHCJ_RestHandler' to Profile labeled "Certinia Integration Profile". Should allowOnce completed, you can move on to the next step (this step does not have to succeed on the Feature Console - as long as the class is added to the profile) Step 2 - Clear Error to allow Enablement of Feature Console: Use Dev Console and use below query for Feature Console Step Record:Select Id, fferpcore__TargetId__c, fferpcore__Status__c, fferpcore__Enabled__c from fferpcore__FeatureConsoleActivation__c WHERE fferpcore__Enabled__c = falseLook for 'step.psaj___CreateConfigureSite' and change fferpcore__Status__c to 'Success' and fferpcore__Enabled__c to 'True'Verify Feature Console and close Dev Console once complete CauseHelp CauseError happens as Salesforce changes the data returned for the metadata API call that Certinia uses to retrieve the profile of the site guest user for the site we use as a webhook endpoint. When Salesforce adds (or the org shape causes something we’ve not seen before) to that structure, the Salesforce SOAP API stuff crashes out.Additional NotesHelp Additional Notes
Was this article helpful?00Choose a general reason-- Choose a general reason --FeedbackUpload FilesUpload FilesOr drop filesSubmit