Skip to main content

Buzzsprout Data Source

The Buzzsprout connector enables you to ingest podcast and episode data from your Buzzsprout account into Nexla. Follow the instructions below to create a new data flow that ingests data from a Buzzsprout source in Nexla.
buzzsprout_api.png

Buzzsprout

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Buzzsprout connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Buzzsprout instance, and click Next; or, create a new Buzzsprout credential for use in this flow.

  3. In Nexla, Buzzsprout data sources can be created using pre-built endpoint templates, which expedite source setup for common Buzzsprout endpoints. Each template is designed specifically for the corresponding Buzzsprout endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Buzzsprout sources can also be configured manually, allowing you to ingest data from Buzzsprout endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Buzzsprout endpoints. Each template is designed specifically for the corresponding Buzzsprout endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    List Episodes

    This endpoint returns a list of all episodes for a Buzzsprout podcast. Use it to bulk-ingest your episode catalog for analytics, syndication, or backup workflows. The template issues paginated GET requests against https://www.buzzsprout.com/api/<podcast_id>/episodes.json and automatically advances through pages until no further data is returned.

    • Enter the podcast identifier in the Podcast ID field. This is the same numeric ID configured on your Buzzsprout credential and appears in your Buzzsprout URL (for example, the 9999 in /api/9999/episodes.json). This field is required.
    • No additional pagination configuration is needed — the template uses Buzzsprout's page and per_page query parameters with a default page size of 50 and stops automatically when an empty page is returned.

    For the full list of episode attributes returned by this endpoint, see the Buzzsprout episodes API reference.

    Get Episode

    This endpoint returns a single episode by ID. Use it when you already know the episode ID and want to fetch the latest details for that one record — for example, to refresh a specific episode after an edit in Buzzsprout.

    • Enter the podcast identifier in the Podcast ID field. This identifies the podcast that contains the episode.
    • Enter the target episode identifier in the Episode ID field. The episode ID can be obtained from the List Episodes endpoint or from the Buzzsprout admin UI.

    This endpoint is not paginated and returns a single JSON object representing the episode.

    Return all podcasts associated with the authenticated user's account.

    This endpoint retrieves all podcasts associated with the authenticated user's Buzzsprout account. Use it to discover the set of podcast IDs available to your credential — useful when an account hosts more than one podcast and you need to build downstream flows per podcast.

    • This endpoint takes no additional parameters. It issues a GET request to https://www.buzzsprout.com/api/podcasts.json using the credential's API token.
    • The response is a JSON array of podcast objects, each containing the podcast's ID, title, and metadata.

    Use the podcast IDs returned by this endpoint to configure the List Episodes and Get Episode endpoints, or to scope additional credentials.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Buzzsprout data sources can be manually configured to ingest data from any valid Buzzsprout API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Buzzsprout sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Buzzsprout API from the Method pulldown menu. The Buzzsprout API supports the following methods on its read endpoints:

    • GET: For retrieving podcasts and episodes from the API

API Endpoint URL​

  1. Enter the URL of the Buzzsprout API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. All Buzzsprout API URLs end in .json.

    • Example for listing episodes: https://www.buzzsprout.com/api/<podcast_id>/episodes.json
    • Example for a single episode: https://www.buzzsprout.com/api/<podcast_id>/episodes/<episode_id>.json
    • Example for listing podcasts: https://www.buzzsprout.com/api/podcasts.json

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL.

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime

    • {now-1} – The datetime one time unit before the current datetime

    • {now+1} – The datetime one time unit after the current datetime

    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)​

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data. This is particularly useful for chaining Buzzsprout calls — for example, using podcast IDs returned by the podcasts list endpoint to drive subsequent episode-list calls.

  1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

  2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data​

Optional

If only a subset of the data returned by the API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response.

Buzzsprout list endpoints return a top-level JSON array (for example, /episodes.json returns an array of episode objects), so the most common Path to Data value for Buzzsprout list endpoints is $[*]. Single-record endpoints such as /episodes/<id>.json return a JSON object and use $ as the path.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format, enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $[*] for a top-level array, or $.data.items[*] to access an array of items within a data object).
    Path to Data Example:

    For the Buzzsprout endpoint https://www.buzzsprout.com/api/<podcast_id>/episodes.json, which returns a top-level array of episode objects, set Path to Data to $[*] so that Nexla treats each array element as an individual record.

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

    PathSuggestions.png

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array.

Buzzsprout list endpoints return a bare top-level array with no surrounding metadata wrapper, so most Buzzsprout sources do not need to set a metadata path. This option is most useful for custom or chained endpoints whose responses include additional contextual fields.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

    • For responses in JSON format, enter the JSON path to the object or array that contains the metadata.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Buzzsprout recommends setting an explicit User-Agent header — requests using a default library user agent may be blocked.

    You do not need to include any headers already present in the credentials. The Authorization: Token token=... header is added automatically by Nexla from your Buzzsprout credential.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Buzzsprout 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.