Naylor Python API Docs | dltHub
Build a Naylor-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Naylor (Timberlake) AMS REST API is an API that provides access to member, organization, event, and registrant data, with responses primarily in XML format. The REST API base URL is https://{baseurl}/api and All requests require a partner-provided securityKey passed as a query parameter 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 Naylor data in under 10 minutes.
What data can I load from Naylor?
Here are some of the endpoints you can load from Naylor:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| get_all_members | /api/GetAllMembers | GET | Member | Returns an array of Member class objects |
| get_all_member_types | /api/GetAllMemberTypes | GET | MemberTypes | Returns an array of MemberTypes |
| get_all_organizations | /api/GetAllOrganizations | GET | Organizations | Returns an array of Organizations |
| get_events | /api/GetEvents | GET | EventListItem | Returns an array of EventListItem objects |
| get_event_registrants | /api/GetEventRegistrants | GET | Registrant | Returns an array of Registrant objects |
| get_member_info | /api/GetMemberInfo | GET | Returns member fields and addresses | |
| get_member_key_using_email | /api/GetMemberKeyUsingEmail | GET | GetMemberKeyUsingEmailResult | Returns a member key using an email |
| authenticate_user | /api/AuthenticateUser | GET | ContactId | Returns a ContactId for an authenticated user |
| get_organization_info | /api/GetOrganizationInfo | GET | Returns organization fields | |
| get_server_time | /api/GetServerTime | GET | GetServerTimeResult | Returns the server time |
How do I authenticate with the Naylor API?
Authentication requires a partner-provided securityKey that must be passed as a query parameter in all API calls.
1. Get your credentials
Prior to development, the partner will receive the security key and base URL directly from Naylor.
2. Add them to .dlt/secrets.toml
[sources.naylor_source] security_key = "your_security_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 Naylor 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 naylor_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline naylor_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset naylor_data The duckdb destination used duckdb:/naylor.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline naylor_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 get_all_members and get_all_organizations from the Naylor 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 naylor_source(security_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{baseurl}/api", "auth": { "type": "api_key", "securityKey": security_key, }, }, "resources": [ {"name": "get_all_members", "endpoint": {"path": "GetAllMembers", "data_selector": "Member"}}, {"name": "get_all_organizations", "endpoint": {"path": "GetAllOrganizations", "data_selector": "Organizations"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="naylor_pipeline", destination="duckdb", dataset_name="naylor_data", ) load_info = pipeline.run(naylor_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("naylor_pipeline").dataset() sessions_df = data.get_all_members.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM naylor_data.get_all_members LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("naylor_pipeline").dataset() data.get_all_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 Naylor 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
If an invalid securityKey is provided, the API will return an InvalidSecurityKey error. For SSO token validation, a NULL or blank response indicates failure.
Pagination and Data Retrieval
The API does not specify pagination. However, 'changed' endpoints (e.g., for changed members or organizations) accept updatedSince dates to retrieve incremental differences, which can be used for efficient data synchronization.
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 Naylor?
Request dlt skills, commands, AGENT.md files, and AI-native context.