Each intent parameter has a type, called the entity type, which dictates exactly how data from an end-user expression is extracted.
Dialogflow provides predefined system entities that can match many common types of data. For example, there are system entities for matching dates, times, colors, email addresses, and so on. You can also create your own custom entities for matching custom data. For example, you could define a vegetable entity that can match the types of vegetables available for purchase with a grocery store agent.
The unique identifier of the entity type. Required forEntityTypes.UpdateEntityTypeandEntityTypes.BatchUpdateEntityTypesmethods. Supported formats: -projects/<Project ID>/agent/entityTypes/<Entity Type ID>-projects/<Project ID>/locations/<Location ID>/agent/entityTypes/<Entity
Type ID>
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-27 UTC."],[[["\u003cp\u003eEntityType dictates how data is extracted from end-user expressions in Dialogflow, using either predefined system entities or custom entities.\u003c/p\u003e\n"],["\u003cp\u003eThe JSON representation of an EntityType includes fields like \u003ccode\u003ename\u003c/code\u003e, \u003ccode\u003edisplayName\u003c/code\u003e, \u003ccode\u003ekind\u003c/code\u003e, \u003ccode\u003eautoExpansionMode\u003c/code\u003e, \u003ccode\u003eentities\u003c/code\u003e, and \u003ccode\u003eenableFuzzyExtraction\u003c/code\u003e, defining its structure and behavior.\u003c/p\u003e\n"],["\u003cp\u003eEntityType management involves several methods, including creating, deleting, retrieving, and updating entity types, as well as batch operations for multiple entities.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003ekind\u003c/code\u003e and \u003ccode\u003edisplayName\u003c/code\u003e are required fields for every EntityType and defines the type of entity and its name respectively.\u003c/p\u003e\n"],["\u003cp\u003eEntityType can have the option \u003ccode\u003eenableFuzzyExtraction\u003c/code\u003e enabled, which will allow fuzzy extraction when the classification process occurs.\u003c/p\u003e\n"]]],[],null,["# REST Resource: projects.locations.agent.entityTypes\n\n- [Resource: EntityType](#EntityType)\n - [JSON representation](#EntityType.SCHEMA_REPRESENTATION)\n- [Methods](#METHODS_SUMMARY)\n\nResource: EntityType\n--------------------\n\nEach intent parameter has a type, called the entity type, which dictates exactly how data from an end-user expression is extracted.\n\nDialogflow provides predefined system entities that can match many common types of data. For example, there are system entities for matching dates, times, colors, email addresses, and so on. You can also create your own custom entities for matching custom data. For example, you could define a vegetable entity that can match the types of vegetables available for purchase with a grocery store agent.\n\nFor more information, see the [Entity guide](https://cloud.google.com/dialogflow/docs/entities-overview)."]]
