Meta tags:
description=Authenticate to the Chronicle API with a workspace-scoped API key.;

Headings (most frequently used words):

api, key, authentication, reference, using, documentation, index, create, an, use, the, store, keys, securely, errors, faqs, related, posts, on, this, page, get, started, authorization,

Text of the page (most frequently used words):
key (38), api (35), the (27), chronicle (13), keys (12), and (11), workspace (11), create (10), use (9), get (9), page (8), your (8), copy (7), #authentication (6), store (6), developer (6), only (6), presentations (6), authorization (5), can (5), when (5), docs (5), securely (4), using (4), this (4), documentation (4), reference (4), once (4), are (4), you (4), with (4), that (4), api_key (4), post (4), for (3), request (3), revoked (3), rate (3), one (3), each (3), see (3), resources (3), 403 (3), bearer (3), send (3), never (3), settings (3), templates (3), generate (3), started (3), search (3), related (2), posts (2), faqs (2), errors (2), introduction (2), error (2), codes (2), quickstart (2), longer (2), than (2), requests (2), limited (2), per (2), resource (2), belongs (2), bound (2), scoped (2), but (2), why (2), valid (2), manager (2), raw (2), method (2), consistently (2), across (2), integration (2), returned (2), header (2), secure (2), access (2), revoke (2), immediately (2), environment (2), chronicle_api_key (2), curl (2), https (2), chroniclehq (2), com (2), fetch (2), support (2), home (2), generationid (2), index (2), built, hosted, mintlify, platform, powered, website, linkedin, next, endpoints, formats, responses, previous, used, rather, hard, deleted, preserves, audit, visibility, delete, hit, limit, reduce, frequency, retry, backoff, learn, more, yes, most, common, cause, different, its, own, means, was, accepted, action, not, permitted, getting, even, though, secret, lose, new, security, reasons, shows, did, either, how, public, rest, user, token, outside, single, forbidden, auth, malformed, expired, invalid, missing, 401, unauthorized, keep, share, them, publicly, provides, full, compromised, from, separate, possible, needed, rotate, periodically, commit, source, control, expose, frontend, applications, server, side, code, supported, headers, include, every, location, such, variable, secrets, will, shown, click, web, app, open, specific, let, application, update, behalf, authenticate, navigation, help, changelog, troubleshooting, scope, limits, mcp, setup, message, status, uploads, target, patch, overview, skip, main, content, file, discover, all, available, pages, before, exploring, further, complete, llms, txt,

Text of the page (random words):
authentication 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 get started authentication developer docs developer docs get started authentication copy page copy page authenticate to the chronicle api with a workspace scoped api key copy page copy page api keys let your application create generate fetch and update presentations on behalf of a chronicle workspace when you create a key it belongs to a specific workspace it can access resources in that workspace create an api key 1 open api settings go to settings api in the chronicle web app 2 create a key click create api key 3 copy and store securely copy the key immediately it will only be shown once store it in a secure location such as an environment variable or secrets manager use the api key include the key in the header with every request supported headers authorization bearer api_key x api key api_key use one method consistently across your integration using authorization curl x get https api chroniclehq com api v1 templates h authorization bearer chronicle_api_key using x api key curl x get https api chroniclehq com api v1 templates h x api key chronicle_api_key store keys securely use api keys only in server side code never expose keys in frontend applications never commit keys to source control rotate keys periodically revoke keys that are no longer needed use separate keys per environment when possible keep your api keys secure and never share them publicly each key provides full access to your chronicle workspace if a key is compromised revoke it immediately from the settings page authentication errors 401 unauthorized returned when the key is missing the key is invalid the key is expired the key is revoked the auth header is malformed 403 forbidden returned when the key is valid but the resource is outside the key s workspace each api key is bound to a single workspace and can only see resources in that workspace faqs do i use an api key or a user token use an api key for the public rest api create the key in chronicle store it securely and send it with requests to api v1 how do i send my api key send it as either authorization bearer api_key x api key api_key use one method consistently across your integration why did i only see the raw key once for security reasons chronicle only shows the raw api key once copy it when you create it and store it in your secret manager if you lose it create a new key why am i getting 403 even though my key is valid a 403 means your key was accepted but the action is not permitted the most common cause is that the resource belongs to a different workspace than the one your key is bound to each key is workspace scoped and can only see resources in its own workspace are api keys rate limited yes requests are rate limited per api key if you hit the limit reduce request frequency and retry with backoff learn more can i delete an api key keys are revoked rather than hard deleted this preserves audit visibility once revoked the key can no longer be used related posts quickstart api reference error codes previous introduction reference for chronicle api endpoints request formats and responses next i x linkedin website powered by this documentation is built and hosted on mintlify a developer documentation platform on this page create an api key use the api key using authorization using x api key store keys securely authentication errors faqs related posts