Phyllo

Connect to the Phyllo API to access consented creator-economy data (accounts, profiles, content, and work-platform info) across social and creator platforms such as YouTube, Instagram, TikTok, and Twitch.

Power end-to-end data operations for your Phyllo API with Nexla. Our bi-directional Phyllo connector is purpose-built for Phyllo, 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 Phyllo or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Phyllo 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

Phyllo is a unified API for the creator economy. It lets you access consented data (accounts, profiles, published content, and engagement metrics) that creators have connected from work platforms such as YouTube, Instagram, TikTok, and Twitch. The Phyllo API uses HTTP Basic authentication: every request must include your client_id and client_secret, which Nexla sends in the Authorization header.

To obtain your Phyllo API credentials, follow these steps:

1. Sign up for and sign in to the Phyllo Developer Dashboard.

2. Navigate to the API Credentials page in the dashboard.

3. Locate your Client ID (client_id) and Client Secret (client_secret). These are displayed on the dashboard and can be viewed or rotated from this page.

4. Copy both values and store them securely. The Client Secret is sensitive and should be kept confidential. Phyllo recommends that API calls be made only from your server, never from a frontend or mobile app.

Phyllo provides separate environments (for example, sandbox and production), each with its own set of credentials. Make sure you use the credentials for the environment you intend to connect to. For detailed information about authentication and available resources, refer to the Phyllo API Documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	No	Your Phyllo API client_id.
Client Secret	Yes	Yes	Your Phyllo API client_secret.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Phyllo API client_id in the Client ID field. This value is found on the API Credentials page of your Phyllo Developer Dashboard.

4. Enter your Phyllo API client_secret in the Client Secret field. This value is also found on the API Credentials page of your Phyllo Developer Dashboard and must be kept confidential.

   The Phyllo API uses HTTP Basic authentication. Nexla sends your Client ID and Client Secret in the Authorization header on every request. If your Client Secret is compromised, rotate it from the API Credentials page of your Phyllo Developer Dashboard and update the credential in Nexla.

   For detailed information about authentication, environments, and available resources, see the Phyllo API Documentation.

5. 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 Phyllo connector tile, then select the credential that will be used to connect to Phyllo, and click Next; or, create a new Phyllo 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 Phyllo 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] Retrieve list of Phyllo users

Retrieve list of Phyllo users.

A User represents an end creator in your Phyllo account. This endpoint returns the list of users you have created. For detailed information about response structures and available fields, see the Phyllo API Documentation.

[Rest API] Retrieve all connected accounts

Retrieve all connected accounts. An Account represents a user's connection to a work platform (e.g. YouTube, Instagram, TikTok).

An Account represents a user's connection to a specific work platform. This endpoint returns all connected accounts accessible to your credential. For detailed information about response structures and available fields, see the Phyllo API Documentation.

[Rest API] Retrieve all Profiles

Retrieve all Profiles. A Profile contains identity information for the creator (name, email, follower count, etc.).

A Profile contains identity information for a creator, such as name, email, and follower count. This endpoint returns all Profiles accessible to your credential. For detailed information about response structures and available fields, see the Phyllo API Documentation.

[Rest API] Retrieve a single Profile by id

Retrieve a single Profile by id.

This endpoint returns the identity information for a single Profile, identified by its id. For detailed information about response structures and available fields, see the Phyllo API Documentation.

[Rest API] Retrieve all supported work platforms

Retrieve all supported work platforms (YouTube, Instagram, TikTok, Twitch, Shopify, Upwork, etc.).

A Work Platform is a source that Phyllo integrates with, such as YouTube, Instagram, TikTok, Twitch, Shopify, or Upwork. This endpoint returns the full list of supported work platforms. For detailed information about response structures and available fields, see the Phyllo API Documentation.

[Rest API] Retrieve all content items (posts)

Retrieve all content items (posts) published by a creator, with engagement metrics (likes, shares, impressions).

This endpoint returns the content items (posts) published by a creator, including engagement metrics such as likes, shares, and impressions. For detailed information about response structures and available fields, see the Phyllo API Documentation.

[Rest API] Retrieve a single content item by id

Retrieve a single content item by id.

This endpoint returns a single content item, identified by its id, including its engagement metrics. For detailed information about response structures and available fields, see the Phyllo API Documentation.

[Rest API] Retrieve content items in bulk

Retrieve content items in bulk by providing a list of content ids.

This endpoint returns multiple content items in a single request when you provide a list of content ids. For detailed information about request parameters and response structures, see the Phyllo API Documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Phyllo data sources can also be manually configured to ingest data from any valid Phyllo API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Phyllo data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Phyllo destination, and select the Send to Destination option from the menu. Select the Phyllo connector from the list of available destination connectors, then select the credential that will be used to connect to Phyllo, and click Next; or, create a new Phyllo credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Phyllo endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Generate an SDK token

Generate an SDK token for the Connect account-linking flow.

This endpoint creates an SDK token that is used to initialize the Phyllo Connect account-linking flow. Each record from your Nexset will be sent as a separate API request. For detailed information about the request body and response, see the Phyllo API Documentation.

[Rest API] Disconnect a connected account

Disconnect a connected account.

This endpoint disconnects a previously connected account. Each record from your Nexset will be sent as a separate API request. For detailed information about the request body and response, see the Phyllo API Documentation.

[Rest API] Trigger a Profile refresh

Trigger a refresh of a Profile's data from the source platform.

This endpoint triggers a refresh of a Profile's data from its source work platform. Each record from your Nexset will be sent as a separate API request. For detailed information about the request body and response, see the Phyllo API Documentation.

[Rest API] Create a Phyllo user

Create a Phyllo user.

This endpoint creates a new User in your Phyllo account. Each record from your Nexset will be sent as a separate API request to create a user. For detailed information about the request body and response, see the Phyllo API Documentation.

Manual configuration

Phyllo destinations can also be manually configured to send data to any valid Phyllo API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Phyllo APIs typically expect JSON format for write operations. For operations that act on a specific object, include the object's id at the end of the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Phyllo endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Phyllo endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.