Spotify Ads

Spotify Ads is the advertising platform for the Spotify Ad Studio, exposed through the Spotify Ads API. It lets you manage ad accounts, ad sets, ads, and drafts, administer ad account members, and retrieve reporting and targeting reference data such as ad categories, all through the api-partner.spotify.com REST endpoints.

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

Before creating a Spotify Ads credential, you need to register an application in the Spotify Developer Dashboard, obtain its Client ID and Client Secret, and accept the Ads API Terms. The Spotify Ads API supports two authentication methods in Nexla: an API Key (a bearer token you supply directly) and OAuth 2.0 (the standard Spotify authorization-code flow, where Nexla obtains and refreshes access tokens on your behalf).

To register an application and obtain your credentials, follow these steps:

1. Sign in to the Spotify Developer Dashboard with your Spotify account.

2. Click Create app and enter a name and description for your application.

3. When asked which APIs you plan to use, select Ads API.

4. Configure a Redirect URI for the application (for example, http://127.0.0.1:8080/callback). This value is required by the authorization flow and must match the redirect URI used when requesting tokens.

5. Save the application, then open its Settings page to view the Client ID and to reveal the Client Secret. Store both values securely, as the Client Secret is sensitive.

6. Accept the Ads API Terms for your application by visiting the Spotify Ads API Terms page and signing in with the Client ID of the app you created. Requests to the Ads API will fail until this step is completed, and it can take up to one hour for your Client ID to be allowlisted after signing.

If you require access to campaign-management capabilities, or intend to onboard more than 25 users onto your app, Spotify requires additional review. Submit the pre-integration questionnaire or a quota-extension request from the Developer Dashboard, and the Spotify Ads API team will follow up.

For complete details about app registration, authorization, tokens, and available endpoints, see the Spotify Ads API documentation.

Authenticate

Credentials required

Api Key

An authentication method that requires sending a unique secret token with each API request

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests

OAuth 2.0

An OAuth authentication flow where users must authorize an application to access their data

Field	Required	Secret	Description
Authorization URL	No	No	The URL endpoint where users authenticate and authorize access
Client ID	Yes	Yes	A unique public identifier assigned to your application
Access Scope	No	No	A space-separated list of permissions your application requests
Token URL	No	No	The URL endpoint where authorization codes are exchanged for access tokens
Client Secret	No	Yes	A private key used to authenticate your application when requesting tokens

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. Select the authentication method you want to use:

   • Api Key: Enter your bearer token in the API Key Value field. Nexla sends this value in the Authorization header (as Bearer <token>) on every request. Because Spotify Ads access tokens expire after one hour, this method is best suited to short-lived tasks or when you manage token refresh externally.

   • OAuth 2.0: Enter the Client ID and Client Secret from your Spotify application. The Authorization URL and Token URL default to Spotify's standard endpoints (https://accounts.spotify.com/authorize/ and https://accounts.spotify.com/api/token) and can be left unchanged. Optionally provide a space-separated Access Scope. You will be redirected to Spotify to authorize the application, after which Nexla stores the resulting refresh token and automatically obtains new short-lived access tokens as needed.

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

The OAuth 2.0 method is recommended for ongoing data flows, since Nexla refreshes access tokens automatically and you do not need to manage the one-hour token expiration yourself. Keep your Client Secret and any bearer tokens confidential; if a value is compromised, rotate it from the Spotify Developer Dashboard.

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 Spotify Ads connector tile, then select the credential that will be used to connect to Spotify Ads, and click Next; or, create a new Spotify Ads 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 Spotify Ads 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] Get Ad Account by ID

Get Ad Account by ID.

• Provide the Ad Account Id for the ad account you want to retrieve. This endpoint returns the details of a single ad account.

[Rest API] Get all members in an ad account

Get all members in an ad account.

• Provide the Ad Account Id to list every member associated with that ad account.

[Rest API] Get Ad Categories

Get Ad Categories.

• Retrieve the list of available ad categories. Optionally supply a Q search term to filter the categories returned.

[Rest API] Get Ad Set by ID

Get Ad Set by ID.

• Provide the Ad Account Id and Ad Set Id to retrieve the details of a single ad set.

