Memberstack Python API Docs | dltHub
Build a Memberstack-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Memberstack is a membership platform and authentication/identity management service that provides an Admin REST API to manage members, verify tokens, and perform administrative tasks. The REST API base URL is https://admin.memberstack.com and all requests require a secret key in the X-API-KEY header.
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 Memberstack data in under 10 minutes.
What data can I load from Memberstack?
Here are some of the endpoints you can load from Memberstack:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| members | /members | GET | data | List members (paginated: totalCount, endCursor, hasNextPage, data[]) |
| member | /members/:id_or_email | GET | data | Retrieve a single member by id (mem_...) or URL-encoded email |
| plans | /plans | GET | data | List plans (if present in docs; included for completeness) |
| verify_token | /members/verify-token | POST | Verify a JWT/webhook token (response contains verified member data) | |
| member_actions_add_plan | /members/:id/add-plan | POST | Add a free plan to a member | |
| member_actions_remove_plan | /members/:id/remove-plan | POST | Remove a free plan from a member |
How do I authenticate with the Memberstack API?
The Admin REST API uses secret API keys (test keys start with sk_sb_...; live keys start with sk_...) sent in the X-API-KEY header. Keep keys server-side and never expose them client-side. Include Content-Type: application/json for POST/PATCH requests.
1. Get your credentials
- Log into Memberstack dashboard. 2) Open Dev Tools / API Keys or Test Mode keys. 3) Create or copy a secret key (sk_sb_... for test, sk_... for live). 4) Store it in environment variables and use it in the X-API-KEY header.
2. Add them to .dlt/secrets.toml
[sources.memberstack_source] api_key = "sk_sb_your_secret_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:
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 Memberstack 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 memberstack_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline memberstack_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset memberstack_data The duckdb destination used duckdb:/memberstack.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline memberstack_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 members and member from the Memberstack 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 memberstack_source(secret_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://admin.memberstack.com", "auth": { "type": "api_key", "api_key": secret_key, }, }, "resources": [ {"name": "members", "endpoint": {"path": "members", "data_selector": "data"}}, {"name": "member", "endpoint": {"path": "members/:id_or_email", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="memberstack_pipeline", destination="duckdb", dataset_name="memberstack_data", ) load_info = pipeline.run(memberstack_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("memberstack_pipeline").dataset() sessions_df = data.members.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM memberstack_data.members LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("memberstack_pipeline").dataset() data.members.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 Memberstack 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 failures
If you receive 401 Unauthorized, verify the X-API-KEY header is present and contains a valid secret key (test keys start with sk_sb_, live keys start with sk_). Ensure the key is used server-side and not expired.
Rate limits (429)
Memberstack rate limits the Admin REST API to 25 requests per second. On 429 responses implement exponential backoff, batching and pagination to reduce request volume.
Pagination
List endpoints (e.g., GET /members) return pagination fields: totalCount, endCursor, hasNextPage, and data (array). Use endCursor as the after parameter and check hasNextPage to iterate.
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 Memberstack?
Request dlt skills, commands, AGENT.md files, and AI-native context.