Setting Up API Monitoring in 3 Minutes with Rumbliq

This is a quick-start tutorial for developers who want API monitoring running now, not after reading a 50-page docs site.

By the end of this post, you'll have:

A Rumbliq account (free, no credit card)
A monitor running against a real API endpoint
An alert configured to fire when the schema changes

Let's go.

Minute 0: What You Need Before You Start

One thing: an API endpoint URL you want to monitor.

This can be:

A third-party API your code depends on (Stripe, Twilio, GitHub, etc.)
One of your own internal API endpoints
A public API endpoint you want to track

If you have a specific endpoint in mind, great. If not, use the Stripe test API — it's a realistic example and has test credentials that work for monitoring:

https://api.stripe.com/v1/payment_methods
Authorization: Bearer sk_test_4eC39HqLyjWDarjtT1zdp7dc

Step 1: Sign Up (30 seconds)

Go to rumbliq.com/signup.

Enter your email and password. That's it — no credit card, no company details, no questionnaire.

You'll get a verification email. Click the link. You're in.

The free plan includes 25 monitors. That covers most teams' critical integrations without touching a payment form.

Step 2: Create Your First Monitor (60 seconds)

From the dashboard, click New Monitor.

You'll see a form with a few fields:

Name — something descriptive. "Stripe Payment Methods" or "GitHub Repos API" works fine.

URL — paste your endpoint URL here.

Method — GET for most read endpoints, POST if you're monitoring a write endpoint with a test payload.

Interval — how often to check. The free plan minimum is 3 minutes. For critical endpoints on paid plans, you can go down to 30 seconds.

For a Stripe payment methods endpoint, fill it in like this:

Name: Stripe Payment Methods
URL: https://api.stripe.com/v1/payment_methods?type=card
Method: GET
Interval: 3 minutes

If your endpoint requires authentication (most do), click Add Header and add your auth header:

Key: Authorization
Value: Bearer sk_test_...

Rumbliq stores header values encrypted. The raw API key is never exposed after initial entry.

Click Create Monitor.

Step 3: Let Rumbliq Capture the Baseline (30 seconds)

When you create a monitor, Rumbliq immediately makes its first check. It captures the response, extracts the JSON schema, and stores that as your baseline.

You'll see the monitor appear in your dashboard with a Running status and a green badge once the first check succeeds.

Click into the monitor to see the captured baseline schema. For a Stripe payment methods response, it'll show something like:

{
  "object": "string",
  "data": [
    {
      "id": "string",
      "object": "string",
      "billing_details": {
        "address": "object",
        "email": "null | string",
        "name": "null | string",
        "phone": "null | string"
      },
      "card": {
        "brand": "string",
        "checks": "object",
        "country": "string",
        "exp_month": "number",
        "exp_year": "number",
        "fingerprint": "string",
        "funding": "string",
        "last4": "string"
      },
      "created": "number",
      "customer": "null | string",
      "livemode": "boolean",
      "type": "string"
    }
  ],
  "has_more": "boolean",
  "url": "string"
}

This is now your schema baseline. If any of these fields change — types, names, nesting, additions, removals — Rumbliq will flag it.

Step 4: Configure an Alert (60 seconds)

A monitor without an alert is just a log. Let's set up an alert so you get notified when something changes.

From the monitor detail page, click Add Alert Destination.

You have three options: Slack webhook, Email, or Custom webhook.

For Slack:

Go to your Slack workspace → Apps → Incoming Webhooks → Add to Slack
Select the channel where alerts should go (#monitoring, #api-alerts, whatever works)
Copy the webhook URL (looks like https://hooks.slack.com/services/T.../B.../...)
Paste it into Rumbliq's Slack webhook field

For Email:

Enter the email address where alerts should go. You can add multiple addresses.

For custom webhooks:

Enter a URL. Rumbliq will POST alert payloads to that URL in JSON format when drift is detected.

You can add multiple alert destinations to a single monitor — for example, both a Slack channel and an email for on-call coverage.

After adding your alert destination, click Save.

Step 5: Verify It's Working (30 seconds)

Your monitor is now running. You can verify it's working from the dashboard — you should see:

Status: Healthy (green)
Last check: A timestamp from a few seconds ago
Next check: Scheduled based on your interval
Schema: The baseline schema you captured in Step 3

From the monitor detail page, you can see the full check history. Each row shows the timestamp, response time, HTTP status code, and drift status (no change / drift detected / check failed).

That's it. You're monitoring.

What Happens When Drift Is Detected

When Rumbliq detects a schema change, here's what you get:

A Slack message (if configured) that looks like this:

⚠️ Schema drift detected: Stripe Payment Methods
Endpoint: https://api.stripe.com/v1/payment_methods?type=card
Detected at: 2026-04-03 14:22:07 UTC

Changes:
  ✦ card.networks added (object)
  ✦ card.wallet changed: null → object
  - card.three_d_secure_usage removed

View full diff → https://rumbliq.com/monitors/mon_xxx

An email with the same information, plus a link to the full diff in the Rumbliq dashboard.

The dashboard shows the drift event in the check history, with a full side-by-side schema comparison:

Before                              After
──────────────────────────────────────────────────────────
card:                               card:
  brand: string                       brand: string
  checks: object                      checks: object
  country: string                     country: string
  exp_month: number                   exp_month: number
  exp_year: number                    exp_year: number
  fingerprint: string                 fingerprint: string
  funding: string                     funding: string
  last4: string                       last4: string
  three_d_secure_usage: object    ✦   networks: object (NEW)
                                  ✦   wallet: null | object (CHANGED)
                                  ✗   three_d_secure_usage: removed

From there, you decide: is this a breaking change that needs a code fix? An additive change that's safe? You update your code if needed, then click Reset Baseline to accept the new schema as the new normal.

Going Further: The Next 10 Minutes

With your first monitor running, here's what to add next:

Add your other critical endpoints. If you're monitoring Stripe, add payment_intents, customers, subscriptions, and webhooks — the endpoints your payment processing code actually reads.

Import from OpenAPI or Postman. If you have an OpenAPI spec or Postman collection for an API you want to monitor, Rumbliq can import it and create monitors for all endpoints automatically. Go to Import in the sidebar.

Set up the API for automation. If you want to add monitors programmatically (useful for microservices environments where new endpoints get added regularly):

curl -X POST https://api.rumbliq.com/v1/monitors \
  -H "Authorization: Bearer $RUMBLIQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Stripe Customers",
    "url": "https://api.stripe.com/v1/customers/cus_test_xxx",
    "method": "GET",
    "headers": {
      "Authorization": "Bearer sk_test_..."
    },
    "interval": 60,
    "alerts": [
      {
        "type": "slack",
        "webhookUrl": "https://hooks.slack.com/services/..."
      }
    ]
  }'

Add teammates. On the Pro plan and above, you can invite teammates and share monitors across your team. Alerts can be routed to team-specific channels so the right engineer gets the right alert.

The 3-Minute Version (TL;DR)

Sign up — 30 seconds
Click New Monitor, paste your URL, add auth headers if needed — 60 seconds
Rumbliq captures the baseline automatically — 30 seconds
Click Add Alert Destination, add your Slack webhook or email — 60 seconds

Done. You now have schema drift monitoring on your API endpoint. If the response structure ever changes, you'll know within 3 minutes.

The free plan includes 25 monitors — more than enough to cover your critical third-party integrations immediately.

Start monitoring free → — no credit card required.