Geckoboard Datasets API

Name: Geckoboard Datasets API
Brand: Geckoboard Datasets API
Availability: InStock

✓ Official Vendor SpecAnalyticsBusiness Intelligencebasic6 EndpointsREST

For Agents

Push custom datasets to Geckoboard for real-time dashboard visualisation, and append, replace, or delete records by dataset id.

Install Jentic One Beta

Connect the Geckoboard Datasets API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Geckoboard Datasets API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Geckoboard Datasets API.

Verify API credentials by calling GET / before pushing any data

Find or create a dataset with a typed schema using PUT /datasets/{dataset_id}

Append records to an existing dataset via POST /datasets/{dataset_id}/data without overwriting history

GET STARTED

Start building with Geckoboard Datasets API

Explore with Jentic

View OpenAPI Document

The Geckoboard Datasets API lets teams push their own structured data into Geckoboard, where it is then displayed on real-time KPI dashboards on TVs, monitors, and team boards. The API exposes six operations covering dataset definition (find or create with a typed schema), full append, batch append, replace, and delete, alongside a root verification endpoint. Auth is HTTP Basic with the Geckoboard API key as the username — no separate OAuth flow. It is purpose-built for teams that already have data in a warehouse, app, or script and need it visible on a wall display in seconds.

Use Cases

Patterns agents use Geckoboard Datasets API for, with concrete tasks.

★ Wall-Display KPIs From An Internal App

Stream live counters — orders per hour, active users, support tickets — from your own backend to a Geckoboard wall display. The agent calls PUT /datasets/{dataset_id} once to define the schema, then POST /datasets/{dataset_id}/data on every update to append rows. Replaces fragile screenshot-based status TVs.

PUT /datasets/orders_hourly with the typed schema, then POST /datasets/orders_hourly/data with the latest hour's record on a 5-minute cron

Snapshot Reporting For Sales Pipelines

Replace the Geckoboard dataset entirely each evening with the current state of the sales pipeline so the morning standup board shows live deal counts by stage. The agent calls PUT /datasets/{dataset_id}/data with the full payload, eliminating drift between CRM and dashboard.

PUT /datasets/sales_pipeline/data with the full array of {stage, count, value} rows queried from the CRM at midnight

Batch Append From An ETL Job

When an ETL run finishes, push only the rows that changed instead of replacing the whole dataset. The agent batches the new records and calls POST /datasets/{dataset_id}/data with up to the supported batch size, leaving historical rows in place. Reduces network volume and keeps Geckoboard's history charts intact.

POST /datasets/{dataset_id}/data with the batch of records produced by the ETL run; rerun on next ETL trigger

Agent-Driven Dashboarding Through Jentic

AI agents discover Geckoboard via Jentic, load the dataset push operation, and stand up a live KPI board for a team in minutes — without writing a custom client. Jentic isolates the basic-auth API key in its vault. Useful for ops bots that surface anomalies on a shared display.

Use Jentic search query 'push data to a Geckoboard dataset' to load the geckoboard_push_data tool and execute with dataset_id and the records array

Key Endpoints

6 endpoints — the geckoboard datasets api lets teams push their own structured data into geckoboard, where it is then displayed on real-time kpi dashboards on tvs, monitors, and team boards.

METHOD

PATH

DESCRIPTION

GET

Verify the API key with a no-op root call

PUT

/datasets/{dataset_id}

Find or create a dataset with a typed schema

POST

/datasets/{dataset_id}/data

Append records to a dataset

PUT

/datasets/{dataset_id}/data

Replace all records in a dataset

DELETE

/datasets/{dataset_id}

Delete a dataset

GET

Verify the API key with a no-op root call

PUT

/datasets/{dataset_id}

Find or create a dataset with a typed schema

POST

/datasets/{dataset_id}/data

Append records to a dataset

PUT

/datasets/{dataset_id}/data

Replace all records in a dataset

DELETE

/datasets/{dataset_id}

Delete a dataset

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Geckoboard API keys are stored encrypted in the Jentic vault. Agents call operations with a scoped execution token; Jentic constructs the Basic-auth header at execution time so the key never enters the agent context.

Intent-based discovery

Agents search by intent (e.g. 'push data to a Geckoboard dataset') and Jentic returns the right operation among the six endpoints, with input schema, so the agent does not have to choose between PUT and POST on /data manually.

Time to first call

Direct Geckoboard integration: 2-4 hours to model the schema, wire basic auth, and test append vs replace. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using Geckoboard Datasets API through Jentic.

What authentication does the Geckoboard Datasets API use?

HTTP Basic with the Geckoboard API key as the username and an empty password. Through Jentic the key is stored encrypted in the vault and the basic-auth header is injected per request.

Can I append records to a Geckoboard dataset without replacing it?

Yes. POST /datasets/{dataset_id}/data appends the supplied records and preserves existing history, which is the right call for incremental ETL updates.

How do I create a new dataset with the Geckoboard API?

Call PUT /datasets/{dataset_id} with a typed schema. The endpoint is find-or-create — if a dataset with that id already exists with a matching schema, the call is a no-op; otherwise it is created.

What are the rate limits for the Geckoboard Datasets API?

Geckoboard does not declare rate-limit headers in the spec. Treat HTTP 429 as a back-off signal and follow Geckoboard's published guidance on push frequency in their documentation.

How do I delete a Geckoboard dataset?

Call DELETE /datasets/{dataset_id}. The dataset and all its records are removed from your Geckoboard account, so widgets bound to that id will stop rendering.

How do I push data through Jentic?

Install with pip install jentic, search 'push data to a Geckoboard dataset', load the geckoboard_push_data operation schema, and execute with the dataset id and the records array.

Geckoboard Datasets API

Connect the Geckoboard Datasets API to your agent

Capabilities

Start building with Geckoboard Datasets API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs