To confirm that a Sub User ID is functioning correctly, send multiple test parse requests using the specific Sub User ID and verify its presence in the Parsing Logs section of RChilli MyAccount.
Verification Steps
- Send Parse Requests
- For each client, send 2–3 Parse API calls.
- Include the client’s Sub User ID in the API request payload (use the key subUserId).
- Access Parsing Logs
- Open RChilli MyAccount.
- Navigate to Parsing Logs.
- Locate the most recent entries corresponding to the test parse requests.
- Verify Sub User ID Details
- Each log entry should display the Sub User ID alongside the API call details.
- Confirm that the Sub User ID matches the client used for those requests.
Troubleshooting
- Sub User ID not visible in logs: Re-check your payload key (subuserid, subUserId) and confirm it’s populated.
- Wrong client association: Ensure you’re using the correct User Key and Sub User ID pair for that client.
- No entries in logs: Wait a moment and refresh; if still missing, confirm the parse requests succeeded (200 responses).
Need help? Email RChilli Support or raise a ticket at help.rchilli.com with your payload and timestamps of the test calls.
Comments
0 comments
Please sign in to leave a comment.