Why REST API Date/Time Values Differ from the Jama Connect UI

Published Date: April 14, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered:

Jama Connect® all versions
Cloud/CVC
Self-hosted

IMPORTANT: Access to the REST API is limited to users with a Named Creator Jama Connect license, including access to v1, labs, and SCIM endpoints. Users without a Named Creator Jama Connect license, including those with a Creator Float License, do not have access.

Summary

This article explains why date and time values returned by the Jama Connect REST API may differ from what is displayed in the user interface (UI).

Jama Connect server logs and REST API responses use the UTC / UTC+0 timezone when recording and returning date and time values. In contrast, the UI displays dates and times based on the end user’s local system timezone.

This difference in time zones can cause timestamps from the API to appear offset (for example, UTC vs. EST), even though they represent the same point in time.

Resolution

Understand timezone behavior

Be aware that the Jama Connect REST API returns all date and time values in the UTC timezone. This is consistent with how timestamps are recorded in server logs.

The UI, however, automatically converts and displays these values based on the user’s local system timezone, which may result in apparent differences.

Convert API timestamps to local time

To align API data with what is shown in the UI, convert the returned UTC timestamps to your local timezone (for example, EST or your system’s configured timezone).

This conversion can be done using standard date/time handling tools or libraries in your integration or reporting solution.

Validate time comparisons

When comparing timestamps between the API, logs, and UI, ensure that all values are converted to the same timezone before drawing conclusions.

This helps avoid confusion when validating events, troubleshooting issues, or auditing system activity.

Prevent confusion in integrations

If you are building integrations or reports using the Jama Connect REST API, standardize on a single timezone (commonly UTC) or ensure consistent conversion logic is applied across systems.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to