Meta tags:
description=What the Chronicle v1 API covers, rate limits and how to work within its current scope.;

Headings (most frequently used words):

api, scope, rate, limits, the, reference, and, documentation, index, what, covers, polling, generation, jobs, production, best, practices, related, posts, on, this, page, get, started, working, outside, current,

Text of the page (most frequently used words):
api (18), the (17), presentations (15), generation (13), and (13), status (11), get (11), rate (10), chronicle (9), for (9), #limits (8), error (8), generate (8), post (8), polling (7), scope (7), page (7), presentation (7), developer (6), codes (6), reference (6), generationid (6), response (5), content (5), docs (5), documentation (4), job (4), poll (4), message (4), example (4), can (4), create (4), templates (4), copy (4), current (3), what (3), covers (3), this (3), from (3), failures (3), available (3), when (3), 429 (3), per (3), key (3), use (3), after (3), patch (3), target (3), fetch (3), search (3), related (2), posts (2), production (2), best (2), practices (2), jobs (2), working (2), outside (2), shape (2), troubleshooting (2), your (2), too (2), not (2), transient (2), messages (2), log (2), request (2), see (2), asynchronous (2), how (2), requests (2), images (2), input (2), template (2), completed (2), you (2), files (2), complete (2), title (2), new (2), with (2), endpoint (2), pages (2), update (2), metadata (2), send (2), follow (2), during (2), uploads (2), list (2), support (2), home (2), index (2), built, hosted, mintlify, platform, powered, website, linkedin, next, common, http, previous, integration, performs, most, reliability, issues, come, aggressively, handling, well, tip, avoid, aggressive, loops, surface, useful, operators, retry, only, types, ids, handle, timeouts, gracefully, back, off, repeated, stop, reaches, terminal, state, reasonable, interval, workflows, are, fits, into, client, behavior, limit, exceeded, api_key_rate_limited, code, limited, should, return, many, minute, policy, may, apply, charts, diagrams, prompted, through, text, more, predictable, layouts, based, generating, structured, includes, url, viewing, output, there, export, present, needed, exporting, uses, model, creating, until, failed, waiting, does, modify, slide, updated, via, any, other, change, revised, updating, field, details, linked, start, presigned, uploading, attachment, existing, description, method, rest, workspace, scoped, valid, upload, https, chroniclehq, com, work, within, its, navigation, help, changelog, mcp, setup, introduction, authentication, quickstart, overview, started, skip, main, file, discover, all, before, exploring, further, llms, txt,

Text of the page (random words):
api scope and rate limits chronicle developer docs documentation index fetch the complete documentation index at llms txt use this file to discover all available pages before exploring further skip to main content chronicle developer docs home page search k get started overview quickstart authentication api reference introduction get templates get presentations id post presentations patch presentations id post uploads create target post presentations generate get generationid status post presentations generate generationid message reference mcp setup api scope and rate limits error codes troubleshooting changelog get help support go to chronicle chronicle developer docs home page search k support go to chronicle go to chronicle search navigation reference api scope and rate limits developer docs developer docs reference api scope and rate limits copy page copy page what the chronicle v1 api covers rate limits and how to work within its current scope copy page copy page what the api covers the rest api at https api chroniclehq com api v1 is workspace scoped with a valid api key you can list templates create and fetch presentations update presentation metadata upload reference files poll job status and send follow up messages during generation method endpoint description get templates list available templates get presentations id fetch an existing presentation post presentations create a new presentation from a template post uploads create target get a presigned s3 target for uploading an attachment post presentations generate start an ai presentation generation job get presentations generate generationid status poll generation job status post presentations generate generationid message send a follow up message during generation patch presentations id update presentation metadata for example title for request and response field details use the linked endpoint pages working outside the current scope updating content after generation the api does not modify slide content after generation title can be updated via patch presentations id for any other content change generate a new presentation with the revised input waiting for generation to complete the api uses an asynchronous polling model after creating a generation poll get presentations generate generationid status until the status is completed or failed exporting files a completed presentation includes a url for viewing the output from there you can export present as needed generating images and structured content images charts and diagrams can be prompted through your input text for more predictable layouts use the template based generation rate limits chronicle may apply rate limits per api key example policy 20 requests per minute per key when rate limited the api should return 429 too many requests example response example response error code api_key_rate_limited message rate limit exceeded status 429 for how 429 fits into client behavior see error codes polling generation jobs generation workflows are asynchronous when polling poll at a reasonable interval stop polling when the job reaches a terminal state back off on repeated failures handle timeouts gracefully see get presentations generate generationid status for the status response shape production best practices log request ids if available log status codes and error types retry only transient failures surface useful error messages to operators avoid aggressive polling loops tip if your integration performs generation most reliability issues come from polling too aggressively or not handling transient failures well related posts error codes api reference troubleshooting previous error codes chronicle api error response shape and common http status codes next i x linkedin website powered by this documentation is built and hosted on mintlify a developer documentation platform on this page what the api covers working outside the current scope rate limits polling generation jobs production best practices related posts