Automation for clients

Stage 1 · Lesson 8 of 8

Rate limits and quotas

How automation works

cap how many requests you can send, such as 100 per minute or 10,000 per day. This cap is called a . Go over it and the API answers 429 Too Many Requests.

A workflow that loops through 2,000 contacts can hit that in seconds. So read each API's limits first. Process large lists in batches: small groups, with a short wait between them.

If the API sends a Retry-After , it is telling you how long to wait, so respect it. Your automation tool also has its own limits and billing units, which you will meet in the next stage.

Common traptesting with five records, going live with five thousand and watching the workflow fail halfway through, leaving half the records updated and half not.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with· follow one of these

  • GuideFree
    MDN: HTTP

    Mozilla · Beginner

    Read the overview, methods, status codes and headers pages: the HTTP every automation tool sits on

  • GuideFree
    JavaScript.info

    Ilya Kantor

    The JSON methods and objects chapters teach you to read and reshape the data each step passes on

Practise

  • Call real APIs by hand, see status codes and headers, before you build anything around them

  • Get a throwaway URL and see exactly what an app sends in a webhook

Keep handy

  • A map of API concepts, from REST and auth to rate limiting, to check what you have not met yet

  • Clear chapters on OAuth flows and scopes for when "Connect your account" stops being magic

Also worth your time

Mark this stage as not done?