Simployer Python API Docs | dltHub
Build a Simployer-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Simployer provides a suite of APIs for managing employee information, analytics, and HR processes within their tenant ecosystem. The REST API base URL is https://api.simployer.com/v1 and all requests require an Authorization header with a Bearer token.
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 add "dlt[hub]" and start loading Simployer data in under 10 minutes.
What data can I load from Simployer?
Here are some of the endpoints you can load from Simployer:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| employees | /employees | GET | Retrieves a list of employees | |
| departments | /departments | GET | Retrieves a list of departments | |
| positions | /positions | GET | Retrieves a list of positions | |
| locations | /locations | GET | Retrieves a list of locations | |
| contracts | /contracts | GET | Retrieves a list of contracts |
How do I authenticate with the Simployer API?
Authentication is performed by including a JWT-based access token in the Authorization header of requests, typically using the 'Bearer' scheme (e.g., 'Authorization: Bearer '). Access tokens are obtained via the SimplAuth protocol using client credentials (client ID and secret).
1. Get your credentials
To access Simployer APIs, you typically use either the Simployer Admin Center or the user-specific Settings area depending on your target API. For system-wide integrations (such as HR Connect or Handbooks API), contact Simployer Customer Care to request access to the 'Admin Center'. Once you have access: 1. Log in to the Admin Center. 2. Create a new API client or client credential. 3. Generate a client secret (store this safely immediately as it cannot be retrieved again). 4. Use the client ID and secret to obtain an OAuth 2.0 access token via the SimplAuth authentication server. For Simployer One (formerly AlexisHR) APIs, users with 'Owner' permissions can generate an access token directly by navigating to 'Settings' -> 'Access tokens' in the main portal. Always copy your generated token or secret immediately as it will not be displayed again.
2. Add them to .dlt/secrets.toml
[sources.simployer_source] simployer_api_key = "your_api_key_or_access_token_here" simployer_client_id = "your_client_id_if_using_simplauth" simployer_client_secret = "your_client_secret_if_using_simplauth"
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 Simployer 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:
uv run python simployer_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline simployer_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset simployer_data The duckdb destination used duckdb:/simployer.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 employees and units from the Simployer 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 simployer_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.simployer.com/v1", "auth": {"type": "bearer", "token": api_token}, }, "resources": [ {"name": "employees", "endpoint": {"path": "employees"}}, {"name": "departments", "endpoint": {"path": "departments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="simployer_pipeline", destination="duckdb", dataset_name="simployer_data", ) load_info = pipeline.run(simployer_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("simployer_pipeline").dataset() sessions_df = data.employees.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM simployer_data.employees LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("simployer_pipeline").dataset() data.employees.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 Simployer 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.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Simployer?
Request dlt skills, commands, AGENT.md files, and AI-native context.