Getting started

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

Create a connector & set permissions

Navigate to the Connectors page to define your destination storage.

Google Cloud Storage

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

1. First, identify your exact bucket name within the Cloud Storage browser in your Google Cloud Console.
2. Next, navigate to IAM & Admin to create a dedicated Service Account for Soundcharts.
3. Assign this account the "Storage Object Creator" role to strictly enforce least privilege.
4. Once created, go to the "Keys" tab of this service account, click "Add Key," select the JSON format, and download the file.
5. 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.

1. Create a dedicated S3 bucket, for example soundcharts-data.
2. Locate your exact bucket name and AWS region identifier in your S3 console.
3. Next, navigate to the IAM dashboard and create a new user specifically for this integration. Do not use root credentials.
4. Attach an inline policy granting exclusively the s3:PutObject action for your target resource: arn:aws:s3:::your-bucket-name/*.
5. Upon creation, generate an Access Key.
6. 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.

Always use the "Test connection" button to ensure our system can successfully authenticate and write to your destination before saving.

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 dashboard.

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

To guarantee pipeline robustness, any enriched data will solely be added within existing JSON payload columns, ensuring your integrations never break. Exact structure and headers for each TSV file are detailed on their respective data feed documentation pages.

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.