As the next step in our process to improve UserID support across the Iterable platform, all of our API endpoints that require a user parameter now also accept UserID - in addition to email. This new option will:
- Minimize security risk by removing the need to pass email (PII)
- Streamline implementation for customers who commonly leverage UserID in their own internal systems
- Provide more flexibility with APIs in Iterable
Things to know:
- All API endpoints that reference a user now accept UserID or email.
- You can choose whether to pass email or userID.
- If you pass both values in the request, the system will prioritize email and discard the UserID.
- Current projects do not enforce uniqueness on UserID, so it's possible that your project may have duplicate UserIDs. If this is the case and UserID is passed in an API request, we will take action on the first user profile returned with that UserID.
- If a project includes duplicate UserIDs, we recommend passing email to ensure the right user is updated via the API.
Check out the updated API docs and support docs and reach out to your Customer Success Manager with any questions. Thanks!