YouTube Data

The YouTube Data API lets you retrieve and manage YouTube resources such as videos, channels, playlists, comments, and subscriptions. Nexla connects to the YouTube Data API v3 using OAuth 2.0, so you can ingest video, channel, comment, and search data into your flows or write playlists, comments, subscriptions, and video updates back to YouTube on behalf of an authorized account.

Power end-to-end data operations for your YouTube Data API with Nexla. Our bi-directional YouTube Data connector is purpose-built for YouTube Data, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to YouTube Data or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your YouTube Data workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The YouTube Data API uses OAuth 2.0 for authentication. To connect Nexla, you need an OAuth 2.0 client (a Client ID and Client Secret) created in a Google Cloud project that has the YouTube Data API v3 enabled. Requests act on behalf of the Google account that authorizes the connection, and the access granted is scoped to the permissions you request.

To obtain your OAuth 2.0 credentials, follow these steps:

Sign in to the Google Cloud Console and select an existing project or create a new one.
Open the API Library, search for YouTube Data API v3, and click Enable to activate the API for your project.
Configure the OAuth consent screen for your project, providing the required application details and adding any test users if the app is not yet published.
Go to the Credentials (Clients) page, click Create credentials > OAuth client ID, and select the Web application application type.
Add the authorized redirect URI required for the OAuth flow, then click Create.
Copy the Client ID and Client Secret shown after the client is created. The client secret is displayed only at creation time and cannot be retrieved again later, so store it securely.
Determine the OAuth scopes your integration needs (for example, read-only access versus scopes that permit managing playlists, comments, and subscriptions), and make sure they are approved for your consent screen.

For full details on authorization, scopes, and available resources, see the YouTube Data API documentation and Obtaining authorization credentials.

Authenticate

Credentials required

Field	Required	Secret	Description
Authorization URL	No	No	The URL endpoint where users authenticate and authorize access
Client ID	Yes	Yes	A unique public identifier assigned to your application
Access Scope	No	No	A space-separated list of permissions your application requests
Token URL	No	No	The URL endpoint where authorization codes are exchanged for access tokens
Client Secret	No	Yes	A private key used to authenticate your application when requesting tokens

Create a credential in Nexla

After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter the Client ID and Client Secret from the OAuth 2.0 client you created in Prerequisites. The Authorization URL, Token URL, and Access Scope fields are pre-populated with the standard values for the YouTube Data API; adjust the Access Scope only if your use case requires different permissions.
Complete the OAuth 2.0 authorization flow when prompted, signing in with the Google account whose YouTube data you want to access and granting the requested permissions.

The connection acts on behalf of the account that authorizes it, and access is limited to the scopes you request. If your Client Secret is compromised, revoke the client in the Google Cloud Console and create a new OAuth 2.0 client.
For detailed information about OAuth 2.0 authorization, scopes, and available endpoints, see the YouTube Data API documentation and Implementing OAuth 2.0 Authorization.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the YouTube Data connector tile, then select the credential that will be used to connect to the YouTube Data API, and click Next; or, create a new YouTube Data credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common YouTube Data API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Videos

Retrieve a list of videos matching the given criteria.