Salesforce Loyalty Management: Troubleshooting "Invalid Action Type" and "Invalid Request" API Errors

Loyalty Management API errors are typically caused by one of the following conditions: an unsupported API version, invalid or missing required request parameters, insufficient permissions, or missing licenses. The following sections describe each cause and its corresponding resolution.

Cause 1: API Version Below the Minimum Supported Version

Certain Loyalty Management standard actions and Connect API endpoints are supported only from specific API versions onward. For example, the mergeLoyaltyProgramMembership action is supported beginning with API version 56.0. When the action is called by using API version 55.0 or earlier, the following error is returned:

Invalid Action Type: mergeLoyaltyProgramMembership

Resolution

1. The minimum supported API version for the required action should be identified by reviewing the Loyalty Management REST API documentation in the Salesforce Developer Guide.

2. The API endpoint URL should be updated to use the required or latest supported API version. For example:

   /services/data/v55.0/actions/standard/mergeLoyaltyProgramMembership

   should be updated to:

   /services/data/v56.0/actions/standard/mergeLoyaltyProgramMembership

   or a later supported version.

3. If a Named Credential or another integration configuration is used, the URL path should be updated in Setup > Named Credentials to reference the appropriate API version.
4. The API request should be resubmitted, and a successful response (HTTP 200) should be verified.

Cause 2: Invalid or Missing Required Parameters in Flow Action Calls

When Loyalty Management actions, such as getPointsBalance, are invoked from Flow, the error FlowActionCall: Invalid request for LoyaltyProgramMemberId indicates that one or more required input parameters are null, blank, or contain invalid record IDs. This condition commonly occurs when required values, such as LoyaltyProgramMemberId or ProgramCurrencyName, are not populated by preceding Flow elements, including Get Records or Assignment elements.

Resolution

1. The affected Flow should be opened from Setup > Flows, and the Action element invoking the Loyalty Management action (for example, getPointsBalance) should be located.
2. The LoyaltyProgramMemberId input parameter should be verified to ensure that a valid 18-character Salesforce record ID from the LoyaltyProgramMember object is provided.
3. The ProgramCurrencyName or LoyaltyMemberCurrencyId input parameter should be verified to ensure that a valid value corresponding to an existing Loyalty Program Currency record is supplied.
4. A Decision element should be added before the Action element so that all required input variables are validated for null or blank values. Null values should be routed through an appropriate fault path.
5. If membership information is retrieved by using a Get Records element, the filter criteria should be verified to ensure that exactly one record is returned and assigned correctly.
6. The updated Flow version should be saved and activated.
7. The Flow should be tested by using a known valid LoyaltyProgramMember record ID, and the points balance should be verified to be returned successfully.

Cause 3: Missing Permissions or Loyalty Management License

Loyalty Management API actions and Flow invocable actions require that the Loyalty Management permission set license be assigned to the running user or integration user. If the required license or permissions are not assigned, unknown exception errors or permission-related failures may be returned. Even when a Flow is executed in system context, license validation may still be enforced by the invoked action.

Resolution

1. The availability of the Loyalty Management permission set license should be verified in Setup > Permission Set Licenses.
2. The Loyalty Management permission set should be located in Setup > Permission Sets.
3. The permission set should be assigned to the user executing the API request or to the integration user associated with the Connected App.
4. If the Flow is configured to run as a specific user, the user's Permission Set Assignments should be reviewed to confirm that the Loyalty Management permission set has been assigned.
5. If the Flow invokes actions that require object-level access, the running user's permissions should be verified to ensure that Read access is available for LoyaltyProgramMember, TransactionJournal, Voucher, and any related objects.
6. For voucher redemption scenarios, Create permission on the Voucher and LoyaltyProgramMember objects should also be verified, as documented in the Loyalty Management permission requirements.