Daylite WebsiteMarketcircle Blog
Discussions

Discussions

Ask a Question
Back to all

**Daylite REST API — Intermittent HTTP 504 Gateway Timeout Using Make Integration**

2 days ago by Bob Rinaldi

Subject: Daylite REST API — Intermittent HTTP 504 Gateway Timeout Using Make Integration

Hello Daylite API Engineering Team,

Daylite Support directed us to this developer forum for assistance investigating an API connectivity problem.

Rinaldi Advisory Services is developing a supervised, approval-based CRM data-quality integration using Daylite's REST API and Make. We have successfully performed numerous controlled Daylite operations, but an intermittent API timeout is preventing us from completing validation of our automated workflow.

Technical details

  • Date of failure: October 22, 2026
  • API host: api.marketcircle.net
  • Endpoint: GET /v1/companies/{company_id}
  • Integration: Make's native Daylite "Make an API Call" module
  • Response: HTTP 504 Gateway Time-out
  • Response format: HTML error page generated by nginx
  • Elapsed time: 30.2 seconds
  • Subsequent Make error: Response parsing failure because HTML was returned instead of the expected API response
  • Authentication: No explicit HTTP 401 or 403 response was received
  • CRM modifications: None. The failure occurred during a read-only company retrieval, before any contact-creation request was attempted.

We understand that Daylite reported an API/network incident beginning October 16, which was marked resolved on October 18. Our failure occurred afterward, on October 22.

Questions for the API engineering team

  1. Gateway timeout: Can you determine whether this request reached Daylite's API infrastructure and whether the HTTP 504 originated from Daylite's gateway, an upstream service, or an intermediary?

  2. Timeout behavior: Is there a documented 30-second timeout applicable to company retrieval requests through the Daylite API or Make integration?

  3. Endpoint performance: Are there any known circumstances in which GET /v1/companies/{company_id} can take more than 30 seconds, including company relationships or other linked data?

  4. Make integration: Are you aware of intermittent gateway timeouts involving Make's native Daylite "Make an API Call" module? Is there a preferred configuration or supported alternative for reliable company retrieval?

  5. Diagnostic information: What request identifiers, timestamps, response headers, or sanitized execution details would help your engineers trace this specific failure?

  6. Safe retry behavior: For read-only GET requests, what retry and timeout-handling practices do you recommend? For future contact PATCH and POST requests, is there a supported method to determine whether a request committed successfully when the client times out?

  7. API service reliability: Have there been any API gateway or upstream-service incidents after October 18 that might explain this October 22 failure?

Our integration uses exact CRM record IDs, explicit approval controls, pre-update backups and independent post-write verification. We are deliberately holding further API write testing until we better understand the timeout.

We would appreciate guidance on the likely cause and the most reliable supported implementation approach.

Thank you,

Rinaldi Advisory Services