Quest GraphQL API Deprecation Notice

We are deprecating several Quest-related GraphQL types, fields, and input filters as part of our migration to an improved Quest reporting system (reportV2 and findQuests). These changes streamline Quest data retrieval and provide better support for multiple Quest selections.

• Deprecated Items
• Migration Guide
• Key Differences
• Backward Compatability
• Action Required

Deprecated Items

• Status: Deprecated
• Replacement: Use findQuests and/or reportV2 instead
• Reason: Being replaced with a more efficient implementation that supports querying multiple Quests simultaneously
   

• Status: Deprecated
• Replacement: Use reportV2 instead
• Reason: The new reportV2 provides enhanced filtering capabilities and better data aggregation

• Replacement: Use questSourceIds: [String!]! (plural) in QuestFilterInputV2
• Note: The new field accepts multiple Quest IDs, enabling multi-Quest reporting
   

• Replacement: None - reportV2 always returns data for the latest Quest revision
• Note: Revision tracking is now handled automatically
   

• Replacement: Use the filtering options in reportV2
• Note: Filtering by tags is still supported but through the new input structure
   

• Replacement: Use the filtering options in reportV2
• Note: Filtering by teams is still supported but through the new input structure

• details: QuestDetails! → Use reportV2.quests
• objectiveCompletion(...) → Use reportV2.objectiveCompletion
• objectiveAccuracy(...) → Use reportV2.objectiveAccuracy
• securityConceptObjectiveCompletion(...) → Use reportV2.securityConceptObjectiveCompletion
• learners: QuestLearners → Use reportV2.learners

Migration Guide

Before (Deprecated - Single Quest)
 

query {
  quests {
    report(filter: {
      questSourceId: "quest-123"
      questRevisionNumber: 5
      tags: ["engineering"]
      teamIds: ["team-1", "team-2"]
    }) {
      details {
        name
        status
      }
      objectiveCompletion(first: 10) {
        edges {
          node {
            category
            completionRate
          }
        }
      }
      learners {
        objectiveAssignedLearners(first: 20) {
          edges {
            node {
              name
              email
            }
          }
        }
      }
    }
  }
}

query {
  quests {
    reportV2(filter: {
      questSourceIds: ["quest-123", "quest-456"]
      tags: ["engineering"]
      teamIds: ["team-1", "team-2"]
    }) {
      quests {
        edges {
          node {
            name
            status
          }
        }
      }
      objectiveCompletion(first: 10) {
        edges {
          node {
            category
            allLearnersCompletedRate
          }
        }
      }
      learners {
        objectiveAssignedLearners(first: 20) {
          edges {
            node {
              name
              email
            }
          }
        }
      }
    }
  }
}

Key Differences
 

1. Multiple Quests: reportV2 accepts multiple Quest IDs via questSourceIds (plural)
2. Automatic Latest Revision: No need to specify questRevisionNumber - the latest revision is always used
3. Enhanced Fields: Some completion fields have been renamed (e.g., completionRate → allLearnersCompletedRate)
4. Filtering: Tag and team filtering is handled through the new filter structure in reportV2

Backward Compatibility

The deprecated fields and types will continue to function until November 1, 2025. However, we strongly recommend migrating to reportV2 and findQuests as soon as possible to:
 

• Take advantage of multi-Quest reporting
• Ensure uninterrupted service after the deprecation date
• Benefit from improved performance and data accuracy

Action Required

• findQuests for retrieving Quest details
• reportV2 with QuestFilterInputV2 for Quest reporting data