InfoJobs Python API Docs | dltHub

Build a InfoJobs-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

InfoJobs API requires developer credentials for access. User authentication via OAuth2 is mandatory. Quick start guide available for immediate API use. The REST API base URL is https://api.infojobs.net and App requests use HTTP Basic (Client ID and Client Secret); user‑authorized operations use OAuth2 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 pip install "dlt[workspace]" and start loading InfoJobs data in under 10 minutes.


What data can I load from InfoJobs?

Here are some of the endpoints you can load from InfoJobs:

ResourceEndpointMethodData selectorDescription
offer_list/offerGETReturns a list of Job Offers matching search criteria
offer_get/offer/{offerId}GETReturns detail of an offer by id
application_list/applicationGETReturns list of job applications for the authenticated user
application_get/application/{applicationId}GETReturns application details for authenticated user
candidate_get/candidateGETReturns account data of the authenticated user
curriculum_list/curriculumGETReturns list of CVs for authenticated user
dictionary_get/dictionary/{dictionaryId}GETReturns all valid elements of a dictionary
coverletter_list/coverletterGETReturns list of user's cover letters

How do I authenticate with the InfoJobs API?

Include an Authorization header with HTTP Basic (Base64‑encoded ClientID:ClientSecret) for app authentication. For user‑scoped calls add the Bearer access token to the header, optionally combined with the basic credentials as shown in the docs.

1. Get your credentials

  1. Register or log in to the InfoJobs developers portal. 2) Create a new application; the portal will provide a Client ID and Client Secret. 3) For user‑scoped operations, implement the OAuth2 flow: direct the user to the authorization endpoint, receive the verification code, and exchange it for an access token via the token endpoint.

2. Add them to .dlt/secrets.toml

[sources.infojobs_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 InfoJobs 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 infojobs_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline infojobs_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset infojobs_data The duckdb destination used duckdb:/infojobs.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline infojobs_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 offer_list and application_list from the InfoJobs 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 infojobs_source(client_credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.infojobs.net", "auth": { "type": "http_basic", "client_secret": client_credentials, }, }, "resources": [ {"name": "offer_list", "endpoint": {"path": "offer"}}, {"name": "application_list", "endpoint": {"path": "application"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="infojobs_pipeline", destination="duckdb", dataset_name="infojobs_data", ) load_info = pipeline.run(infojobs_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("infojobs_pipeline").dataset() sessions_df = data.offer_list.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM infojobs_data.offer_list LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("infojobs_pipeline").dataset() data.offer_list.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 InfoJobs data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 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 InfoJobs?

Request dlt skills, commands, AGENT.md files, and AI-native context.