[{"data":1,"prerenderedAt":694},["ShallowReactive",2],{"developers:\u002Fdevelopers\u002Frate-limits":3},{"doc":4,"lang":385,"nav":396,"alternatePath":501,"policy":502,"specVersion":546,"reference":547,"layout":683,"toc":684,"prev":691,"next":692,"operations":693,"overview":7,"heroExample":7},{"id":5,"title":6,"apiTag":7,"body":8,"description":382,"draft":383,"extension":384,"lang":385,"meta":386,"navTitle":7,"navigation":387,"order":388,"path":389,"rawbody":390,"section":391,"seo":392,"stem":393,"translationKey":394,"version":7,"__hash__":395},"developers_en\u002Fdevelopers\u002Frate-limits.md","Rate limits",null,{"type":9,"value":10,"toc":370},"minimark",[11,28,41,46,49,124,135,139,159,162,207,216,235,238,249,252,255,268,272,280,310,326,330,338,341,345],[12,13,14,15,19,20,23,24,27],"p",{},"Each key has two limits, shared by every team it reads: a ",[16,17,18],"strong",{},"rate limit"," on how fast it reads, and a ",[16,21,22],{},"daily quota"," on how much. Both count ",[16,25,26],{},"items",", not requests. An item is one object in a response: a feed page of 100 changes is 100 items, removals included.",[29,30,33],"dev-callout",{"title":31,"type":32},"Approximate during the Beta","note",[12,34,35,36,40],{},"In the Beta, each server that answers your requests counts these limits, and the lockout after failed attempts, on its own, and a restart starts its count again. So the numbers on this page are approximate: a key can sometimes read more, and a request refused with ",[37,38,39],"code",{},"429"," can succeed when it is retried. Design your integration for the numbers on this page.",[42,43,45],"h2",{"id":44},"two-limits-per-key","Two limits per key",[12,47,48],{},"Which requests count toward which limit:",[50,51,52,68],"table",{},[53,54,55],"thead",{},[56,57,58,62,65],"tr",{},[59,60,61],"th",{},"Requests",[59,63,64],{},"Rate limit",[59,66,67],{},"Daily quota",[69,70,71,93,113],"tbody",{},[56,72,73,88,91],{},[74,75,76,77,80,81,84,85],"td",{},"The changes feed, every list, a lead's activities, ",[37,78,79],{},"GET \u002Fv1\u002Fteams",", ",[37,82,83],{},"GET \u002Fv1\u002Fmembers"," and ",[37,86,87],{},"GET \u002Fv1\u002Fbooking_services",[74,89,90],{},"Yes",[74,92,90],{},[56,94,95,108,110],{},[74,96,97,98,101,102,84,105],{},"A request for one record, such as ",[37,99,100],{},"GET \u002Fv1\u002Fleads\u002F{id}",", and also ",[37,103,104],{},"POST \u002Fv1\u002Fleads\u002Fsearch",[37,106,107],{},"GET \u002Fv1\u002Fme",[74,109,90],{},[74,111,112],{},"No",[56,114,115,120,122],{},[74,116,117],{},[37,118,119],{},"GET \u002Fv1\u002Fhealth",[74,121,112],{},[74,123,112],{},[12,125,126,127,130,131,134],{},"Each endpoint in the reference shows its row: ",[16,128,129],{},"Sync"," for the first, ",[16,132,133],{},"Read"," for the second.",[136,137,64],"h3",{"id":138},"rate-limit",[12,140,141,142,146,147,150,151,154,155,158],{},"A key reads up to ",[143,144],"api-const",{"name":145},"SYNC_VELOCITY.perMinute"," items a minute, with bursts of up to ",[143,148],{"name":149},"SYNC_VELOCITY.burst",". Capacity you do not use builds back up at that pace until the burst is full again. Past the limit, the API answers ",[37,152,153],{},"429 rate_limited",", and ",[37,156,157],{},"Retry-After"," says how long until there is room for your request.",[12,160,161],{},"How a request counts:",[163,164,165,180,191,201],"ul",{},[166,167,168,169,172,173,175,176,179],"li",{},"Before it runs, a request reserves its ",[37,170,171],{},"limit",". A list or feed request that sends no ",[37,174,171],{}," reserves ",[143,177],{"name":178},"PAGE_LIMIT.default","; a request for one record reserves one.",[166,181,182,183,186,187,190],{},"Once it has run, it is charged for the items it returned, and at least one. A short page gives back the difference, but a request that returns nothing still costs one item: a search that finds no lead, an id that answers ",[37,184,185],{},"404",", or any other error it gets once it runs, ",[37,188,189],{},"quota_exceeded"," included.",[166,192,193,194,197,198,200],{},"A request refused before it runs is not charged, such as a failed authentication, a missing permission or, on a route that takes ",[37,195,196],{},"Totem-Team",", a team the key cannot read or that is not ready yet. A request that names a record by its id, such as ",[37,199,100],{}," or a lead's activities, checks its team as it runs, so a refusal for that team costs one item.",[166,202,203,204,206],{},"A request for one record is charged for what it returns: ",[37,205,100],{}," returns a lead with its two facets, so it counts up to three items. A search counts each lead it returns, or one when it finds none.",[12,208,209,210,212,213,215],{},"Because a request reserves its full ",[37,211,171],{}," first, a smaller ",[37,214,171],{}," lets you keep reading when little capacity is left.",[12,217,218,220,221,223,224,228,229,234],{},[37,219,153],{}," can also mean that your IP address or your key is locked out after too many failed authentication attempts. ",[37,222,157],{}," tells the two apart: a lockout always sends ",[143,225],{"name":226,"divide":227},"AUTH_FAILURE_LIMITS.banMs","1000"," seconds, the full length of the lock, while the rate limit asks for the few seconds your request needs. Slowing down does not end a lockout: find the process at that address that sends a missing, malformed, wrong or unknown key, fix it, then wait. ",[230,231,233],"a",{"href":232},"\u002Fdevelopers\u002Fauthentication#failed-attempts","Authentication"," explains what counts as a failed attempt.",[136,236,67],{"id":237},"daily-quota",[12,239,240,241,244,245,248],{},"Each UTC day, a key can read ",[143,242],{"name":243},"SYNC_DAILY_BUDGET.floor"," items, or ",[143,246],{"name":247},"SYNC_DAILY_BUDGET.recordsMultiplier"," times the number of records in its teams if that is more. Records of every kind count toward that number, removals included. Every item returned by the requests in the first row of the table counts toward the quota, whatever its kind.",[12,250,251],{},"The number of records is taken at the key's first request of each UTC day, so a team added to the key later that day may raise the quota only from the next day. Plan the initial sync of a large team for when its quota allows it.",[12,253,254],{},"The quota leaves room for an initial sync of every team and a day of polling. Re-reading whole lists again and again is what spends it.",[12,256,257,258,261,262,264,265,267],{},"Past the quota, those requests answer ",[37,259,260],{},"429 quota_exceeded"," until 00:00 UTC, when the quota resets. ",[37,263,157],{}," counts the seconds until then. Requests for one record, search and ",[37,266,107],{}," keep working.",[42,269,271],{"id":270},"retry-after-a-429","Retry after a 429",[12,273,274,276,277,279],{},[37,275,157],{}," comes with every ",[37,278,39],{}," the API itself returns, and it is always a whole number of seconds. Wait at least that long, then send the same request again, with the same cursor. Nothing is lost while you wait: the feed keeps every change for you.",[163,281,282,296],{},[166,283,284,285,288,289,291,292,295],{},"After ",[37,286,287],{},"rate_limited",", the wait is usually a few seconds, or ",[143,290],{"name":226,"divide":227}," seconds after an ",[230,293,294],{"href":232},"authentication lockout",".",[166,297,284,298,300,301,305,306,309],{},[37,299,189],{},", the wait runs until 00:00 UTC and can last hours. Do not keep a process asleep that long: end the run, and schedule the next one for that time. The ",[230,302,304],{"href":303},"\u002Fdevelopers\u002Fsync#tested-reference-client","reference client"," does this with its ",[37,307,308],{},"retry_later"," outcome.",[12,311,312,313,315,316,318,319,322,323,325],{},"A ",[37,314,39],{}," from the firewall in front of the API has no ",[37,317,157],{}," and no JSON error body: back off exponentially. A ",[37,320,321],{},"5xx"," carries no ",[37,324,157],{}," either: retry it with exponential backoff too.",[42,327,329],{"id":328},"initial-sync-estimates","Initial sync estimates",[12,331,332,333,337],{},"The table gives the minimum time the rate limit adds to an initial sync at the limits on this page, for one key with no other traffic; during the Beta it is approximate, as the note at the top of this page explains. It counts records of every kind, one item each: a lead with its attribution, its response and three activities is six records. Network time, and the time Totem needs to prepare a team just added to a key, come on top. A copy that fits within the burst shows ",[334,335,336],"em",{},"Under 1 minute",": the rate limit adds nothing to it, but it still takes the time of its requests.",[339,340],"dev-initial-sync-table",{},[42,342,344],{"id":343},"good-practice","Good practice",[163,346,347,350,357,360,363],{},[166,348,349],{},"Run one sync process per key and team. Several workers on one key share the same limits, so they only make each other wait.",[166,351,352,353,356],{},"Ask for full pages of ",[143,354],{"name":355},"PAGE_LIMIT.max"," items during an initial sync.",[166,358,359],{},"Poll the changes feed every 1 to 5 minutes. A poll that finds nothing new costs one item of the rate limit and nothing of the daily quota.",[166,361,362],{},"Read members and bookable services when you start a team, when you meet an id you do not know, and once a day: not on every run, and not again for an id the last read did not resolve.",[166,364,365,366,295],{},"Never create more integrations or keys to get around the limits. If they are too low for what you need, ",[230,367,369],{"href":368},"\u002Fdevelopers\u002Fsupport","tell us",{"title":371,"searchDepth":372,"depth":372,"links":373},"",3,[374,379,380,381],{"id":44,"depth":375,"text":45,"children":376},2,[377,378],{"id":138,"depth":372,"text":64},{"id":237,"depth":372,"text":67},{"id":270,"depth":375,"text":271},{"id":328,"depth":375,"text":329},{"id":343,"depth":375,"text":344},"How much a key can read per minute and per day, what counts toward each limit, how to retry after a 429, and how long an initial sync takes.",false,"md","en",{},true,"30","\u002Fdevelopers\u002Frate-limits","---\ntitle: Rate limits\ndescription: How much a key can read per minute and per day, what counts toward each limit, how to retry after a 429, and how long an initial sync takes.\nsection: reference\norder: 30\ntranslationKey: rate-limits\nlang: en\ndraft: false\n---\n\nEach key has two limits, shared by every team it reads: a **rate limit** on how fast it reads, and a **daily quota** on how much. Both count **items**, not requests. An item is one object in a response: a feed page of 100 changes is 100 items, removals included.\n\n::dev-callout{type=\"note\" title=\"Approximate during the Beta\"}\nIn the Beta, each server that answers your requests counts these limits, and the lockout after failed attempts, on its own, and a restart starts its count again. So the numbers on this page are approximate: a key can sometimes read more, and a request refused with `429` can succeed when it is retried. Design your integration for the numbers on this page.\n::\n\n## Two limits per key\n\nWhich requests count toward which limit:\n\n| Requests | Rate limit | Daily quota |\n|---|---|---|\n| The changes feed, every list, a lead's activities, `GET \u002Fv1\u002Fteams`, `GET \u002Fv1\u002Fmembers` and `GET \u002Fv1\u002Fbooking_services` | Yes | Yes |\n| A request for one record, such as `GET \u002Fv1\u002Fleads\u002F{id}`, and also `POST \u002Fv1\u002Fleads\u002Fsearch` and `GET \u002Fv1\u002Fme` | Yes | No |\n| `GET \u002Fv1\u002Fhealth` | No | No |\n\nEach endpoint in the reference shows its row: **Sync** for the first, **Read** for the second.\n\n### Rate limit\n\nA key reads up to :api-const{name=\"SYNC_VELOCITY.perMinute\"} items a minute, with bursts of up to :api-const{name=\"SYNC_VELOCITY.burst\"}. Capacity you do not use builds back up at that pace until the burst is full again. Past the limit, the API answers `429 rate_limited`, and `Retry-After` says how long until there is room for your request.\n\nHow a request counts:\n\n- Before it runs, a request reserves its `limit`. A list or feed request that sends no `limit` reserves :api-const{name=\"PAGE_LIMIT.default\"}; a request for one record reserves one.\n- Once it has run, it is charged for the items it returned, and at least one. A short page gives back the difference, but a request that returns nothing still costs one item: a search that finds no lead, an id that answers `404`, or any other error it gets once it runs, `quota_exceeded` included.\n- A request refused before it runs is not charged, such as a failed authentication, a missing permission or, on a route that takes `Totem-Team`, a team the key cannot read or that is not ready yet. A request that names a record by its id, such as `GET \u002Fv1\u002Fleads\u002F{id}` or a lead's activities, checks its team as it runs, so a refusal for that team costs one item.\n- A request for one record is charged for what it returns: `GET \u002Fv1\u002Fleads\u002F{id}` returns a lead with its two facets, so it counts up to three items. A search counts each lead it returns, or one when it finds none.\n\nBecause a request reserves its full `limit` first, a smaller `limit` lets you keep reading when little capacity is left.\n\n`429 rate_limited` can also mean that your IP address or your key is locked out after too many failed authentication attempts. `Retry-After` tells the two apart: a lockout always sends :api-const{name=\"AUTH_FAILURE_LIMITS.banMs\" divide=\"1000\"} seconds, the full length of the lock, while the rate limit asks for the few seconds your request needs. Slowing down does not end a lockout: find the process at that address that sends a missing, malformed, wrong or unknown key, fix it, then wait. [Authentication](\u002Fdevelopers\u002Fauthentication#failed-attempts) explains what counts as a failed attempt.\n\n### Daily quota\n\nEach UTC day, a key can read :api-const{name=\"SYNC_DAILY_BUDGET.floor\"} items, or :api-const{name=\"SYNC_DAILY_BUDGET.recordsMultiplier\"} times the number of records in its teams if that is more. Records of every kind count toward that number, removals included. Every item returned by the requests in the first row of the table counts toward the quota, whatever its kind.\n\nThe number of records is taken at the key's first request of each UTC day, so a team added to the key later that day may raise the quota only from the next day. Plan the initial sync of a large team for when its quota allows it.\n\nThe quota leaves room for an initial sync of every team and a day of polling. Re-reading whole lists again and again is what spends it.\n\nPast the quota, those requests answer `429 quota_exceeded` until 00:00 UTC, when the quota resets. `Retry-After` counts the seconds until then. Requests for one record, search and `GET \u002Fv1\u002Fme` keep working.\n\n## Retry after a 429\n\n`Retry-After` comes with every `429` the API itself returns, and it is always a whole number of seconds. Wait at least that long, then send the same request again, with the same cursor. Nothing is lost while you wait: the feed keeps every change for you.\n\n- After `rate_limited`, the wait is usually a few seconds, or :api-const{name=\"AUTH_FAILURE_LIMITS.banMs\" divide=\"1000\"} seconds after an [authentication lockout](\u002Fdevelopers\u002Fauthentication#failed-attempts).\n- After `quota_exceeded`, the wait runs until 00:00 UTC and can last hours. Do not keep a process asleep that long: end the run, and schedule the next one for that time. The [reference client](\u002Fdevelopers\u002Fsync#tested-reference-client) does this with its `retry_later` outcome.\n\nA `429` from the firewall in front of the API has no `Retry-After` and no JSON error body: back off exponentially. A `5xx` carries no `Retry-After` either: retry it with exponential backoff too.\n\n## Initial sync estimates\n\nThe table gives the minimum time the rate limit adds to an initial sync at the limits on this page, for one key with no other traffic; during the Beta it is approximate, as the note at the top of this page explains. It counts records of every kind, one item each: a lead with its attribution, its response and three activities is six records. Network time, and the time Totem needs to prepare a team just added to a key, come on top. A copy that fits within the burst shows *Under 1 minute*: the rate limit adds nothing to it, but it still takes the time of its requests.\n\n::dev-initial-sync-table\n::\n\n## Good practice\n\n- Run one sync process per key and team. Several workers on one key share the same limits, so they only make each other wait.\n- Ask for full pages of :api-const{name=\"PAGE_LIMIT.max\"} items during an initial sync.\n- Poll the changes feed every 1 to 5 minutes. A poll that finds nothing new costs one item of the rate limit and nothing of the daily quota.\n- Read members and bookable services when you start a team, when you meet an id you do not know, and once a day: not on every run, and not again for an id the last read did not resolve.\n- Never create more integrations or keys to get around the limits. If they are too low for what you need, [tell us](\u002Fdevelopers\u002Fsupport).\n","reference",{"title":6,"description":382},"developers\u002Frate-limits","rate-limits","y88Luit0zSz829gYKZnlHXDs_L_KRiKLe3iAZDtR4GQ",[397,411,438,483],{"section":398,"items":399},"start",[400,404,408],{"path":401,"title":402,"description":403},"\u002Fdevelopers","Overview","Read the leads, calls, conversations and bookings of your Totem teams from your own systems, and keep a copy in sync.",{"path":405,"title":406,"description":407},"\u002Fdevelopers\u002Fquickstart","Quickstart","Make your first requests to the Totem API in a few minutes. Check your key, find your team, list leads and start a sync.",{"path":409,"title":233,"description":410},"\u002Fdevelopers\u002Fauthentication","Secret keys and where they may live, the Totem-Team header for keys with several teams, IP allowlists, and how to roll or revoke a key.",{"section":412,"items":413},"guides",[414,418,422,426,430,434],{"path":415,"title":416,"description":417},"\u002Fdevelopers\u002Ftypescript","TypeScript SDK","Use the official TypeScript client to read your Totem data, paginate lists and handle API errors from your server.",{"path":419,"title":420,"description":421},"\u002Fdevelopers\u002Fsync","Keep a copy in sync","Copy a team with the changes feed and keep the copy current. Apply pages safely, recover from errors, and start from a reference client that Totem tests.",{"path":423,"title":424,"description":425},"\u002Fdevelopers\u002Fpagination","Lists and pagination","How list endpoints return records a page at a time, how to read every page, and what order and filters a list supports.",{"path":427,"title":428,"description":429},"\u002Fdevelopers\u002Fcoverage","Data coverage","What Totem records, since when, and how to tell an empty value from a fact that was never recorded.",{"path":431,"title":432,"description":433},"\u002Fdevelopers\u002Ftesting","Testing and go-live","How to build and test an integration safely while the API has no test environment, and what to check before you go live.",{"path":435,"title":436,"description":437},"\u002Fdevelopers\u002Fsecurity","Security and personal data","How Totem protects API keys and the data the API serves, what it records about each key, where the API runs, and what to do with the personal data you copy.",{"section":391,"items":439},[440,444,448,449,454,459,464,469,474,479],{"path":441,"title":442,"description":443},"\u002Fdevelopers\u002Fconventions","Conventions","The notation these docs use, and the rules every response follows: ids, timestamps, empty values, amounts, enums, versions, stability, errors and untrusted text.",{"path":445,"title":446,"description":447},"\u002Fdevelopers\u002Ferrors","Errors","The error format, how your integration should handle each kind of error, and every error code with when it happens and what to do.",{"path":389,"title":6,"description":382},{"path":450,"title":451,"description":452,"apiTag":453},"\u002Fdevelopers\u002Freference-account","Account, teams and members","Check that a key works and what it can read, list its teams with their time zones, list each team's members, and check that the API is up.","account",{"path":455,"title":456,"description":457,"apiTag":458},"\u002Fdevelopers\u002Freference-leads","Leads, boards and activities","List, fetch and search a team's leads and clients, read each lead's activities, and list the boards and stages they move through.","leads",{"path":460,"title":461,"description":462,"apiTag":463},"\u002Fdevelopers\u002Freference-calls","Calls","List and fetch a team's calls, with their direction, timing and a normalized outcome. No recordings or transcripts.","calls",{"path":465,"title":466,"description":467,"apiTag":468},"\u002Fdevelopers\u002Freference-conversations","Conversations","List and fetch a team's conversations on every channel, with their status, assignee, whether a person has taken them over and when the last messages came and went. Never message content.","conversations",{"path":470,"title":471,"description":472,"apiTag":473},"\u002Fdevelopers\u002Freference-bookings","Bookings and services","List and fetch a team's bookings, and list the services its customers can book.","bookings",{"path":475,"title":476,"description":477,"apiTag":478},"\u002Fdevelopers\u002Freference-sync","Changes feed","One endpoint that copies a team and then returns every change, page by page.","sync",{"path":480,"title":481,"description":482},"\u002Fdevelopers\u002Fobjects","All objects","Every object the API returns, field by field, with an example of each.",{"section":484,"items":485},"resources",[486,490,493,497],{"path":487,"title":488,"description":489},"\u002Fdevelopers\u002Fchangelog","Changelog","Changes to the Totem API, newest first, each under the date it shipped.",{"path":368,"title":491,"description":492},"Support","How to get help with the Totem API, what to include in a request, and what to do if a key leaks.",{"path":494,"title":495,"description":496},"\u002Fdevelopers\u002Fglossary","Glossary","The terms these docs use, defined in one place, each with a link to the page that explains it.",{"path":498,"title":499,"description":500},"\u002Fdevelopers\u002Ffaq","FAQ","Short answers to the questions developers ask most about the Totem API, with links to the details.","\u002Fdevelopers\u002Fes\u002Frate-limits",{"ACTIVATION_MARGIN_MS":503,"ADMIN_ACCESS_DISCLOSURE_VERSION":504,"AUDIT_RETENTION_DAYS":505,"AUTH_FAILURE_LIMITS":506,"CAPTURE_LAG_FLOOR_MS":510,"CAPTURE_LAG_P99_MS":7,"CURSOR_MAX_AGE_DAYS":511,"DIRTY_TTL_DAYS":511,"FAMILY_TEAM_SCOPE":512,"FAMILY_TEAM_SCOPE_OPTIONS":513,"FEED_SETTLE_LAG_MS":515,"GATE_REFRESH_MS":503,"INTEGRATION_NAME_LENGTH":516,"INTEGRATION_PURPOSE_LENGTH":518,"KEY_CACHE_TTL_MS":521,"KEY_STATS_RETENTION_DAYS":522,"LEAD_RESPONSE_READ_BUDGET":523,"LIST_SCAN_MAX":526,"MAX_FAMILY_INTEGRATION_TEAMS":511,"MAX_INTEGRATIONS_PER_FAMILY":527,"MAX_IP_ALLOWLIST":508,"PAGE_LIMIT":528,"PLATFORM_CONFIG_TTL_MS":531,"REMOVAL_RETENTION_DAYS":532,"REQUEST_BODY_MAX_BYTES":533,"ROLL_GRACE_DEFAULT_HOURS":534,"ROLL_GRACE_HOURS":535,"SEARCH_MAX_RESULTS":527,"SENSITIVE_SECTOR_POLICY":538,"SENSITIVE_SECTOR_POLICY_OPTIONS":539,"SYNC_DAILY_BUDGET":541,"SYNC_VELOCITY":543,"TEAM_CACHE_TTL_MS":545},60000,"2026-10-17",365,{"perIpPerMinute":507,"perLookupIdPerMinute":508,"banMs":509},60,20,600000,300000,30,"explicit_list",[512,514],"all_family_teams",10000,{"min":375,"max":517},80,{"min":519,"max":520},1,280,5000,90,{"conversations":508,"messageReads":524,"calls":525},200,50,1000,10,{"default":529,"max":530},25,100,15000,45,16384,24,[536,519,534,537],0,168,"exclude",[538,540],"allow",{"floor":542,"recordsMultiplier":372},250000,{"perMinute":544,"burst":515},2000,30000,"1.0a",{"operations":548,"schemas":549,"errors":550,"commonErrors":678,"defaultStability":679,"policy":502,"problemExample":680},[],[],[551,559,564,569,576,581,588,595,600,605,611,616,622,629,636,643,649,656,660,667,673],{"code":552,"status":553,"title":554,"wireTitle":554,"action":555,"description":556,"fix":557,"retryable":383,"retry":558},"invalid_request",400,"Invalid request","fix_request","Something in the request is not valid: an unknown, repeated or out-of-range query parameter, a query string or body on an endpoint that takes none, a cursor issued for another endpoint, filter or team, a malformed `Totem-Team` header, or a body that is not the JSON this endpoint expects. `param` names the parameter, header or field at fault. A conversations cursor is also refused once the conversation it points at has been erased.","Correct what `param` names before you retry: the same request fails the same way. For a cursor, send the `next_cursor` you received from the same endpoint, with the same filters and team. If a conversations cursor you did not change is refused, start that list again from the first page.","no",{"code":560,"status":553,"title":561,"wireTitle":561,"action":555,"description":562,"fix":563,"retryable":383,"retry":558},"team_required","Team required","The key reads more than one team and this endpoint reads one team's data, but the request does not say which team.","Send the team's id (`team_…`, as listed by `GET \u002Fv1\u002Fteams`) in the `Totem-Team` header.",{"code":565,"status":553,"title":566,"wireTitle":566,"action":555,"description":567,"fix":568,"retryable":383,"retry":558},"secret_key_in_browser","Secret key sent from a browser","The request carried a secret key together with an `Origin` header, which means it came from a browser. Totem refuses it before reading anything.","Call the API only from your server. If the key has been in a web page, a mobile app or a browser extension, treat it as leaked: roll it and mark it as compromised, so the old key stops working at once.",{"code":570,"status":571,"title":572,"wireTitle":572,"action":573,"description":574,"fix":575,"retryable":383,"retry":558},"invalid_credentials",401,"Invalid credentials","check_credentials","The `Authorization` header is missing or malformed, or the key is unknown, wrong or revoked, or its integration is no longer active.","Send `Authorization: Bearer \u003Ckey>` with a current secret key. Do not retry in a loop: repeated failures from one IP address, or against one key, lock it out for a while with `429 rate_limited`.",{"code":577,"status":571,"title":578,"wireTitle":578,"action":573,"description":579,"fix":580,"retryable":383,"retry":558},"key_expired","Key expired","The key was rolled and its grace period is over.","Deploy the key that replaced it: the old key is past its grace period and will not work again. If there is no replacement, create a new key in Settings → Developers.",{"code":582,"status":583,"title":584,"wireTitle":584,"action":585,"description":586,"fix":587,"retryable":383,"retry":558},"insufficient_scope",403,"Insufficient scope","contact_support","The key lacks a permission this endpoint needs. Every v1.0a key holds the full read set, so this should not happen.","Contact support and quote the `Totem-Request-Id` of the response.",{"code":589,"status":583,"title":590,"wireTitle":590,"action":591,"description":592,"fix":593,"retryable":387,"retry":594},"plan_not_entitled","Plan not entitled","keep_and_retry","The organization's plan does not include the Totem API at the moment.","Keep your data and cursors, and pause calls until the customer has a plan with API access again; then continue where you left off. While access is refused, the feed delivers nothing for the key's teams, removals included: if the refusal lasts longer than your retention policy allows, delete your copy.","restored",{"code":596,"status":583,"title":597,"wireTitle":597,"action":573,"description":598,"fix":599,"retryable":383,"retry":558},"ip_not_allowed","IP address not allowed","The key is valid, but the request came from an IP address outside the integration's allowlist.","Call from an allowed address, or ask an administrator to add yours to the allowlist in Settings → Developers.",{"code":601,"status":583,"title":602,"wireTitle":602,"action":591,"description":603,"fix":604,"retryable":387,"retry":594},"team_state_restricted","Team restricted","The team is restricted for now: it is disabled (for example, suspended for non-payment), archived or billing-only, or its API access is paused. `GET \u002Fv1\u002Fteams` still lists it.","Keep the team's data and cursor, skip it for this run and try again later. The key's other teams are not affected. While the team is restricted, the feed delivers nothing for it, removals included: if the restriction lasts longer than your retention policy allows, delete the team's copy.",{"code":606,"status":583,"title":607,"wireTitle":607,"action":591,"description":608,"fix":609,"retryable":383,"retry":610},"sector_restricted","Sector restricted","Totem does not export this team's data through the API because the team works in a sensitive sector, such as health care, where its records can reveal health information.","Skip the team: waiting does not change this. The feed delivers nothing for it, removals included, so keep what you already have only as long as your retention policy allows, then delete the team's copy. Talk to the customer or to Totem if you need its data.","blocked",{"code":612,"status":583,"title":613,"wireTitle":613,"action":591,"description":614,"fix":615,"retryable":387,"retry":594},"capability_disabled","Capability disabled","Totem has temporarily switched this endpoint off for every key.","Keep your data and cursors and try again later; the other endpoints keep working.",{"code":617,"status":618,"title":619,"wireTitle":619,"action":555,"description":620,"fix":621,"retryable":383,"retry":558},"resource_missing",404,"Resource not found","The record does not exist, was removed, belongs to a team this key does not read, or was created so recently that Totem has not prepared it yet. A `GET` or `POST` under `\u002Fv1\u002F` that matches no endpoint also gets this code. Any other method, and any path outside `\u002Fv1\u002F`, gets a plain `404` from the firewall in front of the API, with no problem body and no `Totem-Request-Id`.","Check the id and the path. If the record was created moments ago, do not retry in a loop: the changes feed delivers it as soon as it is ready.",{"code":623,"status":618,"title":624,"wireTitle":624,"action":625,"description":626,"fix":627,"retryable":383,"retry":628},"team_not_accessible","Team not accessible","drop_team","The `Totem-Team` header names a team this key does not read: one it never covered, one removed from the key or from the organization, or one that was deleted. Without the header, it means the key no longer reads any team.","Re-read `GET \u002Fv1\u002Fteams` before you act. If the team is no longer listed, delete its copy and its cursor; if it is still listed, keep everything and try again on the next run.","confirm",{"code":630,"status":631,"title":632,"wireTitle":632,"action":633,"description":634,"fix":635,"retryable":383,"retry":558},"resync_required",409,"Resync required","resync","Totem cannot continue the feed from this cursor: the data was restored from a backup, or a gap was found in the team's changes.","Run a full resync: forget the versions you stored for the team, read the feed again without a cursor, and once it has caught up delete every local record of the team it did not deliver. Keep using your current copy until then.",{"code":637,"status":631,"title":638,"wireTitle":638,"action":639,"description":640,"fix":641,"retryable":387,"retry":642},"capture_not_ready","Team data is still being prepared","wait_capture","Totem is still preparing this team's data for the API. This happens once per team, after it is first added to any key; adding it to another key later does not repeat it.","Keep whatever you hold for the team and try again in a few minutes; the key's other teams keep syncing meanwhile.","later",{"code":644,"status":645,"title":646,"wireTitle":646,"action":633,"description":647,"fix":648,"retryable":383,"retry":558},"sync_cursor_expired",410,"Sync cursor expired","The cursor is more than 30 days old, counted from the point in the feed it reached (or, while an initial sync is still running, from when that sync started).","Run a full resync, as for `resync_required`. To prevent it, save the `next_cursor` of every page, empty pages included: the cursor of a team you poll regularly never ages out.",{"code":287,"status":650,"title":651,"wireTitle":651,"action":652,"description":653,"fix":654,"retryable":387,"retry":655},429,"Rate limited","retry_after","The key went over its rate limit (items per minute), or too many failed authentication attempts from this IP address or against this key have locked it out for a while.","Wait the seconds in `Retry-After`, then retry the same request. Each request sets aside its full `limit` up front and gives back what it does not use, so a smaller `limit` keeps a nearly spent allowance moving.","after",{"code":189,"status":650,"title":657,"wireTitle":657,"action":652,"description":658,"fix":659,"retryable":387,"retry":655},"Daily quota exceeded","The key has spent its daily quota of items. Every item returned by the changes feed and by every list counts toward it, including `GET \u002Fv1\u002Fteams`, `GET \u002Fv1\u002Fmembers`, `GET \u002Fv1\u002Fbooking_services` and a lead's activities. The quota resets at 00:00 UTC.","Stop syncing until 00:00 UTC (`Retry-After` counts the seconds) and resume then with the same cursor: nothing is lost. Requests for one record, such as `GET \u002Fv1\u002Fleads\u002F{id}`, search and `GET \u002Fv1\u002Fme` do not count toward the quota and keep working.",{"code":661,"status":662,"title":663,"wireTitle":663,"action":664,"description":665,"fix":666,"retryable":387,"retry":664},"internal_error",500,"Internal error","backoff","Something went wrong inside Totem while answering this request.","Retry with exponential backoff. If it keeps failing, contact support and quote the `Totem-Request-Id`.",{"code":668,"status":669,"title":670,"wireTitle":670,"action":664,"description":671,"fix":672,"retryable":387,"retry":664},"api_disabled",503,"API disabled","Totem has temporarily switched the API off for every key.","Keep your data and cursors and retry later with exponential backoff.",{"code":674,"status":669,"title":675,"wireTitle":675,"action":664,"description":676,"fix":677,"retryable":387,"retry":664},"service_unavailable","Service unavailable","Reserved: the API itself does not return this code today. A `503` from the load balancer or the hosting platform in front of the API arrives without a problem body; treat it like this code.","Retry with exponential backoff; your data and cursors stay valid.",[552,565,570,577,582,589,596,612,287,661,668,674],"beta",{"type":681,"title":619,"status":618,"code":617,"request_id":682,"doc_url":681},"https:\u002F\u002Ftotemstudio.ai\u002Fdevelopers\u002Ferrors#resource_missing","req_0f6b2c1e-8d4a-4b7e-9c3f-5a2d1e7b9c40","guide",[685,686,687,688,689,690],{"id":44,"text":45,"depth":375},{"id":138,"text":64,"depth":372},{"id":237,"text":67,"depth":372},{"id":270,"text":271,"depth":375},{"id":328,"text":329,"depth":375},{"id":343,"text":344,"depth":375},{"path":445,"title":446,"section":391},{"path":450,"title":451,"section":391},[],1792502789473]