Thruk REST API

Name: Thruk REST API API
Brand: Thruk REST API
Availability: InStock

✓ Official Vendor SpecCommunicationsPush NotificationsapiKey, basic42 EndpointsREST

For Agents

Programmatically list all hosts, get a specific host. Covers 42 operations with apiKey, basic authentication.

Use for: I need to all hosts, I want to a specific host, Search for schedule downtime for a host, Find all all services

Connect the Thruk REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Thruk REST 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.

Install Jentic One Beta (Self-Hosted)

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

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 Thruk REST API API.

List all hosts

Get a specific host

Schedule downtime for a host

Query and filter Thruk REST API records by parameters

Monitor Thruk REST API operational status and events

GET STARTED

Start building with Thruk REST API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Thruk REST API API for, with concrete tasks.

★ Communications Operations

Use the Thruk REST API to perform communications operations programmatically. The API provides 42 endpoints covering core functionality including list all hosts, get a specific host, schedule downtime for a host.

Call GET /hosts to list all hosts

Automated Alerts Management

Automate alerts operations by combining multiple Thruk REST API endpoints. Agents can get a specific host and then schedule downtime for a host in a single workflow.

Call GET /hosts/{name} to get a specific host, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Thruk REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, basic tokens manually.

Search Jentic for 'list all hosts', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

42 endpoints — thruk rest api exposes monitoring data from naemon, nagios, icinga, and shinken monitoring systems.

METHOD

PATH

DESCRIPTION

GET

/hosts

List all hosts

GET

/hosts/{name}

Get a specific host

POST

/hosts/{name}/cmd/schedule_host_downtime

Schedule downtime for a host

GET

/services

List all services

GET

/hosts/{hostName}/services/{description}

Get a specific service

GET

/hostgroups

List all host groups

GET

/servicegroups

List all service groups

GET

/contacts

List all contacts

GET

/hosts

List all hosts

GET

/hosts/{name}

Get a specific host

POST

/hosts/{name}/cmd/schedule_host_downtime

Schedule downtime for a host

GET

/services

List all services

GET

/hosts/{hostName}/services/{description}

Get a specific service

Why though Jentic?

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

Credential isolation

Thruk REST API apiKey, basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list all hosts') and Jentic returns the matching Thruk REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Thruk REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using Thruk REST API API through Jentic.

What authentication does the Thruk REST API use?

The Thruk REST API uses apiKey, basic authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I list all hosts with the Thruk REST API?

Yes. Use the GET /hosts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Thruk REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I list all hosts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list all hosts'. Jentic returns the matching Thruk REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Thruk REST API have?

The Thruk REST API exposes 42 endpoints covering alerts, checks, cmd operations.