Chartbrew API reference

What authentication does the Chartbrew API reference use?

The Chartbrew API uses HTTP bearer-token authentication. Every request must include an Authorization header of the form 'Bearer <token>'. Through Jentic, the bearer token is stored in your encrypted Jentic One instance and never exposed to the agent's prompt context.

Can I create a public shareable dashboard with the Chartbrew API?

Yes. Create a project, then call POST /project/{id}/share/token to generate a share token. You can also configure granular access through POST /project/{id}/share/policy. The returned token resolves to a public dashboard URL that can be embedded in another site.

How do I refresh just one chart without rebuilding the whole dataset?

Call POST /team/{team_id}/datasets/{dataset_id}/dataRequests/{id}/request. This runs a single data request bound to one chart, which is the right approach when an upstream ETL job finishes and only some charts need fresh data.

How do I build a Chartbrew dashboard through Jentic?

Run pip install jentic, set JENTIC_AGENT_API_KEY, then search 'create a chartbrew dashboard'. Jentic returns the create-team, create-connection, create-dataset, create-project, and create-chart operations with their input schemas so the agent can chain the calls without browsing docs.

Are there documented rate limits for the Chartbrew API?

The OpenAPI specification does not declare rate-limit headers or quotas, and Chartbrew is typically self-hosted, so limits are governed by the deployment's own infrastructure rather than a vendor-imposed quota. Check the headers on a 429 response from your specific instance to learn its limits.

Can I limit what my agent is allowed to do with the Chartbrew API?

Yes. Because you run Jentic One yourself, your own rules decide which Chartbrew operations and credentials the agent can use, and Chartbrew puts the team and project ids directly in the URL path (/team/{team_id}/... and /project/{project_id}/...), so a rule can pin the agent to one team or project. You choose exactly which calls it may make, such as adding connections, datasets, and charts to that scope while leaving everything else off. Creating new teams is not included unless you explicitly grant it, and the bearer token stays with your instance rather than the agent's context.