Xsolla Python API Docs | dltHub

Xsolla API is a platform that provides various functionalities for game developers and publishers, including Pay Station, Subscriptions, Login, and Shop Builder APIs. The REST API base URL is https://api.xsolla.com and Requests to the Xsolla API require Basic access authentication for server-side calls, using an Authorization header with a Base64 encoded merchant ID:API key pair, or a Bearer token for client-side calls..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Xsolla data in under 10 minutes.

---

What data can I load from Xsolla?

Here are some of the endpoints you can load from Xsolla:

---

How do I authenticate with the Xsolla API?

For server-side requests, the Xsolla API uses Basic access authentication, requiring an Authorization header with Basic followed by a Base64 encoded 'merchant ID:API key' pair. Client-side requests can use a Bearer token in the Authorization header.

1. Get your credentials

The provided documentation does not contain step-by-step instructions for obtaining API credentials from the Xsolla dashboard. It only mentions the requirement of a 'merchant ID:API key pair' for Basic authentication.

2. Add them to .dlt/secrets.toml

Copy
[sources.xsolla_games_source]
merchant_id = "your_merchant_id_here"
api_key = "your_api_key_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Xsolla API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
python xsolla_games_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline xsolla_games_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset xsolla_games_data
The duckdb destination used duckdb:/xsolla_games.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline xsolla_games_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads merchant_token and project_admin_payment_token from the Xsolla API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def xsolla_games_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.xsolla.com",
            "auth": {
                "type": "http_basic",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "merchant_token", "endpoint": {"path": "merchant/v2/merchants/{merchant_id}/token", "data_selector": "token"}},
            {"name": "project_admin_payment_token", "endpoint": {"path": "api/v2/project/{project_id}/admin/payment/token", "data_selector": "token"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="xsolla_games_pipeline",
        destination="duckdb",
        dataset_name="xsolla_games_data",
    )
    load_info = pipeline.run(xsolla_games_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("xsolla_games_pipeline").dataset()
sessions_df = data.merchant_token.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM xsolla_games_data.merchant_token LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("xsolla_games_pipeline").dataset()
data.merchant_token.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load Xsolla data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

API Error Handling

Xsolla API error responses are provided as JSON objects containing http_status_code, message, extended_message, and request_id fields. Common HTTP errors include 400 Bad Request, 401 Unauthorized, 402 Request Failed, 403 Forbidden, 404 Not Found, 409/422 Invalid request parameters, 412 Precondition Failed, 415 Unsupported Media Type, and 5xx Server Errors.

Pagination

List endpoints in the Xsolla API may paginate results. Pagination is typically handled using offset and limit parameters.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack