Overview
The error "Influitive API not working for reward redemption fulfill" occurs when there is incorrect use of UUID in the API call. This is not a defect but a user error in API usage. Correcting the UUID usage resolves the issue.
Information
Error Message: "Influitive API not working for reward redemption fulfill"
Cause: Incorrect use of UUID in the API call for reward redemption fulfill.
Resolution Steps:
-
Verify the UUID:
- Ensure you are using the correct UUID for the reward redemption.
- Fetch the correct UUID using the following CURL command:
curl --location 'https://api.influitive.com/reward_redemptions' \ --header 'Authorization: Token <your_token>' \ --header 'X_ORG_ID: <your_org_id>' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json'
-
Correct the API Call:
- Use the correct UUID in your API call for reward redemption fulfill:
curl --location --request POST 'https://api.influitive.com/reward_redemptions/<correct_uuid>/decision/fulfill' \ --header 'Authorization: Token <your_token>' \ --header 'X_ORG_ID: <your_org_id>' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json'
- Use the correct UUID in your API call for reward redemption fulfill:
-
Verify Resolution:
- Execute the corrected API call.
- Confirm that the reward redemption is processed successfully without errors.
Note: Ensure that all headers and tokens are correctly configured in your API call.
Frequently Asked Questions
- How do I know if I'm using the correct UUID?
- You can fetch the correct UUID using the provided CURL command to list reward redemptions and ensure you are using the correct one in your API call.
- What should I do if the API call still fails after correcting the UUID?
- Double-check all headers, tokens, and ensure the UUID is correctly placed in the API call. If issues persist, contact support with details of your API call and any error messages received.
- Is this a defect in the API?
- No, this is not a defect. The issue arises from incorrect usage of the API, specifically the UUID. Correcting the usage resolves the issue.
Priyanka Bhotika
Comments