---
title: "POST /v1/{+parent}/metadataFeeds"
method: POST
path: "/v1/{+parent}/metadataFeeds"
tags: ["projects"]
---

# POST /v1/{+parent}/metadataFeeds

`POST /v1/{+parent}/metadataFeeds`

Creates a MetadataFeed.

## Path parameters

- `parent` string, required

## Query parameters

- `metadataFeedId` string
- `validateOnly` boolean

## Request body

- GoogleCloudDataplexV1MetadataFeed — MetadataFeed contains information related to the metadata feed.
  - `createTime` string, google-datetime — Output only. The time when the feed was created.
  - `updateTime` string, google-datetime — Output only. The time when the feed was updated.
  - `pubsubTopic` string — Optional. The pubsub topic that you want the metadata feed messages to publish to. Please grant Dataplex service account the permission to publish messages to the topic. The service account is: service-{PROJECT_NUMBER}@gcp-sa-dataplex.iam.gserviceaccount.com.
  - `scope` GoogleCloudDataplexV1MetadataFeedScope — Scope defines the scope of the metadata feed. Scopes are exclusive. Only one of the scopes can be specified.
    - `projects` string[] — Optional. The projects whose entries you want to listen to. Must be in the same organization as the feed. Must be in the format: projects/{project_id_or_number}.
    - `entryGroups` string[] — Optional. The entry groups whose entries you want to listen to. Must be in the format: projects/{project_id_or_number}/locations/{location_id}/entryGroups/{entry_group_id}.
    - `organizationLevel` boolean — Optional. Whether the metadata feed is at the organization-level. If true, all changes happened to the entries in the same organization as the feed are published. If false, you must specify a list of projects or a list of entry groups whose entries you want to listen to.The default is false.
  - `name` string — Identifier. The resource name of the metadata feed, in the format projects/{project_id_or_number}/locations/{location_id}/metadataFeeds/{metadata_feed_id}.
  - `filters` GoogleCloudDataplexV1MetadataFeedFilters — Filters defines the type of changes that you want to listen to. You can have multiple entry type filters and multiple aspect type filters. All of the entry type filters are OR'ed together. All of the aspect type filters are OR'ed together. All of the entry type filters and aspect type filters are AND'ed together.
    - `entryTypes` string[] — Optional. The entry types that you want to listen to, specified as relative resource names in the format projects/{project_id_or_number}/locations/{location}/entryTypes/{entry_type_id}. Only entries that belong to the specified entry types are published.
    - `changeTypes` string[] — Optional. The type of change that you want to listen to. If not specified, all changes are published.
    - `aspectTypes` string[] — Optional. The aspect types that you want to listen to. Depending on how the aspect is attached to the entry, in the format: projects/{project_id_or_number}/locations/{location}/aspectTypes/{aspect_type_id}.
  - `uid` string — Output only. A system-generated, globally unique ID for the metadata job. If the metadata job is deleted and then re-created with the same name, this ID is different.
  - `labels` object — Optional. User-defined labels.

## Response `200`

Successful response

---

[API](https://skmtc.net/google/apis/dataplex.md) · [All operations](https://skmtc.net/google/apis/dataplex/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/google/dataplex/versions/43a3b60ca93b/schema)