When your data changes, know it.
Watch an API on your schedule. Track the fields that matter and deliver signed change events to your application.
$.price- Schedules from 5 minutes to 7 daysChoose the cadence your workflow needs.
- Up to 20 JSONPath fieldsCompare selected fields or the full response.
- HMAC-signed change eventsVerify notifications at your receiver.
See a status change become a useful alert.
Watch a checkout-status API on the left. ApiClay compares the next response with the saved value and prepares a signed webhook when it changes. The right side shows how your own receiver can turn that event into a team alert.
From your input to a useful result.
- Choose a sample input
- Apply the feature’s workflow
- Inspect the result
This example runs entirely in your browser with illustrative data. Use the real feature’s guide and listing to check supported inputs, access rules, and pricing.
Explore the example, then use the setup guide to try the real feature.
Project setup and what to check
Input: An accessible API route, a polling schedule, and a webhook destination. Pick relevant JSONPath fields or watch the whole response payload.
Workflow: Establish a baseline and poll the route. When the watched value changes, ApiClay emits a signed monitor.changed event to your configured receiver.
Result: A change event your application can use to refresh cached data, create a review task, or notify a team through its existing tools.
Verify the HMAC signature in your receiver and test event handling. Implement business thresholds and notification rules in the receiver; a value change alone may not need an alert.
From a changing response to a useful signal.
Track the fields that matter. Let your application decide what happens next.
- 1
Choose your API
Select a route and test its inputs and response.
- 2
Track the right fields
Set a schedule and choose the JSONPath values to compare.
- 3
Connect your receiver
Verify the signed webhook and review delivery history.
Watch the change that matters.
Compare selected fields instead of reacting to an unrelated timestamp elsewhere in the response.
- Poll from every 5 minutes to every 7 days.
- Track a full-response hash or up to 20 JSONPath fields.
- Verify webhook signatures and handle repeated deliveries safely.
Example comparison only. The monitor reports changes; price thresholds and downstream actions belong in your webhook receiver.
$.price
$.in_stock
Schedule: every 1 hour
Comparison: selected JSONPath fields
Delivery: your HTTPS webhook receiverField Previous Current
price 49.00 45.00
in_stock false true
Event type: monitor.changed
Delivery signature: HMAC-SHA256
Your receiver decides whether to send an alert.Changes without the noise
Compare selected values so an unrelated timestamp does not trigger a change event.
A notification you can verify
Validate HMAC-SHA256 signatures and handle repeated deliveries safely.
Scheduled API change detection without a custom cron service
Many useful APIs only answer when you call them. A supplier's stock feed, a registry lookup, or a changing pricing endpoint may provide no native event stream. ApiClay Monitors adds a polling and change-detection workflow to a configured route, so your application can react when new information arrives.
Choose whether to compare the complete response or a focused set of JSONPath fields. Send detected changes to your own webhook receiver, where your business rules decide what should happen next. A monitor detects changes on completed polls; its schedule is different from an upstream system pushing events immediately.
Watch the entire response or selected fields
Full-response comparison uses a SHA-256 digest to identify payload changes.
How it works
Targeted JSONPath comparisons focus on fields relevant to your workflow. Tracking a price or availability field can avoid notifications caused by unrelated changes elsewhere in the payload, such as a generated timestamp.
Separate detection from your business rules
A monitor.changed event reports a detected difference.
How it works
Your webhook receiver can then check whether a price decreased, inventory crossed a threshold, or a status moved to a particular value. This keeps alert conditions and downstream actions under your application's control instead of treating every change as the same business event.
Authenticate notifications at the receiver
Webhook delivery uses HMAC-SHA256 signatures so your receiver can check message authenticity.
How it works
Store the signing secret securely and reject messages that fail verification. Delivery destinations are subject to safety checks; choose an HTTPS receiver that ApiClay can reach and that responds promptly.
Inspect polling and delivery outcomes
Run history and delivery logs let you distinguish an API execution problem from an unreachable webhook.
How it works
Delivery has up to three attempts. Manual runs support setup and diagnosis without waiting for the next scheduled poll. Your receiver should handle repeated delivery safely and record the events it processes.
Where this fits into your work.
Price and inventory updates
Track a supplier route's price and stock fields. Let your receiver determine whether to notify a buyer, review a reorder, or update an internal report.
Registry and research changes
Watch a listing or status endpoint for new information. Store the detected change as a research event with the source and polling time.
Operations notifications
Poll an approved operational API and forward relevant changes through your own Slack, Make, Zapier, or service integration webhook receiver.
Start with a focused test.
Use these steps to set up API Monitors and review the result before making it part of a larger workflow.
Create an API monitor →- 1
Choose the route and inputs
Select an API route, configure its request parameters, and run a sample request. Use a route with a stable response shape for reliable comparisons.
- 2
Set the schedule and comparison
Poll every 5 minutes to 7 days. Compare the full response or track up to 20 JSONPath expressions such as $.price or $.in_stock.
- 3
Connect and verify your webhook
Add your receiver, verify the HMAC signature in your application, and inspect run and delivery logs. Manual runs help test the complete flow.
Understand each workflow’s cost.
Match the feature’s limits and billing model to the work you want to run.
Explore API listings →Scheduled polls execute the selected API route and follow its applicable usage and infrastructure charges, even when the tracked response has not changed. A change notification and a successful poll are different outcomes.
Choose the polling interval based on how quickly the source changes and how much spend the workflow justifies. Keep sufficient credits available and inspect failed runs rather than assuming an unchanged notification stream means the source is unchanged.
Open an API listing for its Reference, Playground, and Pricing. Check the selected route’s allowances and applicable infrastructure charges before increasing usage.
FAQs
Are notifications instantaneous?
Monitors poll on a schedule, so changes are detected on a subsequent successful poll. The shortest supported interval is five minutes; delivery also depends on the route and your receiver.
Can I monitor only one field?
Yes. Configure JSONPath expressions for the fields you need, up to 20 per monitor. Choose fields with stable meanings and test the paths against a real route response.
Will I be charged when nothing changes?
Successful scheduled calls still consume the selected route's applicable usage and add-ons. The webhook is triggered by a detected change, but polling is required to discover whether anything changed.
Can monitors send threshold alerts?
Use a monitor to detect the relevant field change, then evaluate the threshold in your webhook receiver or downstream automation. A change event by itself is not a built-in business-rule threshold engine.
Stay ahead of the next change.
Create a monitor and connect live API changes to your workflow.