Data Catalog API methods that are related to Data Catalog search and metadata are deprecated and will be discontinued on January 30, 2026. See Transition from Data Catalog to Dataplex Universal Catalog. Methods that are related to policy tags and policy tag taxonomies are not deprecated.
An entry group contains logically related entries together with Cloud Identity and Access Management policies. These policies specify users who can create, edit, and view entries within entry groups.
Data Catalog automatically creates entry groups with names that start with the @ symbol for the following resources:
You can create your own entry groups for Cloud Storage fileset entries and custom entries together with the corresponding IAM policies. User-created entry groups can't contain the @ symbol, it is reserved for automatically created groups.
Entry groups, like entries, can be searched.
A maximum of 10,000 entry groups may be created per organization across all locations.
You must enable the Data Catalog API in the project identified by the parent parameter. For more information, see Data Catalog resource project.
HTTP request
POST https://datacatalog.googleapis.com/v1/{parent}/entryGroups
Path parameters
Parameters
parent
string
Required. The names of the project and location that the new entry group belongs to.
Note: The entry group itself and its child resources might not be stored in the location specified in its name. It takes the form projects/{project}/locations/{location}.
Query parameters
Parameters
entryGroupId
string
Required. The ID of the entry group to create.
The ID must contain only letters (a-z, A-Z), numbers (0-9), underscores (_), and must start with a letter or underscore. The maximum size is 64 bytes when encoded in UTF-8.
Request body
The request body contains an instance of EntryGroup.
Response body
If successful, the response body contains a newly created instance of EntryGroup.
[[["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-07-17 UTC."],[[["\u003cp\u003eEntry groups logically organize related entries and their associated Cloud Identity and Access Management policies, which dictate user permissions for creation, editing, and viewing within those groups.\u003c/p\u003e\n"],["\u003cp\u003eData Catalog automatically generates entry groups for BigQuery, Pub/Sub, and Dataproc Metastore resources, with names prefixed by the \u003ccode\u003e@\u003c/code\u003e symbol, which are not available for user created groups.\u003c/p\u003e\n"],["\u003cp\u003eThe creation of an entry group involves making a POST request to the specified URL, providing necessary details like the parent project and location, as well as an entry group ID that must follow specific character constraints.\u003c/p\u003e\n"],["\u003cp\u003eEach organization can create up to 10,000 entry groups across all locations, and it is necessary to have the Data Catalog API enabled within the parent project.\u003c/p\u003e\n"],["\u003cp\u003eThe request body uses \u003ccode\u003eEntryGroup\u003c/code\u003e and if successful, the response body will contain a newly created instance of \u003ccode\u003eEntryGroup\u003c/code\u003e as well.\u003c/p\u003e\n"]]],[],null,["# Method: projects.locations.entryGroups.create\n\n- [HTTP request](#body.HTTP_TEMPLATE)\n- [Path parameters](#body.PATH_PARAMETERS)\n- [Query parameters](#body.QUERY_PARAMETERS)\n- [Request body](#body.request_body)\n- [Response body](#body.response_body)\n- [Authorization scopes](#body.aspect)\n- [Try it!](#try-it)\n\n| Data Catalog is deprecated. Please use Dataplex Universal Catalog instead.\nCreates an entry group.\n\nAn entry group contains logically related entries together with [Cloud Identity and Access Management](/data-catalog/docs/concepts/iam) policies. These policies specify users who can create, edit, and view entries within entry groups.\n\nData Catalog automatically creates entry groups with names that start with the `@` symbol for the following resources:\n\n- BigQuery entries (`@bigquery`)\n- Pub/Sub topics (`@pubsub`)\n- Dataproc Metastore services (`@dataproc_metastore_{SERVICE_NAME_HASH}`)\n\nYou can create your own entry groups for Cloud Storage fileset entries and custom entries together with the corresponding IAM policies. User-created entry groups can't contain the `@` symbol, it is reserved for automatically created groups.\n\nEntry groups, like entries, can be searched.\n\nA maximum of 10,000 entry groups may be created per organization across all locations.\n\nYou must enable the Data Catalog API in the project identified by the `parent` parameter. For more information, see [Data Catalog resource project](https://cloud.google.com/data-catalog/docs/concepts/resource-project).\n\n### HTTP request\n\n`POST https://datacatalog.googleapis.com/v1/{parent}/entryGroups`\n\n### Path parameters\n\n### Query parameters\n\n### Request body\n\nThe request body contains an instance of [EntryGroup](/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups#EntryGroup).\n\n### Response body\n\nIf successful, the response body contains a newly created instance of [EntryGroup](/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups#EntryGroup).\n\n### Authorization scopes\n\nRequires the following OAuth scope:\n\n- `https://www.googleapis.com/auth/cloud-platform`\n\nFor more information, see the [Authentication Overview](/docs/authentication#authorization-gcp)."]]