Load Divine API data to DuckDB

Divine API provides a comprehensive suite of astrology, tarot, numerology, and horoscope endpoints for developers. Everything needed to build a working Divine API → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Divine API to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Divine API to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Divine API API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Divine API API at a glance

These values come from the Divine API API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Divine API API?

All REST API requests require an 'Authorization' header with the format 'Bearer {token}', where {token} is your secure Access Token.

1. Get your credentials

1. Sign in to your Divine API account at divineapi.com. 2. Navigate to the dashboard. 3. Locate the menu or user icon (usually at the top-right corner) and select 'API Credentials' or 'API Key' from the menu. 4. On the credentials page, you can view, unlock, and copy your 'API Key' and 'Access Token'. Both live (production) and test credentials are available on this page.

2. Add them to .dlt/secrets.toml

Copy
[sources.divine_api_source]
api_key = "your_api_key_here"
auth_token = "your_auth_token_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Divine API data can I load into DuckDB?

These are the Divine API endpoints dlt can load into DuckDB:

---

How do I load only new Divine API records?

The Divine API API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "planetary_positions", "endpoint": {
    "path": "indian-api/v1/planetary-positions",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Divine API pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /indian-api/v1/planetary-positions and /indian-api/v1/kundli from the Divine API API into DuckDB:

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

@dlt.source
def divine_api_source(auth_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "The REST API utilizes multiple base URLs depending on the specific endpoint (e.g., 'https://astroapi-1.divineapi.com', 'https://astroapi-3.divineapi.com', 'https://astroapi-4.divineapi.com', 'https://astroapi-5.divineapi.com').",
            "auth": {"type": "bearer", "token": auth_token},
        },
        "resources": [
            {"name": "planetary_positions", "endpoint": {"path": "indian-api/v1/planetary-positions", "data_selector": "data"}},
            {"name": "vimshottari_dasha", "endpoint": {"path": "indian-api/v1/vimshottari-dasha", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_divine_api_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="divine_api_pipeline",
        destination="duckdb",
        dataset_name="divine_api_data",
    )
    load_info = pipeline.run(divine_api_source())
    print(load_info)


if __name__ == "__main__":
    load_divine_api_to_duckdb()

Run it with python divine_api_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Divine API data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("divine_api_pipeline").dataset()
df = data.planetary_positions.df()
print(df.head())

SQL:

Copy
SELECT * FROM divine_api_data.planetary_positions LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Divine API to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Divine API loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Divine API data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack