Bulk Import and Cursor-Paginated Exports

Updated April 2026 · 6 min read

Once you are managing more than a handful of domains, the marginal cost of clicking around a UI starts to dominate. GuardHound's bulk import lets you onboard hundreds of monitors from a CSV in one shot, and the export endpoints let you stream that data back out into your warehouse, BI tool, or SIEM.

Bulk Import

The Bulk Import wizard accepts a CSV with one row per monitor or domain. The required columns are type, target, and name; optional columns include interval_seconds, keyword, port, and any tag fields you want to apply.

The wizard validates the file in two phases: a parse pass that flags malformed rows, and a plan pass that surfaces conflicts with existing monitors and quota limits. You then approve the plan and the import runs in the background — you do not have to keep the tab open.

Bulk import is available on Pro ($49/mo), Team ($79/mo), and Unlimited ($99/mo).

What You Can Export

• Monitors — current configuration and last-known status.
• Incidents — full incident history including timeline updates.
• Scan history — per-dimension scores and findings across time.
• Per-domain bundles — everything for a single domain, ready to hand to a customer or auditor.

Each endpoint supports CSV and JSON output and is cursor-paginated so you can pull arbitrarily large datasets without blowing up memory on either end.

Cursor Pagination

Every export response includes a next_cursor field. To page through, pass it back as ?cursor=... on the next request. Cursors are stable across new writes — new rows added during a long export show up on subsequent runs, not as duplicates in the current one.

curl -H "Authorization: Bearer $GH_TOKEN" \
     "https://guardhound.io/api/v1/exports/incidents?format=csv"

See the OpenAPI docs for the full parameter reference.

API Scopes

Exports require an API key. Pro and Unlimited plans expose four scopes:

• full — read/write everything.
• read_only — read everything, write nothing.
• monitors — manage monitors only.
• incidents — read incidents and post timeline updates.

Use the narrowest scope that gets the job done; tokens can be rotated at any time from the dashboard.

Loading into a Warehouse

The CSV exports are warehouse-friendly: stable column order, ISO-8601 timestamps, no embedded newlines in string fields. A typical pattern is to schedule a daily job that pulls the incidents and scan-history exports incrementally (using the cursor) and lands them in your data lake. From there, normal BI tools can build long-term reliability dashboards on top of GuardHound data.