A successful HTTP response confirms that Insider One received your request. It does not always confirm that every record was written. Test each User Data API with one user before you send a batch.
Use one test user and a unique identifier, such as a test email address, so you can find the profile quickly.
Check the result in the InOne panel
Go to Audience > User Profiles.
Search for the identifier you sent, such as the email address, phone number, or UUID.
Open the profile and check the tab that matches your call:
API | What to check |
|---|---|
Overview tab: attributes and identifiers match the request. Events tab: the event appears with Platform: API. | |
The attributes in the response match the Overview tab. | |
Insider One sends the download link to your hook URL, and the test user appears in the file. The file has one row for each user event, so the number of rows equals the number of events, not the number of profiles. A 200 response only means the export was queued. | |
The attribute no longer appears on the Overview tab. If your source keeps sending the attribute, Insider One writes it back, so stop sending it from the source first. | |
Update and Delete Identifiers API | The identifier is added to or removed from the profile. You cannot delete the only identifier of a user, so give your test user at least two identifiers, such as an email address and a phone number, before you test the delete. |
If the profile is missing, wait a few minutes and search again. Then check the response for a data.fail entry.
Time to live (TTL) applies to users and events, not to attributes. Insider One calculates the event TTL from the event timestamp, so an event with an old timestamp may be missing from the profile. Use a current timestamp when you test events.
Interpret an Upsert partial success response
The Upsert API returns 200 when it processes the request, even if some users failed. Read data.successful and data.fail in every response.
Field | Meaning | What to do |
|---|---|---|
data.successful.count | Number of users written. | Compare with the number of users you sent. |
data.fail.count | Number of users that failed validation. | If it is greater than zero, read data.fail.errors. |
data.fail.errors | Errors keyed by the path of the failed field, e.g., users.0.identifiers.required. | Fix the field at that path and resend only the failed users. |
Validation errors are returned only in data.fail in the response. If you set error_callback_endpoint, Insider One calls that URL only for unification errors, even when the response is 200 and successful. Check your server log when you expect a unification error.
Reproduce a failure in Postman
Open the endpoint page and select Run in Postman. The Insider One Postman documentation opens at that endpoint.
In the top right corner of the Postman documentation, select Run in Postman.
In the Fork collection into your workspace window, select Fork Collection. Postman opens the collection in the Postman app or in your browser.
Select the environment that holds your API key and partner name.
In the Body tab, select raw and paste the payload that failed.
Select Send and compare the response with the one from your integration.
Reduce the payload to one user, then add fields back until the error returns.
Remove the API key and personal data before you share the request or response.
To trigger a known error on purpose, remove both insider_id and identifiers from a user. The response returns 200 with an entry in data.fail.errors.
For more information, see Insider One APIs in Postman and API Status and Error Codes.