GET SCIM Sync Logs

How it works

Use the GET method to retrieve the SCIM synchronization logs:

GET /admin/scim-sync/logs

Authentication

The JSESSIONID value is used to authenticate all API calls, not the API key. The API key is only used in the authentication call.

For more information, see Authentication.

GET operation parameters

This command takes the following parameters:

Object	Type	Required	Description
`account`	String	Required	The unique identifier for the account.
`utk`	String	Required	The user token for authentication.
`from`	String	Optional	The start of the time range for the logs in ISO 8601 format. The default value is 30 days ago.
`to`	String	Optional	The end of the time range for the logs in ISO 8601 format. The default value is the current date and time.
`status`	String	Optional	The status of the synchronization. For example, `SUCCESS` and `ERROR`.
`action`	String	Optional	The action performed during the synchronization. For example: `User OOO`, `User Patch`, `User Update`, `User Creation`, `User Deletion`, and `User Retrieval`.
`source`	String	Optional	The source of the synchronization request. For example, `SCIM_API`.
`userEmail`	String	Optional	The email address of the user. This value is a case-insensitive substring.
`correlationId`	String	Optional	The correlation ID for the request.
`format`	String	Optional	The response format. Allowed values are `csv` and `json`. The default value is `csv`.
`limit`	String	Optional	The maximum number of log entries to return. The default value is `1000` and the maximum value is `5000`.

Example cURL request

curl --location --request GET 'https://my.tealiumiq.com/urest/admin/scim-sync/logs?account={ACCOUNT}&from=2023-10-01T00:00:00Z&to=2023-10-31T23:59:59Z&limit=100&format=json&utk=01234567890012345678901234567890'

Example response

Expand to view code snippet

timestamp	action_type	resource_type	target_email	target_first_name	target_last_name	target_user_uuid	http_status	outcome	correlation_id	account_name	error_message
2025-10-13 23:01:15.684Z	User Creation	USER	test.userXZ4@example.com	Test	User		409	ERROR	a211d118-f6db-49ec-8a85-05f46742954d	admin1	User already exists in the given account.
2025-10-13 22:51:57.472Z	User Patch	USER	test.userxz4@example.com		User	aa580e7f-569c-460e-b7e0-a73416161949	200	SUCCESS	019f36c9-3018-418c-b877-41450d845fca	admin1
2025-10-13 22:51:53.201Z	User Patch	USER	test.userxz4@example.com	john	User	aa580e7f-569c-460e-b7e0-a73416161949	200	SUCCESS	10120449-3901-4889-b18c-aedeed1a7d88	admin1
2025-10-13 22:47:00.753Z	User Patch	USER	test.userxz4@example.com	john	User	aa580e7f-569c-460e-b7e0-a73416161949	200	SUCCESS	0e79ebfd-76f0-40f9-8e6e-20f105b53e46	admin1
2025-10-13 22:46:54.604Z	User Update	USER				aa580e7f-569c-460e-b7e0-a73416161949	400	ERROR	c9f40bc4-62da-4d10-8fe5-08fddf4686cd	admin1	userName is required.

Error messages

Potential error messages for this endpoint:

Error code	Error message
400	`400 Bad Request: "message": "Account parameter is required."`
401	`400 Bad Request: "message": "Authentication failed"`
403	`403 Forbidden "message": "Unauthorized access."`
405	`405 Invalid Method "message": "Method is not allowed on this endpoint. Allowed methods: GET."`
500	`500 Internal Server Error "message": "Error processing json for extension - account {ACCOUNT}"`