Buzzsprout is a podcast hosting platform that creators use to upload, publish, and promote podcast episodes, and to distribute them to podcast directories such as Apple Podcasts and Spotify.
Hevo uses the Buzzsprout API to replicate the podcasts and episodes of your Buzzsprout account to the Destination of your choice. To ingest data, you must provide Hevo with the API token of your Buzzsprout account.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes |
| History mode | No |
| Custom data (user-configured tables & fields) | No |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | Yes |
Prerequisites
-
An active Buzzsprout account from which data is to be ingested.
-
The API token of your Buzzsprout account is available.
Obtain the API Token
Hevo connects to your Buzzsprout account using an API token. Each Buzzsprout user has one API token, and the API Key page lists the podcasts that the token can access.
Perform the following steps to obtain the API token:
-
Log in to your Buzzsprout account.
-
In the top navigation bar, click Settings, and then click My Profile.
-
In the left navigation pane, click API Key.
-
On the Your API Credentials page, copy the value displayed next to Your API Token, and save it securely like any other password.
Read Authentication for more information about the API token.
If you click Reset API Token, Buzzsprout replaces the API token, and Hevo can no longer connect to your account using the earlier token. To resume data ingestion, modify the Source configuration with the new token.
Configure Buzzsprout as a Source in your Pipeline
Perform the following steps to configure your Buzzsprout Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Buzzsprout.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
In the Configure Source screen, specify the following:
-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, Buzzsprout Source.
-
In the Connect to Buzzsprout section, specify the following:
- API Token: The API token that you obtained from Buzzsprout.
-
-
Click Test & Continue to test the connection to your Buzzsprout Source. Hevo checks the connection by reading the list of your podcasts. The test fails if Buzzsprout rejects the API token. Once the test is successful, you can proceed to set up your Destination.
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. To ingest the Episode object, you must also select the Podcast object.
Hevo ingests the entire data of all the selected objects in each run, as per the sync frequency.
You can resync the Podcast object. Resyncing it also resyncs the Episode object.
Buzzsprout allows 60 API requests per minute for each API token. Read Rate limits and retries.
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Podcast | Contains the podcasts that the API token can access, including the title, author, description, categories, language, artwork, and RSS feed URL of each podcast. It includes a child object, Episode. |
| Episode | Contains the episodes of each podcast, including the title, description, audio URL, duration, publish date, season and episode numbers, and total number of downloads of each episode. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Handling of Deletes
Hevo captures deletes by comparing the data ingested from the Source with the data present in the Destination in each run. If a podcast or an episode exists in the Destination but is no longer returned by the Source, Hevo marks it as deleted by setting the value of the metadata column __hevo__marked_deleted to True. The record remains in the Destination with all its data.
Source Considerations
-
Hevo ingests all the episodes of a podcast, including unpublished episodes. In the Episode object, the private field is True for unpublished episodes. For episodes scheduled to be published later, the published_at field contains a future date.
-
Hevo loads some fields with names that differ from the Buzzsprout API. For example, the keywords and tags fields are loaded as keyword and tag, the main_category2 field is loaded as main_category_2, and the total_downloads field is loaded as total_plays.
Limitations
- Hevo does not ingest the download statistics, chapters, transcripts, contributors, fan mail, or directory listings of your podcasts.