Skip to main content

Tek Juice Data Engine Connector

A standalone, framework-agnostic Python package that customer backends install with pip to authenticate with the Tek Juice Data Engine.

What it does

  • Authenticates your backend with the Tek Juice Data Engine via an E2E handshake.
  • Reports READY state when the Data Engine confirms the backend is connected.
  • Provides bounded retry with exponential backoff for transient failures.
  • Sanitises all log output and diagnostic reports — secrets never leak.
  • Provides a CLI for configuration verification and connectivity testing.

What it does NOT do

This package does not implement content generation, SEO, publication, M2M authentication, or any Data Engine internal logic. It is a connection package only.

Quick start

1. Install

pip install tekjuice-connector

2. Configure

Set the three required environment variables:

export TEKJUICE_WEBSITE_ID=your-website-id
export TEKJUICE_CONNECTOR_KEY=your-connector-key
export TEKJUICE_DATA_ENGINE_URL=https://engine.tekjuice.io

3. Connect

from tekjuice_connector import TekJuiceConnector

connector = TekJuiceConnector()
result = connector.connect()

if result.ready:
    print("Tek Juice Data Engine connected")
    print("Domain:", result.domain)

4. Test the connection

tekjuice test-connection

5. Run diagnostics

tekjuice diagnostics

Requirements

  • Python 3.11+
  • requests >= 2.28

No web framework required.

Configuration

Variable Description
TEKJUICE_WEBSITE_ID Your Tek Juice website identifier
TEKJUICE_CONNECTOR_KEY Your connector key (treat as a secret)
TEKJUICE_DATA_ENGINE_URL Base URL of the Tek Juice Data Engine API

See docs/configuration.md for full details.

CLI commands

tekjuice status              # Print current connection state
tekjuice test-connection     # Live E2E handshake test
tekjuice diagnostics         # Full diagnostic report
tekjuice --version           # Print package version

Security

The connector key is never logged, never included in exception messages, and never appears in diagnostic output. See docs/security.md.

Authentication vs M2M

Connector E2E authentication (this package) and Tek Juice Data Engine M2M publication authentication are completely separate systems. This package does not implement M2M. See docs/authentication.md.

Documentation

Development

git clone https://github.com/tekjuice/tekjuice-connector.git
cd tekjuice-connector
pip install -e ".[dev]"
pytest

License

MIT License. See LICENSE.

Metadata

Release files for tekjuice-connector 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tekjuice-connector 0.1.0
File Size Uploaded Provenance
tekjuice_connector-0.1.0.tar.gz 43.0 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for tekjuice-connector 0.1.0
File Interpreter ABI Platform
tekjuice_connector-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 107.9 kB

Release files / tekjuice_connector-0.1.0.tar.gz

Download URL tekjuice_connector-0.1.0.tar.gz
Size 43.0 kB
Tags Source
SHA-256 checksum
How to use checksums
fdd1b0f0a8fc3550249d90a67648ca6d2b2c41df785b2f8b261df1b9e2d98823
BLAKE2b-256 checksum
How to use checksums
2533e030510a5a52de8961cfe18859e59d7ecabda31b67c17982472cde5a656a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release files / tekjuice_connector-0.1.0-py3-none-any.whl

Download URL tekjuice_connector-0.1.0-py3-none-any.whl
Size 64.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0facfd753225b3b0a9b9c3a0091c5cd7724dde8c50e0cad344748358cfb443d0
BLAKE2b-256 checksum
How to use checksums
9e47c143ddcbed1d9d859c670b1a6a32fed6c45b98c5d9de09944c2271b5507f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Security for tekjuice-connector 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for tekjuice_connector-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page