Domain mapping & impact

Domain mappings are how Intello answers the question, "which area of this API does this change affect?" They turn a raw change like "a field was removed from GET /customers/:id" into the more useful framing "a field was removed from the billing area of Stripe's API."

What a domain mapping is

A domain mapping is a record that associates a slice of an external API — defined by tags, path prefixes, or specific operations — with a named domain such as billing, catalog, or webhooks. When a change event is generated, the pipeline checks whether the affected operation matches any mapping for that dependency and tags the event with the matching domain.

Examples of typical domain assignments:

Once tagged, the domain appears on the change card, in Slack alerts (in the Domain field), and in the Incidents view, where it can be used as a filter.

How mappings are created

Domain mappings are generated automatically when an integration is added. The classifier inspects the OpenAPI specification and produces mappings based on:

• Tags declared on each operation in the specification.
• Path prefixes that group related endpoints.
• Operation IDs for individual endpoints.

Why mappings matter

Without domain tagging, every change presents the same information regardless of which area of the API it touches. With domain tagging, each alert names the affected domain — and your team can filter, route, and triage based on the part of the integration that is implicated.

For multi-team organizations, domain tagging is also the basis for team-specific routing. By creating per-dependency alert preferences with channel filters, you can ensure that, for example, payments-related changes route to the payments team's Slack channel.