Xsolla

Xsolla is a game commerce company that provides tools and services for video game developers and publishers, including a store, in-game purchases, and payment processing. The Xsolla connector lets Nexla read catalog data such as games, virtual items, virtual currencies, and bundles from your project, and write new or updated catalog records back to Xsolla through the Store API.

Power end-to-end data operations for your Xsolla API with Nexla. Our bi-directional Xsolla connector is purpose-built for Xsolla, 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 Xsolla or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Xsolla 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 an Xsolla credential, you need an Xsolla Publisher Account with a configured project, your project's numeric Project ID, and an API Key. Xsolla authenticates Store API requests with the API key sent in the Authorization header as a bearer token.

To obtain your Xsolla credentials, follow these steps:

1. Sign in to your Xsolla Publisher Account.

2. Select the project you want to connect, or create a new project if you do not have one yet.

3. Locate your Project ID — the numeric identifier of the project shown in the Publisher Account. This value identifies which project the Store API requests apply to.

4. Open the API keys section under Project settings (or Company settings for a company-wide key) and create a new API key.

5. Copy the API key immediately after it is generated. Xsolla displays the key only once at creation time, so you must store it securely on your side.

Keep the API key confidential — it grants access to your Publisher Account and projects, and should be stored only on a trusted server, never in client applications. For more details, see the Xsolla Catalog API authentication documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key.
Project ID	Yes	No	Xsolla project ID (numeric identifier of your project in the Publisher Account).

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. Enter your Xsolla API key in the API Key field. This value is sent in the Authorization header as a bearer token and must be kept confidential.

4. Enter your numeric Project ID in the Project ID field. This identifies which Xsolla project the Store API requests apply to.

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

   If your API key is compromised, revoke it in your Xsolla Publisher Account and generate a new one. The API key grants access to your Publisher Account and projects and should be treated as sensitive information.

   For detailed information about Xsolla authentication and available endpoints, see the Xsolla Catalog API documentation.

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 Xsolla connector tile, then select the credential that will be used to connect to Xsolla, and click Next; or, create a new Xsolla 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 Xsolla 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] List Games Catalog

This endpoint template retrieves the games catalog for your Xsolla project. Use this template when you need to ingest the list of games available in your project for analysis, reporting, or integration.

• This endpoint returns the games in your project catalog and pages through results automatically to handle large catalogs.

For detailed information about the catalog response structure and available fields, see the Xsolla Catalog API documentation.

[Rest API] List Drm

This endpoint template retrieves the list of DRM (digital rights management) platforms available for games in your Xsolla project. Use this template when you need to ingest the DRM options associated with your game catalog.

• This endpoint returns the DRM entries defined for your project's games in a single request.

For detailed information about the DRM response structure and available fields, see the Xsolla Catalog API documentation.

[Rest API] List Virtual Items

This endpoint template retrieves the virtual items in your Xsolla project catalog. Use this template when you need to ingest virtual item data for analysis, reporting, or integration.

• This endpoint returns the virtual items in your project catalog and pages through results automatically to handle large catalogs.

For detailed information about the virtual items response structure and available fields, see the Xsolla Catalog API documentation.

[Rest API] List Virtual Currencies

This endpoint template retrieves the virtual currencies defined in your Xsolla project catalog. Use this template when you need to ingest virtual currency data for analysis, reporting, or integration.

• This endpoint returns the virtual currencies in your project catalog and pages through results automatically to handle large catalogs.

For detailed information about the virtual currencies response structure and available fields, see the Xsolla Catalog API documentation.

[Rest API] List Virtual Currency Packages

This endpoint template retrieves the virtual currency packages in your Xsolla project catalog. Use this template when you need to ingest currency package data for analysis, reporting, or integration.

• This endpoint returns the virtual currency packages in your project catalog and pages through results automatically to handle large catalogs.

For detailed information about the virtual currency packages response structure and available fields, see the Xsolla Catalog API documentation.

[Rest API] List Bundles

This endpoint template retrieves the bundles in your Xsolla project catalog. Use this template when you need to ingest bundle data for analysis, reporting, or integration.

• This endpoint returns the bundles in your project catalog and pages through results automatically to handle large catalogs.

For detailed information about the bundles response structure and available fields, see the Xsolla Catalog API documentation.

[Rest API] List Reward Chains

This endpoint template retrieves the reward chains configured for your Xsolla project. Use this template when you need to ingest reward chain data for analysis, reporting, or integration.

• This endpoint returns the reward chains in your project and pages through results automatically to handle large result sets.

For detailed information about the reward chains response structure and available fields, see the Xsolla Catalog API documentation.

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

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

This endpoint template creates a virtual item in your Xsolla project catalog using records from a Nexset. Use this template when you need to add new virtual items to your project based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new virtual item. Each record from your Nexset is sent as a separate API request, and the request body must contain the virtual item data in the format required by the Xsolla API.

For detailed information about virtual item creation, request body formats, and available properties, see the Xsolla Catalog API documentation.

[Rest API] Update Virtual Item

This endpoint template updates an existing virtual item, identified by its SKU, using records from a Nexset. Use this template when you need to modify virtual items already present in your project catalog.

• This endpoint requires an Item SKU value that identifies the virtual item to update. Each record from your Nexset is sent as JSON in the request body as a separate API request.

For detailed information about virtual item updates, request body formats, and available properties, see the Xsolla Catalog API documentation.

[Rest API] Create Bundle

This endpoint template creates a new bundle in your Xsolla project catalog using records from a Nexset. Use this template when you need to add new bundles to your project based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new bundle. Each record from your Nexset is sent as a separate API request, and the request body must contain the bundle data in the format required by the Xsolla API.

For detailed information about bundle creation, request body formats, and available properties, see the Xsolla Catalog API documentation.

[Rest API] Create Payment Order

This endpoint template creates a payment order token for a virtual item purchase using records from a Nexset. Use this template when you need to generate payment order tokens for items in your project catalog.

• This endpoint requires an Item SKU value that identifies the virtual item being purchased. Each record from your Nexset is sent as JSON in the request body as a separate API request.

For detailed information about payment order tokens, request body formats, and available properties, see the Xsolla Catalog API documentation.

[Rest API] Create Virtual Currency

This endpoint template creates a new virtual currency in your Xsolla project catalog using records from a Nexset. Use this template when you need to add new virtual currencies to your project based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new virtual currency. Each record from your Nexset is sent as a separate API request, and the request body must contain the virtual currency data in the format required by the Xsolla API.

For detailed information about virtual currency creation, request body formats, and available properties, see the Xsolla Catalog API documentation.

Manual configuration

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

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 Xsolla endpoint, open the destination resource menu, and select Activate.

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