Spot by Flexera Python API Docs | dltHub
Build a Spot by Flexera-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Spot by Flexera is a cloud optimization platform that provides REST APIs to manage Spotinst resources. The REST API base URL is https://api.spotinst.io and All requests require a Bearer token for authentication.
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 Spot by Flexera data in under 10 minutes.
What data can I load from Spot by Flexera?
Here are some of the endpoints you can load from Spot by Flexera:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| account | /setup/account | GET | Retrieves account details | |
| apikeys | /connect/settings/apikeys | GET | items | Lists API keys created under Connect Settings |
| ocean_cluster_logs | /ocean/cluster/logs | GET | items | Returns log entries for Ocean clusters |
| aws_ec2_group_roll | /aws/ec2/group/{groupId}/roll | GET | items | Shows rollout information for an EC2 group |
| security_policies | /security/v1/policies | GET | items | Lists security/compliance policies |
| notifications | /notificationCenter/notifications | GET | items | Retrieves notifications generated by Spot |
How do I authenticate with the Spot by Flexera API?
The API uses Bearer Token authentication. Include the header Authorization: Bearer <token> in every request.
1. Get your credentials
- Log in to the Spot dashboard.
- Navigate to Connect Settings → API Keys.
- Click Create API Key (or Create Programmatic User).
- Give the key a name and optional permissions, then Save.
- Copy the generated token; it will be shown only once.
- Store the token securely for use in API calls.
2. Add them to .dlt/secrets.toml
[sources.spot_by_flexera_source] token = "your_spot_token_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:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
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:
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 Spot by Flexera 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:
python spot_by_flexera_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline spot_by_flexera_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset spot_by_flexera_data The duckdb destination used duckdb:/spot_by_flexera.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline spot_by_flexera_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 account and apikeys from the Spot by Flexera API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def spot_by_flexera_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.spotinst.io", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "account", "endpoint": {"path": "setup/account"}}, {"name": "apikeys", "endpoint": {"path": "connect/settings/apikeys", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="spot_by_flexera_pipeline", destination="duckdb", dataset_name="spot_by_flexera_data", ) load_info = pipeline.run(spot_by_flexera_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):
import dlt data = dlt.pipeline("spot_by_flexera_pipeline").dataset() sessions_df = data.apikeys.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM spot_by_flexera_data.apikeys LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("spot_by_flexera_pipeline").dataset() data.apikeys.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 Spot by Flexera data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Troubleshooting
Authentication errors
- 401 Unauthorized – occurs when the Bearer token is missing, invalid, or expired. Ensure the
Authorization: Bearer <token>header is present and the token has not been revoked.
Rate limiting
- Spot APIs enforce request limits per account. A 429 Too Many Requests response indicates the limit has been exceeded. The response body contains an
errorobject withcodeandmessage. Implement exponential backoff and respect theRetry-Afterheader if provided.
Pagination quirks
- Many list endpoints return a paginated payload with
nextKey/previousKeyor apaginationInfoobject. Use thenextKeyvalue in the subsequent request's query parameter to retrieve the next page. Some endpoints uselimitandoffsetinstead.
Generic error format
- Errors are returned as JSON with an
errorfield, e.g.:
"error" : { "code" : "string", "message" : "string" }
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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Spot by Flexera?
Request dlt skills, commands, AGENT.md files, and AI-native context.