Image
Dot. Manual
Image
Dot. Manual
Back to home

Dot.

Install Dot. AppDiagnostic Tool

Quote

Quote/0New
Pairing Quote/0How to TapShare with Family and FriendsHow to Charge
Content Mode
Loop ContentFixed Content
TimingNewApp Clip and Tap-to-InteractNew
Screen States and Troubleshooting
Update DeviceReset NetworkReset DeviceChangelogNew
Service and RepairCustomize Quote/0

Rand

Rand/0New
Getting StartedNew
FeaturesNew
Book of AnswersFortuneMBTI GuideWooden FishCoin FlipBluetooth RemoteNewPomodoroNewClockTimerNewDice RollNumber Under TenDisplay ModeNewNFC Cards
Wi-FiCustom WallpaperSettingsHow to Charge
Update DeviceReset DeviceChangelogNew
Service and RepairCustomize Rand/0

Read

Read PicoNew
Getting StartedNew
CrossMuxNewkiikoreadNewRickyOSNewWhiteOSNewCrossLinkNewJust ReadNewPico PageNewAuraReaderNewPageRestNewif-ink OSNewThingsOSNewTake EasyNewVanOSNewCPYOSNewYanReaderNewFolio BookNewXH View OS For PicoNew
Demo SystemDIY Your System

Clock

ClockNew
Getting StartedDIY Your System

Content & Services

Roadmap
Content Studio
Join Content StudioRSS
Shortcuts
Co CreateNew
SoftwareNew
QuoteNew
Rand
ReadNew
ClockNew
HardwareNew
Quote
Rand
ReadNew
Open PlatformNew
What is an APIDot SkillNewGet API KeyGet Device Serial NumberUnderstand API rate limitsNewGet Device ListGet Device StatusGet TimezonesDevice SettingsSwitch to Next ContentList Device ContentControl Text ContentControl Image ContentControl Canvas Content

Explore More Possibilities

Request New ContentJoin Content StudioOur Repositories

Security

Responsible Disclosure Policy

More

Service StatusService and RepairCustomize ProductsPrivacy PolicyUser AgreementContact UsAbout MindReset
Content & ServicesOpen PlatformNew
Image

Understand API rate limits

RSSImprove this page

An API rate limit caps how many requests the server accepts in a given amount of time.

You can use one API key to request an immediate refresh on three devices at the same time. Say you ask the living room device to display a text card immediately, then ask it to display an image one second later. The second request hits the rate limit because immediate refresh requests for the same device must be at least two seconds apart.

Understand requests and rate limits

  • Immediate refresh. Each device accepts one immediate refresh request every two seconds. Text, Image, and Canvas requests that refresh immediately share this limit with requests to switch to the next item. Each device has its own cooldown.
  • HTTP requests. Each client IP can send up to 10 requests per second to the same path. Programs using the same public IP share those 10 requests when they access the same path.

Which operations count toward each limit

In the two seconds after requesting an immediate refresh, you can still check the device status, update settings, or save content for later.

OperationImmediate refresh limitHTTP request limit
Write loop content and request an immediate refresh (taskType: "loop" and refreshNow: true, both defaults)CountsCounts
Switch to the next itemCountsCounts
Save loop content only (taskType: "loop" and refreshNow: false)Does not countCounts
Save fixed content only (taskType: "fixed" and refreshNow: false)Does not countCounts
Read the device list, device status, content list, device settings, or timezonesDoes not countCounts
Update device settingsDoes not countCounts
The device displays fixed content on its own scheduleDoes not countDoes not count

refreshNow controls immediate refresh for loop content only. Fixed content follows the device schedule, so you can omit refreshNow when saving it.

For example, one public IP can make up to 10 status requests per second for the living room device. The bedroom device has a different status path and a separate limit. Requests with different query parameters still count toward the limit for the same path.

How to handle a 429 response

HTTP 429 Too Many Requests means the request was rejected because it arrived too soon. Wait the number of seconds in the Retry-After header, then send the request again. For example, Retry-After: 1 means wait one second.

If a write hits the device refresh limit, the server rejects it before saving the content. The response body also provides the wait time.

{
  "code": "RATE_LIMITED",
  "message": "Refresh requests for this device are too frequent. Try again in 1 second.",
  "retryAfter": 1
}

Did this solve your problem?

Join our community

Get Device Serial Number

Retrieve the device serial number from the Dot. App to use Dot.'s API features in other applications.

Get Device List

Next

Contents

Understand requests and rate limitsWhich operations count toward each limitHow to handle a 429 response