Tickr Python Client
Simple, Shareable, Powerful Counters for Anything.
A Python client library for interacting with the Tickr API (counters service).
Features
- Fetch all your counters (requires authentication)
- Create a new counter (requires authentication)
- Fetch a public counter by slug
- Increment a counter (public or private, depending on API config)
- Update a counter (requires authentication and ownership)
- Delete a counter (requires authentication and ownership)
- Supports API key authentication (recommended; JWT is deprecated)
- Supports
is_privateandis_readonlycounter properties
Installation
pip install -e .
Usage
from tickr_client import TickrClient
# Create a client instance (API key is recommended for authenticated endpoints)
# You can get your API key from the Tickr API docs page: https://tickr.cc/api-docs
client = TickrClient(api_key="YOUR_API_KEY")
# Fetch all counters (authenticated)
counters = client.get_counters()
# Create a new counter (authenticated, with privacy/read-only options)
new_counter = client.create_counter(name="My Counter", initial_value=10, is_private=True, is_readonly=False)
# Fetch a public counter by slug
public_counter = client.get_counter(slug="abc123xyz")
# Increment a counter (public or private)
updated_counter = client.increment_counter(slug="abc123xyz", increment_by=2)
# Update a counter (authenticated, owner only)
updated = client.update_counter(slug="abc123xyz", name="Renamed", current_value=42, is_private=False)
# Delete a counter (authenticated, owner only)
client.delete_counter(slug="abc123xyz")
Authentication
For authenticated endpoints, obtain an API key from your Tickr dashboard and pass it to the client as api_key. Public endpoints do not require authentication.
Note: JWT authentication is deprecated. Use API keys for all new integrations.
Counter Properties
is_private: IfTrue, only authorized users can increment the counter.is_readonly: IfTrue, the counter cannot be incremented by anyone.
These properties are always included in returned counter objects.
License
MIT
Metadata
Release files for tickr-client 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tickr_client-0.1.2.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tickr_client-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.4 kB
Release files / tickr_client-0.1.2.tar.gz
| Download URL | tickr_client-0.1.2.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d02d968320f96a465484696a34e14d1d963b4afe23de706a1d9f208f551b78e9
|
|
BLAKE2b-256 checksum How to use checksums |
228d1b427cd98eed2598387330273c399b34cf5145ff5b654821a2dac4c06d4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.13
|
Release files / tickr_client-0.1.2-py3-none-any.whl
| Download URL | tickr_client-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5ff35861c5c60e568755c984741270df6ee1dd1a296d4229aac76de181f8f5e5
|
|
BLAKE2b-256 checksum How to use checksums |
37ac69f323d8d4a18acb77758c6f60e82d10a70c6e49c92dec00d041fc40eee1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.13
|
Security for tickr-client 0.1.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.