Getting started

Soundcharts Data Feed keeps your data warehouse continuously up to date with Soundcharts data — automatically, on the schedule you choose, without manual exports or custom scraping.

Technically, Data Feed synchronizes the music industry database directly into your storage via asynchronous push. Only the deltas (new data recorded since the last execution) are delivered at your defined frequency, keeping pipelines lightweight. All data feeds are delivered in TSV format.

Soundcharts Data Feed is available starting from the Developer plan.

If your infrastructure enforces strict security policies, private networks, or firewalls requiring specific configuration, you must notify us via this form.

Need large-scale bulk delivery? We can provide full data dump & data feed directly to your storage (S3, GCS, ClickHouse, Databricks, etc.) on demand.

Create a connector & set permissions

Navigate to the Connectors page to define your destination storage.

Every connector type — Google Cloud Storage, Amazon S3, Google Sheets, and Webhook — includes a Test connection button. Always use it before saving to confirm Soundcharts can authenticate and write to your destination.

Google Cloud Storage

To configure this connector, you must provide your Bucket Name, and a Credentials JSON file.

First, identify your exact bucket name within the Cloud Storage browser in your Google Cloud Console.
Next, navigate to IAM & Admin to create a dedicated Service Account for Soundcharts.
Assign this account the "Storage Object Creator" role to strictly enforce least privilege.
Once created, go to the "Keys" tab of this service account, click "Add Key," select the JSON format, and download the file.
You can upload this JSON file directly into our connector interface.

Amazon S3 Storage

To configure this connector, you must provide your Bucket Name, Region, Access Key, and Secret Key.

Create a dedicated S3 bucket, for example soundcharts-data.
Locate your exact bucket name and AWS region identifier in your S3 console.
Next, navigate to the IAM dashboard and create a new user specifically for this integration. Do not use root credentials.
Attach an inline policy granting exclusively the s3:PutObject action for your target resource: arn:aws:s3:::your-bucket-name/*.
Upon creation, generate an Access Key.
Save the Secret Access Key immediately, as AWS will only display it once, and provide both keys in the connector setup.

Note for enterprise security teams: if your infrastructure relies on cross-account bucket policies rather than IAM user keys, authorize the Soundcharts AWS Account ID 412381756219 to write to your bucket.

Google Sheets Storage

To configure this connector:

share your document with our dedicated email soundcharts-export@soundcharts-custom-export.iam.gserviceaccount.com,
grant the "Editor" permissions,
and provide the full spreadsheet URL in the connector setup.

Be aware that Google Sheets imposes a strict limit of 10 million cells per document. Given the massive volume of music industry data, high-frequency data feeds or broad entity monitoring may exceed this capacity, resulting in pipeline failures. We advise using Amazon S3 or Google Cloud Storage for production environments.

Webhook push

To configure this connector:

Provide a publicly accessible HTTPS webhook endpoint URL in the connector setup, ensure the endpoint accepts HTTP POST requests with multipart/form-data payloads, and ensure your infrastructure can receive files up to the expected export size.
When an export is generated, Soundcharts will send the file as a multipart/form-data request containing a single file field named file. The original filename and content type are preserved.

When you test this connector, Soundcharts performs a validation request to verify that the endpoint is reachable. Your endpoint must respond successfully to an HTTP HEAD request for the test to pass.

For production environments, we strongly recommend implementing appropriate monitoring, authentication, and retry handling on your webhook endpoint to ensure reliable delivery of export files.

Manage Data Feeds

Once your connector is authenticated, you can create data feeds manually in the portal or programmatically via our API.

Portal

To create a data feed, you must:

Go to the Features section.
Select the entity to monitor.
Assign it to a previously created connector.
Define the Push interval.

Once created, you can manage your data feeds from your console.

API

To programmatically create a data feed, you must:

use the Get available feeds endpoint to list all available data streams you can consume and identify the specific code for the data you need.
use the Subscribe to a feed endpoint to activate a data pipeline for a specific entity.
audit your active data pipelines via the Get active feeds endpoint and stop ingestion at any time via the Unsubscribe from feed endpoint.

Frequency

For each feed, the Push interval defines the update frequency and must be set in seconds, ranging from 3,600 seconds (1 hour) to 604,800 seconds (1 week).

Delivery Structure and Schemas

Each TSV file uses a fixed set of typed columns. For entities with rich or variable metadata, one column (typically named json) contains a JSON-encoded payload. To guarantee pipeline robustness, any future enrichment will be added as new keys within this existing JSON payload — never as new TSV columns — so the file structure and your integrations never break.

Exact column structure, types, and a sample TSV file are provided on each data feed's reference page (e.g. Artist metadata).

Data is segmented by type and stored using a standard timestamp nomenclature. The directory structure follows this format: [data_type]/[YYYYMMDDHHmmss]/part-001.tsv, for example playlist_audience/20260519000000/part-001.tsv.

Quotas

The number of active data feeds you can maintain is tied to your subscription. Refer to the pricing page to review the data feed limits associated with your current plan.

Delivery Failures and Monitoring

If a delivery to your destination fails (authentication error, unreachable endpoint, etc.), Soundcharts automatically retries the export. If configured, alert notifications are sent by email to warn you when a delivery issue occurs, so you can address it before it impacts your pipeline.