Spaces

What is a polling?

Polling means checking again and again, on a timer, whether anything new has happened, instead of being told when it does.

In plain words

Imagine walking to the mailbox every ten minutes to see if the post has come. Most trips are wasted, and when the letter does arrive you may be a few minutes late. That is polling.

It is the simplest way for software to stay informed, and it works everywhere. The cost is a trade-off. Check often and you waste effort. Check rarely and you react slowly.

For a business, slow reactions matter most when a customer is waiting. A reply that comes ten minutes late can feel like silence. That is why better options exist, where the service tells your agent the moment something happens.

Polling is not wrong, though. For something that can wait, such as a daily summary, a regular check is perfectly fine and easy to understand. Think of a florist who checks the order book once each morning.

That is plenty for the wedding next week flowers, and it is far too slow for a customer standing at the counter. Match the way of checking to how fast the answer is needed.

How it works in Spaces

Spaces suggests an agent learns about new messages through the event stream, without polling. Reading chats and messages is answered from Spaces' own up-to-date copy, so checking does not put pressure on the platform.

If your agent does check on a timer, it can ask GET /v1/events with a cursor and get only what is new.

Related terms

FAQ

Is polling bad?

No. It is simple and fine when a delay does not matter. For quick replies, an event stream or a trigger is better.

Does polling use up my sending limits?

Reading is separate from sending. Reading does not use up the limit on writing messages.

What should my agent use instead?

The event stream, with wait_for_events, or a webhook that pushes events to a web address.

Useful next: Triggers, API reference, Sending limits. Every term: the glossary.