How to Resolve {"delay":"0"} Responses on Jama Connect® REST API Calls

Published Date: August 19, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered:

Jama Connect® version(s)
- Cloud/CVC

IMPORTANT: Access to the REST API and the Jama Connect Cloud MCP Server is restricted to users with a Named Creator Jama Connect license, which includes access to v1, Labs, and SCIM endpoints. Users without a Named Creator license—including those with a Creator Float license—do not have access.

Summary

This article explains why some Jama REST API calls can return {"delay":"0"} and how to fix it quickly. The issue occurs when network security or proxy tools intercept requests before they reach Jama, usually on a specific client path (for example, Postman on a corporate network). In these cases, Jama does not receive the request, so no Jama-side API error appears. You can resolve the issue by allowlisting Jama API domains and paths in your network controls.

Resolution

Resolve the current issue

Confirm the response includes {"delay":"0"} and check response headers for intermediary services (for example, Cloudflare or Envoy). This confirms the request likely did not reach Jama.
Have your network or security team allowlist the Jama API domains and REST paths used by your automation and API clients.
Retry the same request after allowlisting. If the call succeeds, the interception path was the root cause.

Prevent the issue from happening again

Keep Jama API domains and routes permanently allowlisted for all approved API clients, including automation tools.
Standardize API traffic through a validated network path and avoid unapproved proxy inspection for Jama API calls.
If the issue returns, capture the timestamp, endpoint, full response headers, and response body, then share them with Jama Support to speed up confirmation and resolution.

Additional Resources

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

Related to