Aurora GraphQL Deprecation

Aurora GraphQL Deprecation — Removal Effective October 1, 2026

Enerflo will be removing several previously deprecated Aurora GraphQL fields, resolvers, and mutations from the API on October 1, 2026. If your integration uses any of the items below, you must migrate to a supported replacement before that date to avoid disruption.

Mutations Being Removed

Mutation
`createAuroraDesign`
`syncAuroraDesign`
`importAuroraProject`
`approveAuroraRequest`
`requestAuroraDesignChanges`

Queries Being Removed

Query
`getAuroraDesign`
`fetchAuroraProjectForDeal`
`fetchDealForAuroraProjectAndDesign`
`fetchAuroraUserIdForSalesRepOnDeal`
`isAuroraUserValidationRequired`
`sendAuroraUserInvite`
`fetchAuroraDealTemplateSettings`

Field Resolvers Being Removed

Field Resolver
`auroraProject`
`auroraDesign`
`auroraDesignRequest`
`auroraAutoDesigner`
`url`
`designRequestUrl`
`auroraData`

Recommended Actions

Review your integration for usage of any fields/mutations/resolvers listed above.
Migrate to supported replacements prior to October 1, 2026.
Deprecation reasons are visible via standard GraphQL introspection, or by checking the deprecationReason field in your schema explorer.

Note: Integrations managed directly by Enerflo will be updated automatically — no action needed on those.

Questions?

Reach out via Enerflo Support (Chat) or your Partner Success Manager (PSM).