Introducing Enterprise Search FAQ metadata in the Data API Plugin Resources endpoint (Live on 10 November 2026)
What's changing?
Effective November 10, the Plugin Resources endpoint (/export/v1/records/plugin-resources) in the Moveworks Data API returns metadata for FAQs surfaced by Enterprise Search.
Records of type RESOURCE_TYPE_INTERNAL_KNOWLEDGE used to return no details, so you couldn't tell which FAQ the AI Assistant showed. These records now carry a populated detail object for Enterprise Search FAQs:
name: the FAQ titledomain: the FAQ's resource domain, for example IT, HR or FINANCE. It uses the same values as knowledge, form, ticket and approval resources, so you can group FAQ usage alongside them.snippet: the FAQ text that the AI Assistant used in its response
With this, you can see which FAQs employees are shown and track FAQ adoption and effectiveness across your business lines. See an example FAQ record.
What is the impact?
This is a non-breaking, additive change. No records are added or removed, and every other resource type is unchanged. To keep your Data API integration resilient to changes like this, please make sure it follows the Data API integration best practices help doc.
Note: There's no backfill. FAQ metadata is only populated for records created from November 10 onward.
Current limitations
- No
urlkey. An FAQ's source URL points to the document that holds the FAQs, not to the individual FAQ. Useresource_idto count or group individual FAQs, since FAQ titles can repeat. - Enterprise Search FAQs only. FAQs surfaced by the Self Knowledge plugin (questions about the AI Assistant's own capabilities) still return
detail: null. These are a very small share of FAQ records.
See Data API known gaps for details.
Other resources
- Data API release notes (FAQ metadata in Plugin Resources)
- Data API data dictionary: Plugin resources
- Data API: List plugin resources endpoint
- Data API: Breaking vs. non-breaking changes
If you have any questions or concerns, feel free to comment on this post and our team will get back to you.
Thanks,
Moveworks Analytics team