Built-in Namespacing for injectEndpoints to Prevent Endpoint Name Collisions

[User6531]

Hi,

We’re using a single createApi instance + injectEndpoints across ~20 domains, each contributing ~10 endpoints (≈200 total). This architecture works well, but we’re hitting a structural limitation around endpoint name collisions.

The problem

All injected endpoints live in a flat namespace on the API instance. This makes collisions easy and silent:

// users/api.ts
baseApi.injectEndpoints({
  endpoints: (builder) => ({
    getById: builder.query(...)
  })
})

// orders/api.ts
baseApi.injectEndpoints({
  endpoints: (builder) => ({
    getById: builder.query(...) // silently overwrites users.getById
  })
})

This causes:

• accidental overrides with no warning
• runtime bugs that are hard to trace
• reliance on naming discipline (e.g. usersGetById) that doesn’t scale well

With large teams and many domains, this becomes a correctness issue rather than just DX.

Feature idea / question

Is there (or could there be) a built-in way to namespace injected endpoints, for example:

baseApi.injectEndpoints({
  namespace: 'users',
  endpoints: (builder) => ({
    getById: builder.query(...)
  })
})

or

baseApi.injectEndpoints({
  endpoints: {
    users: (builder) => ({
      getById: builder.query(...)
    })
  }
})

With behavior like:

• automatic namespacing in api.endpoints
• hook names derived from namespace + endpointName
• optional dev-time collision detection

---

Thanks for the great work on RTK Query - it’s been solid at scale so far.

[EskiMojo14]

#4975