Subscribe to the integration library
The integration library is Intello’s catalog of provider APIs we monitor for you. You pick a provider, choose which spec slices matter, and get provider change events when Intello publishes updates—usually without pasting a spec URL yourself.
In the web app
Exact labels vary, but the flow is typically:
- Open Dependency library / Integrations library (or similar) from the main nav or Dependencies.
- Browse or search for a provider (e.g. a vendor you integrate with).
- Choose Subscribe / Add subscription.
- On the subscription detail screen, enable the spec surfaces you care about and mute any you don’t (muting stops noise without canceling the whole subscription).
- Open Changes (org-wide or per subscription, depending on your build) to triage provider change events.
- Optionally set alert preferences for that subscription so only certain severities or domains notify you—same idea as BYO dependencies; see Alert preferences.
If you don’t see a vendor, you may need a custom dependency with your own OpenAPI URL instead (Add a dependency).
When subscriptions fit best
- You want Intello-maintained canonical specs, not your own hosted URL.
- Many teams standardize on the same vendor—one subscription, shared visibility.
- You’re fine with updates following Intello’s catalog sync schedule rather than only when you click sync.
Provider changes and history
Provider changes appear in the app’s change feeds alongside your BYO dependencies (exact navigation depends on your version). You can acknowledge items after triage.
Plan note: some plans limit how far back you can see broadcast history; older items might not appear even though they existed. See Plans and usage.
Coverage vs custom dependencies
| Approach | Best when |
|---|---|
| Library subscription | Vendor is in the catalog and the default specs match what you ship against. |
| BYO dependency | You need a fork, private gateway URL, or non-catalog spec. |
Developers: HTTP API
Automation uses routes such as POST /api/provider-subscriptions, GET /api/provider-subscriptions/:id/specs, PUT .../specs/:specId with { "is_muted": true | false }, GET /api/provider-changes, and alert-preference CRUD under /api/provider-subscriptions/:id/alert-preferences. Full tables: Core resources.