# Can an interface implement another interface?

**URL:** <https://community.apollographql.com/t/can-an-interface-implement-another-interface/8798>\
**Category:** Schema Design\
**Tags:** schema-design\
**Created:** [March 26, 2025, 9:26am UTC](https://community.apollographql.com/t/can-an-interface-implement-another-interface/8798 "2025-03-26T09:26:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jleangstartup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/jleangstartup/32/5927_2.png) [@jleangstartup](https://community.apollographql.com/u/jleangstartup)\
**Post date:** [March 26, 2025, 9:26am UTC](https://community.apollographql.com/t/can-an-interface-implement-another-interface/8798/1 "2025-03-26T09:26:01Z")

</div>

I’ve had a look around and cant find much information on this.

Can an interface implement another interface?

My example data model is that there are ‘payees’, and these payees can considered ‘billers’ or ‘transfers’, and within transfers, there are ‘payid’ and ‘account’.

So was thinking I’d have  
interface payee  
interface transfer implements payee  
type payid implements transfer  
type account implements transfer

Something like that, and then in the queries from client, have fragments (inline or named)

Is it recommended? or when would/wouldnt it be recommended?

Currently designing schema for Apollo Server, potentially with a view to move onto Federation later on. Would queries with nested inline fragments still work with federation?

---

<div class="post-metadata">

**Author:** ![dkuc](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/dkuc/32/2892_2.png) [@dkuc](https://community.apollographql.com/u/dkuc)\
**Post date:** [March 26, 2025, 6:54pm UTC](https://community.apollographql.com/t/can-an-interface-implement-another-interface/8798/2 "2025-03-26T18:54:16Z")

</div>

Yes latest GraphQL spec supports interface implementing other interfaces. See [GraphQL spec](https://spec.graphql.org/draft/#sec-Interfaces)

> Would queries with nested inline fragments still work with federation?

At the end of the day federated Supergraph API schema is still a valid GraphQL schema, so yes you can write queries with fragments.
