Pick what you watch

Out of the box, Intello watches the entire integration. That's almost always the right answer. This page exists for the cases where it isn't.

The default: watch everything

When you add an integration, every endpoint, schema, and auth flow in the spec is monitored. New things show up Safe, removed things show up Breaking, and you decide what to do with each.

Resist the urge to scope down preemptively. The cost of monitoring extra endpoints is roughly zero; the cost of not monitoring an endpoint that bites you later is one incident.

When to scope down

Three legitimate reasons to narrow what's watched:

1. You only consume a tiny part of a giant API. AWS exposes thousands of operations; you use ten. Watching all of AWS would drown your inbox in irrelevant additions.
2. The vendor publishes one spec for many products and you only ship the ones in product A.
3. The spec contains internal-only operations the vendor publishes but you've contractually agreed not to use.

If you're not sure your case fits one of those, leave it on the default.

How to scope

On the integration detail page, open Watch settings. You can include or exclude:

• By path prefix — e.g. only /v2/charges/* and /v2/refunds/*.
• By tag — most OpenAPI specs group operations under tags (Billing, Webhooks, etc.). Pick the tags you care about.
• By operation — surgical, useful when you depend on three specific endpoints out of hundreds.

Excluded operations still get fetched as part of the snapshot — Intello just doesn't generate change events for them. If you flip them back on later, you don't lose history.

Versioned APIs deserve a note

If the vendor uses URL versioning (/v1, /v2025-01-15), follow the version your code uses, not the latest one. Pin Watch settings → Version filter to a path prefix.

Stripe, GitHub, and Anthropic all do versioning differently. The library spec for each is preconfigured with the right pattern; for BYO specs, you set it.

Authenticated specs

Most public APIs publish their OpenAPI document at a public URL. Some don't — they require an API key or OAuth token to fetch the spec itself.

Intello supports:

• Bearer tokens — paste the token; we store it encrypted and rotate on demand.
• HTTP Basic — username + password.
• Custom header — for API-key-style auth.

Add credentials at Integration → Spec source → Authentication. The token is only used to fetch the spec. Intello never makes calls to the actual API.