Hourglass Content Intelligence
Website ↗
← All conversations

Conversation

20 Oct 2026, 01:16 UTC · 1 question · ID cd8badafa84f
Who asked
Profile
We don’t have a profile for this visitor.
Question 1

“What should my code do when the API returns 429?”

Answer
Not answered

The site never mentions the Hourglass API, its rate limits or what happens when a limit is exceeded. Nothing explains what a 429 response contains or how code should wait and retry.

Section on the siteStatusTicket
/products/dataThe tools in Data HubMissing here
Add an API limits and error handling section to /products/data

Ticket

Paste this into your ticketing tool.

Add an API limits and error handling section to /products/data

Who needs it: Developers building integrations with the Hourglass API
Section: /products/data › The tools in Data Hub

What is missing:
- Requests allowed per plan are not stated.
- What a 429 response contains, such as headers showing when to retry, is not described.
- Recommended retry behaviour after a 429 is not explained.

Where: New section on /products/data, placed after "Data your teams and agents can rely on".
  Related sections: The tools in Data Hub · Data syncs · Two-way syncs, without custom code
  Main topics: API rate limits by plan · What a 429 response returns · Waiting and retrying after a limit · Where to find full API documentation

What to do:
1. Confirm with engineering the rate limits per plan, the contents of a 429 response and the recommended retry approach.
2. Add the new section with the confirmed limits and retry guidance, linking to the API documentation if one exists.

Done when: /products/data states the API rate limits and explains what a 429 response means and how to retry.

From: conversation cd8badafa84f, question 1: "What should my code do when the API returns 429?"
Who needs it: Developers building integrations with the Hourglass API
What is missing
  • Requests allowed per plan are not stated.
  • What a 429 response contains, such as headers showing when to retry, is not described.
  • Recommended retry behaviour after a 429 is not explained.
Where
New section on /products/data, placed after "Data your teams and agents can rely on".
Related sections
The tools in Data Hub · Data syncs · Two-way syncs, without custom code
Main topics
API rate limits by plan · What a 429 response returns · Waiting and retrying after a limit · Where to find full API documentation
What to do
  1. Confirm with engineering the rate limits per plan, the contents of a 429 response and the recommended retry approach.
  2. Add the new section with the confirmed limits and retry guidance, linking to the API documentation if one exists.
Done when: /products/data states the API rate limits and explains what a 429 response means and how to retry.
/resourcesGuides to get you startedMissing here
Add an API rate limits guide card to /resources

Ticket

Paste this into your ticketing tool.

Add an API rate limits guide card to /resources

Who needs it: Developers building integrations with the Hourglass API
Section: /resources › Guides to get you started

What is missing:
- No guide covers the API, its rate limits or handling 429 responses.

Where: Update this section: add a fifth card beside "Your first day", "Moving from your current CRM", "How agents work in Hourglass" and "Security and control".

What to do:
1. Add a guide card on API rate limits and retry handling with three short points.
2. Link the card to the new API limits section on /products/data.

Done when: /resources shows a guide card on API rate limits that links to the API limits section.
Depends on: Add an API limits and error handling section to /products/data

From: conversation cd8badafa84f, question 1: "What should my code do when the API returns 429?"
Who needs it: Developers building integrations with the Hourglass API
What is missing
  • No guide covers the API, its rate limits or handling 429 responses.
Where
Update this section: add a fifth card beside "Your first day", "Moving from your current CRM", "How agents work in Hourglass" and "Security and control".
What to do
  1. Add a guide card on API rate limits and retry handling with three short points.
  2. Link the card to the new API limits section on /products/data.
Done when: /resources shows a guide card on API rate limits that links to the API limits section.
Depends on: “Add an API limits and error handling section to /products/data”
Answer full page
When the API returns a 429, your code has gone over the rate limit and should wait before retrying. The docs article below explains what the response contains and how to retry.
Sections in the answer pageStatus
/products/dataThe tools in Data HubMissing here
/resourcesGuides to get you startedMissing here

Questions and answers are shown as recorded. Status, what is missing and what to do are our analysis of the live site, read 22 Oct 2026.