Skip to main content
POST /v1/monitors is the proposed interface for scheduled collection. Monitoring endpoints and webhook delivery are not available yet.

​
Bound the workload

Choose carriers, routes, explicit departure dates or a date window, trip duration rules, traveller mix and refresh cadence. Return searches expand into exact outbound/return combinations. A large date range is not a single billable search.

​
Estimate before dispatch

For a simple one-way workload: credits = carriers × routes × departure dates × runs × source weight For sources with different weights, sum the cost per source. Include return-date combinations and passenger/cabin/market variations separately. Set a run budget and monthly cap before enabling a monitor. Example: 2 carriers × 10 routes × 30 departure dates × 1 run/day × 30 days × 1 credit = 18,000 credits/month. This calculation assumes all requested source queries complete successfully and excludes extra return-date combinations.

​
Delivery and gaps

Each run should report requested and returned scope, failed source queries and timestamps. Delivery may be scoped as API retrieval, JSONL export or a signed webhook. Retryable delivery should reuse a delivery ID so your consumer can deduplicate it. A failed capture must remain a gap. Do not replace it with an earlier fare and label it fresh. A successful source search with no offers is a separate result.