LitePolis-router-particiapi
ParticiAPI-compatible router module for LitePolis.
Overview
This module implements the ParticiAPI specification, providing a simpler alternative API for the ParticiApp frontend. It works alongside LitePolis-router-default (Polis API) and can be used interchangeably.
Installation
litepolis-cli deploy add-deps litepolis-router-particiapi
litepolis-cli deploy sync-deps
Configuration
This module exports default configuration. To customize, create a config file:
litepolis-cli deploy init-config
Then edit ~/.litepolis/litepolis.config:
[litepolis_router_particiapi]
session_secret = your-secure-secret-key-here
csrf_token_expire_hours = 24
ParticiAPI Endpoints
| Endpoint | Method | Description |
|---|---|---|
/api/session |
POST | Create/refresh session |
/api/conversations/{id} |
GET | Get conversation |
/api/conversations/{id}/results/ |
GET | Get results (consensus/repness) |
/api/conversations/{id}/statements/ |
GET | Get all statements |
/api/conversations/{id}/statements/ |
POST | Submit new statement |
/api/conversations/{id}/participant |
GET | Get participant info |
/api/conversations/{id}/participant/notifications |
GET | Get notification settings |
/api/conversations/{id}/participant/notifications |
PUT | Set notification settings |
/api/conversations/{id}/votes/{tid} |
PUT | Submit vote |
Key Differences from Polis API
- Endpoint Structure:
/api/prefix vs/api/v3/ - Session Auth: Cookie-based sessions with CSRF tokens
- Error Format: RFC 7807 Problem+JSON responses
- Vote Values: AGREE=-1, NEUTRAL=0, DISAGREE=1 (inverted from Polis)
- Response Format: Direct JSON objects vs PolisResponse wrapper
Quick Start
- Install all ParticiAPI modules:
litepolis-cli deploy add-deps litepolis-database-particiapi
litepolis-cli deploy add-deps litepolis-router-particiapi
litepolis-cli deploy add-deps litepolis-ui-particiapp
litepolis-cli deploy sync-deps
- Start LitePolis server:
litepolis-cli deploy serve
Development Testing
pip install -e .
pytest tests/
Metadata
Release files for litepolis-router-particiapi 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| litepolis_router_particiapi-0.1.1.tar.gz | 7.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| litepolis_router_particiapi-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.6 kB
Release files / litepolis_router_particiapi-0.1.1.tar.gz
| Download URL | litepolis_router_particiapi-0.1.1.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b7858222cc5f14577fcbdca7641ab9b5cc5896ae88b951b16b491ad464a3579
|
|
BLAKE2b-256 checksum How to use checksums |
28b935a2ca7ba29260a01bf76785c7e48cacd36b44f9aa817272624f6566bcc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 24, 2026.
Transparency logRelease files / litepolis_router_particiapi-0.1.1-py3-none-any.whl
| Download URL | litepolis_router_particiapi-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
470fae993464a58c3c9e81c62f3f01c77918518d62fe409e138934ecaa0ce28a
|
|
BLAKE2b-256 checksum How to use checksums |
8f9c19c62776b27c96b77043accd4ac6642501a0c95fe3de81dc4b8b62c62870
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 24, 2026.
Transparency log