Hyros API

Name: Hyros API
Brand: Hyros API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsProduct Analyticsbearer3 EndpointsREST

For Agents

Send leads, sales, and custom user events into Hyros for ad attribution and conversion tracking. Useful for piping CRM and checkout data into paid-media reporting.

Install Jentic One Beta

Connect the Hyros API to your agent

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

Submit a new lead record with email, phone, and tracking identifiers to /v1/leads

Log a completed sale transaction with amount, currency, and customer identifiers to /v1/sales

Record a custom user event such as a webinar registration or upsell click to /v1/events

GET STARTED

Start building with Hyros API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Hyros API, keeping it validated and agent-ready. Hyros is an ad attribution and tracking platform used by direct-response advertisers to tie ad spend to revenue across paid channels. The API exposes three core write endpoints that let you submit lead records, log sales transactions, and record custom user events so Hyros can stitch them into multi-touch attribution reports. It is suited for ingesting first-party conversion data from checkout pages, CRMs, and call centres into the Hyros tracking model.

Use Cases

Patterns agents use Hyros API for, with concrete tasks.

★ Offline Conversion Import

Push closed-won deals from a CRM into Hyros so phone and field sales are attributed to the ad click that generated the lead. Records sent to /v1/sales include the original tracking ID, currency, and amount so Hyros can credit the right ad source. Typical setup wires a CRM webhook to a Jentic toolkit and runs in under a day.

Post a sale of 1499.00 USD with the lead email and Hyros tracking ID to /v1/sales when a CRM deal moves to Closed Won.

Checkout Lead Capture

Submit lead records from a checkout or opt-in form to Hyros via /v1/leads as soon as the visitor enters contact details, before payment completes. This lets Hyros track the visitor across devices and attribute the eventual sale to the original ad. Useful for funnels with a two-step checkout or a high-ticket offer that closes by phone.

Send a lead with email, first name, and the visitor's Hyros click ID to /v1/leads when an opt-in form is submitted.

Custom Event Logging

Record arbitrary funnel events such as webinar registrations, demo bookings, or upsell views to /v1/events so they appear alongside leads and sales in Hyros reports. Each event carries a name, a timestamp, and the user identifier needed to link it to an existing tracked visitor. This makes it possible to optimise paid campaigns against intermediate funnel signals, not only purchases.

Send a custom event named webinar_registered with the user email and timestamp to /v1/events when a registration is confirmed.

AI Agent Conversion Sync

An AI agent triggered by a CRM or e-commerce platform searches Jentic for the Hyros operation that submits a sale, loads its schema, and posts the conversion. Because Hyros has only a handful of endpoints, an agent can cover the full reporting surface with three operations and reliably reconcile conversion data without hand-rolled integration code. Typical end-to-end agent integration is under one hour through Jentic.

Use Jentic search for 'log a sale in Hyros', load the /v1/sales schema, and post the order with tracking ID, amount, and currency.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for hyros api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/leads

Submit a new lead record

POST

/v1/sales

Log a sale transaction

POST

/v1/events

Record a custom user event

POST

/v1/leads

Submit a new lead record

POST

/v1/sales

Log a sale transaction

POST

/v1/events

Record a custom user event

Why Jentic?

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

Credential isolation

Hyros bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped Jentic credentials and never see the raw Hyros token in their context.

Intent-based discovery

Agents search Jentic by intent (for example 'log a sale in Hyros') and Jentic returns the matching POST operation with its input schema, so the agent can call the correct endpoint without reading Hyros docs.

Time to first call

Direct Hyros integration: half a day to a day for auth, payload shaping, and retries. Through Jentic: under one hour — search, load schema, execute.

FAQs

Specific to using Hyros API through Jentic.

Why is there no official OpenAPI spec for Hyros API?

Hyros does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Hyros API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Hyros API use?

The Hyros API uses HTTP bearer token authentication. Through Jentic, the Hyros bearer token is stored in the Jentic vault and never enters the agent's prompt context — agents call Hyros operations using a scoped Jentic credential instead of the raw token.

Can I submit offline sales to Hyros through this API?

Yes. POST a record to /v1/sales with the customer email, the original Hyros tracking ID, the sale amount, and the currency. Hyros uses the tracking ID to attribute the offline sale back to the ad click that generated the lead.

How many endpoints does the Hyros API expose?

The current spec covers three POST endpoints: /v1/leads, /v1/sales, and /v1/events. These are the write operations Hyros uses to ingest funnel data — read-side reporting is done in the Hyros dashboard, not via this API.

How do I send a custom event to Hyros through Jentic?

Search Jentic for 'log a custom event in Hyros', load the /v1/events schema, and execute the call with the event name, timestamp, and user identifier. Install the SDK with pip install jentic and run the search, load, and execute steps with await.

What are the rate limits for the Hyros API?

The published spec does not declare rate limits. Hyros enforces account-level limits documented in their developer portal at hyros.com — start with conservative batching (a few requests per second) and back off on 429 responses.

Hyros API

Connect the Hyros API to your agent

Capabilities

Start building with Hyros API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs