[{"data":1,"prerenderedAt":735},["ShallowReactive",2],{"developers:\u002Fdevelopers\u002Ferrors":3},{"doc":4,"lang":445,"nav":456,"alternatePath":557,"policy":558,"specVersion":602,"reference":603,"layout":727,"toc":728,"prev":732,"next":733,"operations":734,"overview":7,"heroExample":7},{"id":5,"title":6,"apiTag":7,"body":8,"description":442,"draft":443,"extension":444,"lang":445,"meta":446,"navTitle":7,"navigation":447,"order":448,"path":449,"rawbody":450,"section":451,"seo":452,"stem":453,"translationKey":454,"version":7,"__hash__":455},"developers_en\u002Fdevelopers\u002Ferrors.md","Errors",null,{"type":9,"value":10,"toc":435},"minimark",[11,15,20,32,42,129,132,166,169,178,225,229,235,418,421,425,431],[12,13,14],"p",{},"When a request fails, the API answers with an HTTP status and a JSON body that says what went wrong. Every error body links to its entry on this page.",[16,17,19],"h2",{"id":18},"error-format","Error format",[12,21,22,23,27,28,31],{},"Errors follow RFC 9457 and come as ",[24,25,26],"code",{},"application\u002Fproblem+json",". For example, ",[24,29,30],{},"GET \u002Fv1\u002Fleads?limit=500"," answers:",[33,34,40],"pre",{"className":35,"code":37,"language":38,"meta":39},[36],"language-json","{\n  \"type\": \"https:\u002F\u002Ftotemstudio.ai\u002Fdevelopers\u002Ferrors#invalid_request\",\n  \"title\": \"Invalid request\",\n  \"status\": 400,\n  \"code\": \"invalid_request\",\n  \"request_id\": \"req_0f6b2c1e-8d4a-4b7e-9c3f-5a2d1e7b9c40\",\n  \"param\": \"limit\",\n  \"doc_url\": \"https:\u002F\u002Ftotemstudio.ai\u002Fdevelopers\u002Ferrors#invalid_request\"\n}\n","json","",[24,41,37],{"__ignoreMap":39},[43,44,45,58],"table",{},[46,47,48],"thead",{},[49,50,51,55],"tr",{},[52,53,54],"th",{},"Field",[52,56,57],{},"What it holds",[59,60,61,71,81,91,105,119],"tbody",{},[49,62,63,68],{},[64,65,66],"td",{},[24,67,24],{},[64,69,70],{},"What went wrong, as a stable code. Branch on it.",[49,72,73,78],{},[64,74,75],{},[24,76,77],{},"status",[64,79,80],{},"The HTTP status, repeated.",[49,82,83,88],{},[64,84,85],{},[24,86,87],{},"title",[64,89,90],{},"A short description in English, for people. It can change, so never branch on it.",[49,92,93,102],{},[64,94,95,98,99],{},[24,96,97],{},"type"," and ",[24,100,101],{},"doc_url",[64,103,104],{},"A link to the code's entry below.",[49,106,107,112],{},[64,108,109],{},[24,110,111],{},"request_id",[64,113,114,115,118],{},"The id of this request, the same as the ",[24,116,117],{},"Totem-Request-Id"," header.",[49,120,121,126],{},[64,122,123],{},[24,124,125],{},"param",[64,127,128],{},"Present only when one header, query parameter or body field is at fault. It names it, and never repeats the value you sent.",[12,130,131],{},"These headers come with an error:",[133,134,135,147,157],"ul",{},[136,137,138,140,141,146],"li",{},[24,139,117],{},", on every response the API itself sends. Log it, and quote it when you ask ",[142,143,145],"a",{"href":144},"\u002Fdevelopers\u002Fsupport","Support"," for help. Never send us your key or your customers' data.",[136,148,149,152,153,156],{},[24,150,151],{},"Retry-After",", on every ",[24,154,155],{},"429"," the API itself returns: a whole number of seconds to wait.",[136,158,159,152,162,165],{},[24,160,161],{},"WWW-Authenticate: Bearer realm=\"Totem API\"",[24,163,164],{},"401",".",[12,167,168],{},"New codes can appear at any time. Handle a code you do not know by its HTTP status, as the next section describes.",[12,170,171,172,174,175,177],{},"During the Beta, the firewall in front of the API answers some requests itself, before they reach the API. Its answer has no JSON error body, only the firewall's own default page, and no ",[24,173,151],{}," or ",[24,176,117],{},". Do not parse its body as JSON: handle it by its status:",[133,179,180,204,220],{},[136,181,182,185,186,189,190,98,193,196,197,98,200,203],{},[24,183,184],{},"404"," for a path outside ",[24,187,188],{},"\u002Fv1\u002F",", or for any method other than ",[24,191,192],{},"GET",[24,194,195],{},"POST",", ",[24,198,199],{},"HEAD",[24,201,202],{},"OPTIONS"," included;",[136,205,206,209,210,213,214,219],{},[24,207,208],{},"403"," for a request with a body, unless it is ",[24,211,212],{},"POST \u002Fv1\u002Fleads\u002Fsearch",", and for a body larger than ",[215,216],"api-const",{"divide":217,"name":218},"1024","REQUEST_BODY_MAX_BYTES"," KiB;",[136,221,222,224],{},[24,223,155],{}," when one address sends too many requests, for example many requests without a well-formed key.",[16,226,228],{"id":227},"handling-errors","Handling errors",[12,230,231,232,234],{},"Decide by HTTP status first, then by ",[24,233,24],{},":",[133,236,237,270,282,310,337,364,404],{},[136,238,239,246,247,249,250,252,253,257,258,261,262,265,266,269],{},[240,241,242,245],"strong",{},[24,243,244],{},"400",": fix the request."," Sending the same request again fails the same way. ",[24,248,125],{}," says what to fix. One ",[24,251,244],{}," is not your request's fault: a conversations cursor stops working when the conversation it points at is erased, so start that list again from the first page, as ",[142,254,256],{"href":255},"\u002Fdevelopers\u002Fpagination#pages-and-cursors","Lists and pagination"," explains. Two codes need more than a fix: ",[24,259,260],{},"team_required"," means your key reads several teams and the request must name one in ",[24,263,264],{},"Totem-Team","; ",[24,267,268],{},"secret_key_in_browser"," means the key was used from a browser, so treat it as leaked.",[136,271,272,277,278,281],{},[240,273,274,276],{},[24,275,164],{},": fix the key."," Do not retry in a loop: repeated failures lock your IP address or your key out for a while. ",[24,279,280],{},"key_expired"," means the key was rolled and its grace period is over: deploy the new key.",[136,283,284,289,290,293,294,174,297,300,301,304,305,309],{},[240,285,286,288],{},[24,287,208],{},": access is refused for now."," Keep your data and your cursors, and skip the team or the endpoint. Some refusals can end on their own, such as ",[24,291,292],{},"capability_disabled"," or a team whose access Totem has paused; others need someone to act, such as ",[24,295,296],{},"plan_not_entitled",[24,298,299],{},"ip_not_allowed","; and ",[24,302,303],{},"sector_restricted"," does not end by waiting: it lasts as long as Totem's current sector policy applies, and the ",[142,306,308],{"href":307},"\u002Fdevelopers\u002Fchangelog","changelog"," records any change to it. Each code below says which. While access is refused, the changes feed delivers nothing for the team, removals included, so if a refusal lasts longer than your retention policy allows, delete your copy.",[136,311,312,317,318,321,322,325,326,333,334,336],{},[240,313,314,316],{},[24,315,184],{},": check what you asked for."," ",[24,319,320],{},"resource_missing"," means the record does not exist, is gone, or is not ready yet; the changes feed delivers new records once they are ready. ",[24,323,324],{},"team_not_accessible"," means the key may no longer read the team: ",[142,327,329,330],{"href":328},"\u002Fdevelopers\u002Fsync#when-teams-change","confirm it with ",[24,331,332],{},"GET \u002Fv1\u002Fteams"," before you delete anything. A ",[24,335,184],{}," without a JSON error body comes from the firewall: check the method and the path.",[136,338,339,317,348,98,351,354,355,359,360,363],{},[240,340,341,98,344,347],{},[24,342,343],{},"409",[24,345,346],{},"410",": the changes feed needs you to act.",[24,349,350],{},"resync_required",[24,352,353],{},"sync_cursor_expired"," ask for a ",[142,356,358],{"href":357},"\u002Fdevelopers\u002Fsync#full-resync","full resync",". ",[24,361,362],{},"capture_not_ready"," asks you to wait a few minutes, while the key's other teams keep syncing.",[136,365,366,371,372,374,375,378,379,383,384,388,389,392,393,395,396,398,399,403],{},[240,367,368,370],{},[24,369,155],{},": slow down."," Wait the seconds in ",[24,373,151],{},", then retry the same request. ",[24,376,377],{},"rate_limited"," usually clears within seconds, but after an ",[142,380,382],{"href":381},"\u002Fdevelopers\u002Fauthentication#failed-attempts","authentication lockout"," it lasts ",[215,385],{"divide":386,"name":387},"1000","AUTH_FAILURE_LIMITS.banMs"," seconds. ",[24,390,391],{},"quota_exceeded"," lasts until 00:00 UTC, when the daily quota resets. A ",[24,394,155],{}," from the firewall has no ",[24,397,151],{},": back off exponentially. ",[142,400,402],{"href":401},"\u002Fdevelopers\u002Frate-limits","Rate limits"," explains both limits.",[136,405,406,412,413,415,416,165],{},[240,407,408,411],{},[24,409,410],{},"5xx",": retry later."," Retry with exponential backoff, keeping your cursors. If it keeps failing, contact ",[142,414,145],{"href":144}," with the ",[24,417,117],{},[12,419,420],{},"In every case, never save a changes-feed cursor after a failed request.",[16,422,424],{"id":423},"all-error-codes","All error codes",[12,426,427,428,430],{},"Each code has its own anchor, which is where ",[24,429,101],{}," points.",[432,433],"dev-error-catalog",{":example":434},"false",{"title":39,"searchDepth":436,"depth":436,"links":437},3,[438,440,441],{"id":18,"depth":439,"text":19},2,{"id":227,"depth":439,"text":228},{"id":423,"depth":439,"text":424},"The error format, how your integration should handle each kind of error, and every error code with when it happens and what to do.",false,"md","en",{},true,"20","\u002Fdevelopers\u002Ferrors","---\ntitle: Errors\ndescription: The error format, how your integration should handle each kind of error, and every error code with when it happens and what to do.\nsection: reference\norder: 20\ntranslationKey: errors\nlang: en\ndraft: false\n---\n\nWhen a request fails, the API answers with an HTTP status and a JSON body that says what went wrong. Every error body links to its entry on this page.\n\n## Error format\n\nErrors follow RFC 9457 and come as `application\u002Fproblem+json`. For example, `GET \u002Fv1\u002Fleads?limit=500` answers:\n\n```json\n{\n  \"type\": \"https:\u002F\u002Ftotemstudio.ai\u002Fdevelopers\u002Ferrors#invalid_request\",\n  \"title\": \"Invalid request\",\n  \"status\": 400,\n  \"code\": \"invalid_request\",\n  \"request_id\": \"req_0f6b2c1e-8d4a-4b7e-9c3f-5a2d1e7b9c40\",\n  \"param\": \"limit\",\n  \"doc_url\": \"https:\u002F\u002Ftotemstudio.ai\u002Fdevelopers\u002Ferrors#invalid_request\"\n}\n```\n\n| Field | What it holds |\n|---|---|\n| `code` | What went wrong, as a stable code. Branch on it. |\n| `status` | The HTTP status, repeated. |\n| `title` | A short description in English, for people. It can change, so never branch on it. |\n| `type` and `doc_url` | A link to the code's entry below. |\n| `request_id` | The id of this request, the same as the `Totem-Request-Id` header. |\n| `param` | Present only when one header, query parameter or body field is at fault. It names it, and never repeats the value you sent. |\n\nThese headers come with an error:\n\n- `Totem-Request-Id`, on every response the API itself sends. Log it, and quote it when you ask [Support](\u002Fdevelopers\u002Fsupport) for help. Never send us your key or your customers' data.\n- `Retry-After`, on every `429` the API itself returns: a whole number of seconds to wait.\n- `WWW-Authenticate: Bearer realm=\"Totem API\"`, on every `401`.\n\nNew codes can appear at any time. Handle a code you do not know by its HTTP status, as the next section describes.\n\nDuring the Beta, the firewall in front of the API answers some requests itself, before they reach the API. Its answer has no JSON error body, only the firewall's own default page, and no `Retry-After` or `Totem-Request-Id`. Do not parse its body as JSON: handle it by its status:\n\n- `404` for a path outside `\u002Fv1\u002F`, or for any method other than `GET` and `POST`, `HEAD` and `OPTIONS` included;\n- `403` for a request with a body, unless it is `POST \u002Fv1\u002Fleads\u002Fsearch`, and for a body larger than :api-const{name=\"REQUEST_BODY_MAX_BYTES\" divide=\"1024\"} KiB;\n- `429` when one address sends too many requests, for example many requests without a well-formed key.\n\n## Handling errors\n\nDecide by HTTP status first, then by `code`:\n\n- **`400`: fix the request.** Sending the same request again fails the same way. `param` says what to fix. One `400` is not your request's fault: a conversations cursor stops working when the conversation it points at is erased, so start that list again from the first page, as [Lists and pagination](\u002Fdevelopers\u002Fpagination#pages-and-cursors) explains. Two codes need more than a fix: `team_required` means your key reads several teams and the request must name one in `Totem-Team`; `secret_key_in_browser` means the key was used from a browser, so treat it as leaked.\n- **`401`: fix the key.** Do not retry in a loop: repeated failures lock your IP address or your key out for a while. `key_expired` means the key was rolled and its grace period is over: deploy the new key.\n- **`403`: access is refused for now.** Keep your data and your cursors, and skip the team or the endpoint. Some refusals can end on their own, such as `capability_disabled` or a team whose access Totem has paused; others need someone to act, such as `plan_not_entitled` or `ip_not_allowed`; and `sector_restricted` does not end by waiting: it lasts as long as Totem's current sector policy applies, and the [changelog](\u002Fdevelopers\u002Fchangelog) records any change to it. Each code below says which. While access is refused, the changes feed delivers nothing for the team, removals included, so if a refusal lasts longer than your retention policy allows, delete your copy.\n- **`404`: check what you asked for.** `resource_missing` means the record does not exist, is gone, or is not ready yet; the changes feed delivers new records once they are ready. `team_not_accessible` means the key may no longer read the team: [confirm it with `GET \u002Fv1\u002Fteams`](\u002Fdevelopers\u002Fsync#when-teams-change) before you delete anything. A `404` without a JSON error body comes from the firewall: check the method and the path.\n- **`409` and `410`: the changes feed needs you to act.** `resync_required` and `sync_cursor_expired` ask for a [full resync](\u002Fdevelopers\u002Fsync#full-resync). `capture_not_ready` asks you to wait a few minutes, while the key's other teams keep syncing.\n- **`429`: slow down.** Wait the seconds in `Retry-After`, then retry the same request. `rate_limited` usually clears within seconds, but after an [authentication lockout](\u002Fdevelopers\u002Fauthentication#failed-attempts) it lasts :api-const{name=\"AUTH_FAILURE_LIMITS.banMs\" divide=\"1000\"} seconds. `quota_exceeded` lasts until 00:00 UTC, when the daily quota resets. A `429` from the firewall has no `Retry-After`: back off exponentially. [Rate limits](\u002Fdevelopers\u002Frate-limits) explains both limits.\n- **`5xx`: retry later.** Retry with exponential backoff, keeping your cursors. If it keeps failing, contact [Support](\u002Fdevelopers\u002Fsupport) with the `Totem-Request-Id`.\n\nIn every case, never save a changes-feed cursor after a failed request.\n\n## All error codes\n\nEach code has its own anchor, which is where `doc_url` points.\n\n::dev-error-catalog{:example=\"false\"}\n::\n","reference",{"title":6,"description":442},"developers\u002Ferrors","errors","QAfF5IgjmGoM3v3YfE9tG7G2r0_ihA6qr-Mq_ss0iB4",[457,472,498,541],{"section":458,"items":459},"start",[460,464,468],{"path":461,"title":462,"description":463},"\u002Fdevelopers","Overview","Read the leads, calls, conversations and bookings of your Totem teams from your own systems, and keep a copy in sync.",{"path":465,"title":466,"description":467},"\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":469,"title":470,"description":471},"\u002Fdevelopers\u002Fauthentication","Authentication","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":473,"items":474},"guides",[475,479,483,486,490,494],{"path":476,"title":477,"description":478},"\u002Fdevelopers\u002Ftypescript","TypeScript SDK","Use the official TypeScript client to read your Totem data, paginate lists and handle API errors from your server.",{"path":480,"title":481,"description":482},"\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":484,"title":256,"description":485},"\u002Fdevelopers\u002Fpagination","How list endpoints return records a page at a time, how to read every page, and what order and filters a list supports.",{"path":487,"title":488,"description":489},"\u002Fdevelopers\u002Fcoverage","Data coverage","What Totem records, since when, and how to tell an empty value from a fact that was never recorded.",{"path":491,"title":492,"description":493},"\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":495,"title":496,"description":497},"\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":451,"items":499},[500,504,505,507,512,517,522,527,532,537],{"path":501,"title":502,"description":503},"\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":449,"title":6,"description":442},{"path":401,"title":402,"description":506},"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.",{"path":508,"title":509,"description":510,"apiTag":511},"\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":513,"title":514,"description":515,"apiTag":516},"\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":518,"title":519,"description":520,"apiTag":521},"\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":523,"title":524,"description":525,"apiTag":526},"\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":528,"title":529,"description":530,"apiTag":531},"\u002Fdevelopers\u002Freference-bookings","Bookings and services","List and fetch a team's bookings, and list the services its customers can book.","bookings",{"path":533,"title":534,"description":535,"apiTag":536},"\u002Fdevelopers\u002Freference-sync","Changes feed","One endpoint that copies a team and then returns every change, page by page.","sync",{"path":538,"title":539,"description":540},"\u002Fdevelopers\u002Fobjects","All objects","Every object the API returns, field by field, with an example of each.",{"section":542,"items":543},"resources",[544,547,549,553],{"path":307,"title":545,"description":546},"Changelog","Changes to the Totem API, newest first, each under the date it shipped.",{"path":144,"title":145,"description":548},"How to get help with the Totem API, what to include in a request, and what to do if a key leaks.",{"path":550,"title":551,"description":552},"\u002Fdevelopers\u002Fglossary","Glossary","The terms these docs use, defined in one place, each with a link to the page that explains it.",{"path":554,"title":555,"description":556},"\u002Fdevelopers\u002Ffaq","FAQ","Short answers to the questions developers ask most about the Totem API, with links to the details.","\u002Fdevelopers\u002Fes\u002Ferrors",{"ACTIVATION_MARGIN_MS":559,"ADMIN_ACCESS_DISCLOSURE_VERSION":560,"AUDIT_RETENTION_DAYS":561,"AUTH_FAILURE_LIMITS":562,"CAPTURE_LAG_FLOOR_MS":566,"CAPTURE_LAG_P99_MS":7,"CURSOR_MAX_AGE_DAYS":567,"DIRTY_TTL_DAYS":567,"FAMILY_TEAM_SCOPE":568,"FAMILY_TEAM_SCOPE_OPTIONS":569,"FEED_SETTLE_LAG_MS":571,"GATE_REFRESH_MS":559,"INTEGRATION_NAME_LENGTH":572,"INTEGRATION_PURPOSE_LENGTH":574,"KEY_CACHE_TTL_MS":577,"KEY_STATS_RETENTION_DAYS":578,"LEAD_RESPONSE_READ_BUDGET":579,"LIST_SCAN_MAX":582,"MAX_FAMILY_INTEGRATION_TEAMS":567,"MAX_INTEGRATIONS_PER_FAMILY":583,"MAX_IP_ALLOWLIST":564,"PAGE_LIMIT":584,"PLATFORM_CONFIG_TTL_MS":587,"REMOVAL_RETENTION_DAYS":588,"REQUEST_BODY_MAX_BYTES":589,"ROLL_GRACE_DEFAULT_HOURS":590,"ROLL_GRACE_HOURS":591,"SEARCH_MAX_RESULTS":583,"SENSITIVE_SECTOR_POLICY":594,"SENSITIVE_SECTOR_POLICY_OPTIONS":595,"SYNC_DAILY_BUDGET":597,"SYNC_VELOCITY":599,"TEAM_CACHE_TTL_MS":601},60000,"2026-10-17",365,{"perIpPerMinute":563,"perLookupIdPerMinute":564,"banMs":565},60,20,600000,300000,30,"explicit_list",[568,570],"all_family_teams",10000,{"min":439,"max":573},80,{"min":575,"max":576},1,280,5000,90,{"conversations":564,"messageReads":580,"calls":581},200,50,1000,10,{"default":585,"max":586},25,100,15000,45,16384,24,[592,575,590,593],0,168,"exclude",[594,596],"allow",{"floor":598,"recordsMultiplier":436},250000,{"perMinute":600,"burst":571},2000,30000,"1.0a",{"operations":604,"schemas":605,"errors":606,"commonErrors":722,"defaultStability":723,"policy":558,"problemExample":724},[],[],[607,615,619,623,630,634,641,647,651,656,661,665,670,676,682,688,693,700,704,711,717],{"code":608,"status":609,"title":610,"wireTitle":610,"action":611,"description":612,"fix":613,"retryable":443,"retry":614},"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":260,"status":609,"title":616,"wireTitle":616,"action":611,"description":617,"fix":618,"retryable":443,"retry":614},"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":268,"status":609,"title":620,"wireTitle":620,"action":611,"description":621,"fix":622,"retryable":443,"retry":614},"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":624,"status":625,"title":626,"wireTitle":626,"action":627,"description":628,"fix":629,"retryable":443,"retry":614},"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":280,"status":625,"title":631,"wireTitle":631,"action":627,"description":632,"fix":633,"retryable":443,"retry":614},"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":635,"status":636,"title":637,"wireTitle":637,"action":638,"description":639,"fix":640,"retryable":443,"retry":614},"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":296,"status":636,"title":642,"wireTitle":642,"action":643,"description":644,"fix":645,"retryable":447,"retry":646},"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":299,"status":636,"title":648,"wireTitle":648,"action":627,"description":649,"fix":650,"retryable":443,"retry":614},"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":652,"status":636,"title":653,"wireTitle":653,"action":643,"description":654,"fix":655,"retryable":447,"retry":646},"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":303,"status":636,"title":657,"wireTitle":657,"action":643,"description":658,"fix":659,"retryable":443,"retry":660},"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":292,"status":636,"title":662,"wireTitle":662,"action":643,"description":663,"fix":664,"retryable":447,"retry":646},"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":320,"status":666,"title":667,"wireTitle":667,"action":611,"description":668,"fix":669,"retryable":443,"retry":614},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":324,"status":666,"title":671,"wireTitle":671,"action":672,"description":673,"fix":674,"retryable":443,"retry":675},"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":350,"status":677,"title":678,"wireTitle":678,"action":679,"description":680,"fix":681,"retryable":443,"retry":614},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":362,"status":677,"title":683,"wireTitle":683,"action":684,"description":685,"fix":686,"retryable":447,"retry":687},"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":353,"status":689,"title":690,"wireTitle":690,"action":679,"description":691,"fix":692,"retryable":443,"retry":614},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":377,"status":694,"title":695,"wireTitle":695,"action":696,"description":697,"fix":698,"retryable":447,"retry":699},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":391,"status":694,"title":701,"wireTitle":701,"action":696,"description":702,"fix":703,"retryable":447,"retry":699},"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":705,"status":706,"title":707,"wireTitle":707,"action":708,"description":709,"fix":710,"retryable":447,"retry":708},"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":712,"status":713,"title":714,"wireTitle":714,"action":708,"description":715,"fix":716,"retryable":447,"retry":708},"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":718,"status":713,"title":719,"wireTitle":719,"action":708,"description":720,"fix":721,"retryable":447,"retry":708},"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.",[608,268,624,280,635,296,299,292,377,705,712,718],"beta",{"type":725,"title":667,"status":666,"code":320,"request_id":726,"doc_url":725},"https:\u002F\u002Ftotemstudio.ai\u002Fdevelopers\u002Ferrors#resource_missing","req_0f6b2c1e-8d4a-4b7e-9c3f-5a2d1e7b9c40","guide",[729,730,731],{"id":18,"text":19,"depth":439},{"id":227,"text":228,"depth":439},{"id":423,"text":424,"depth":439},{"path":501,"title":502,"section":451},{"path":401,"title":402,"section":451},[],1792502788743]