[Rest API] Get Ad Sets by Ad Account ID

Get Ad Sets by Ad Account ID.

• Provide the Ad Account Id to list the ad sets in that account. Optional query parameters, including limit, offset, sort direction, sort field, campaign IDs, name, and statuses, let you page through and filter the results.

[Rest API] Get Ad Set Drafts

Get Ad Set Drafts.

• Provide the Ad Account Id to list draft ad sets in that account. Optional query parameters, including limit, offset, campaign IDs, and statuses, let you page through and filter the results.

[Rest API] Get Draft Ad Set by ID

Get Draft Ad Set by ID.

• Provide the Ad Account Id and Draft Ad Set Id to retrieve the details of a single draft ad set.

[Rest API] Get Ads by Ad Account ID

Get Ads by Ad Account ID.

• Provide the Ad Account Id to list the ads in that account. Optional query parameters, including fields, ad set IDs, asset IDs, name, statuses, limit, offset, sort direction, and sort field, let you shape and filter the results.

[Rest API] Create an Ad

Create an Ad.

• Provide the Ad Account Id for the account in which the ad is created. This template issues a create request and returns any reject reasons reported for the submitted ad.

[Rest API] Get Ad by ID

Get Ad by ID.

• Provide the Ad Account Id and Ad Id to retrieve a single ad. Optionally supply a Fields parameter to control which fields are returned.

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

Spotify Ads data sources can also be manually configured to ingest data from any valid Spotify Ads 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 Spotify Ads 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 Spotify Ads destination, and select the Send to Destination option from the menu. Select the Spotify Ads connector from the list of available destination connectors, then select the credential that will be used to connect to Spotify Ads, and click Next; or, create a new Spotify Ads 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 Spotify Ads 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] Update Ad Account

Update Ad Account.

• Provide the Ad Account Id for the account to update. Each record from your Nexset is sent as the JSON request body of a PATCH request to modify the ad account.

[Rest API] Add a member to an ad account

Add a member to an ad account that belongs to a business.

• Provide the Ad Account Id for the account. Each record from your Nexset is sent as the JSON request body to add a member to the ad account.

[Rest API] Update an ad account member's role

Update an ad account member's role.

• Provide the Ad Account Id and Member Id to identify the member. Each record from your Nexset is sent as the JSON request body of a PATCH request to update that member's role.

[Rest API] Remove a member from an ad account

Remove a member from an ad account.

• Provide the Ad Account Id and Member Id to identify the member to remove. This template issues a DELETE request for the specified member.

[Rest API] Update Ad Set

Update Ad Set.

• Provide the Ad Account Id and Ad Set Id to identify the ad set. Each record from your Nexset is sent as the JSON request body of a PATCH request to update the ad set.

[Rest API] Create a Draft Ad Set from a Published Ad Set

Create a Draft Ad Set from a Published Ad Set.

• Provide the Ad Account Id and Ad Set Id of the published ad set. This template issues a POST request that creates a draft copy of the specified ad set.

[Rest API] Create an Ad Set

Create an Ad Set.

• Provide the Ad Account Id for the account in which the ad set is created. Each record from your Nexset is sent as the JSON request body to create a new ad set.

[Rest API] Create a Draft Ad Set

Create a Draft Ad Set.

• Provide the Ad Account Id for the account. Each record from your Nexset is sent as the JSON request body to create a new draft ad set.

[Rest API] Update a Draft Ad Set

Update a Draft Ad Set.

• Provide the Ad Account Id and Draft Ad Set Id to identify the draft. Each record from your Nexset is sent as the JSON request body of a PATCH request to update the draft ad set.

[Rest API] Delete a Draft Ad Set

Delete a Draft Ad Set.

• Provide the Ad Account Id and Draft Ad Set Id to identify the draft to remove. This template issues a DELETE request for the specified draft ad set.

Manual configuration

Spotify Ads destinations can also be manually configured to send data to any valid Spotify Ads 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.

Spotify Ads APIs expect JSON format for create and update operations. For update and delete operations, include the relevant ad account, ad set, member, or draft identifier in 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 Spotify Ads endpoint, open the destination resource menu, and select Activate.

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