<p align="center">
<img src="https://heibox.uni-heidelberg.de/f/43bdc63b9458478e949f/?dl=1" alt="elAPI logo" width=120 />
</p>
<p align="center">
<a href="https://pypi.org/project/elapi">
<img alt="Package version" src="https://badge.fury.io/py/elapi.svg/?branch=main" />
</a>
<a href="#compatibility">
<img alt="Static Badge" src="https://img.shields.io/badge/python-3.9%20%7C%203.10%20%7C%203.11%20%7C%203.12-%230d7dbe">
<img alt="Static Badge" src="https://img.shields.io/badge/eLabFTW%20support-4.5%2B%20%7C%205.0%20%7C%205.1-%2323b3be">
</a>
</p>
elAPI is a powerful, extensible API client for [eLabFTW](https://www.elabftw.net/) developed at
the [University Computing Centre](https://www.urz.uni-heidelberg.de/en)
(URZ, [FIRE](https://www.urz.uni-heidelberg.de/en/node/64/organisation/future-it-research-education) division) of
[University of Heidelberg](https://www.uni-heidelberg.de/en). It supports serving all kinds of requests documented in
[eLabFTW API documentation](https://doc.elabftw.net/api/v2/) with ease. elAPI provides a simple interface via its CLI
executable, and numerous advanced APIs when it is used directly as a Python package.
<img src="https://heibox.uni-heidelberg.de/f/7714c7eeb0f54a3ba318/?dl=1" alt="elAPI features in a nutshell" />
**Example:**
From [the documentation](https://doc.elabftw.net/api/v2/#/Users/read-user):
> GET /users/{id}
With elAPI you can do the following:
```sh
$ elapi get experiments --format csv --export ~/Downloads/
```
Once the command is run, in the background, elAPI will read host (eLab server) address, API key and various other
settings (see [configuration](#configuration)) from the configuration file `elapi.yml`, perform validation (e.g.,
whether the server address is valid), fetch all _experiments_ list, convert them to `CSV`, and export them to your
local `~/Downloads/` folder.
## Installation
We recommend [`pipx`](https://pipx.pypa.io/stable/) for installing elAPI for use of its CLI functionalities. Pipx
installs packages in isolated virtual environments, so Pipx-installed elAPI should not conflict with elAPI installed
inside other virtual environments.
```shell
$ pipx install elapi
```
After installation with Pipx is complete, you would also be able to run elAPI just by entering the `elapi` command on
the terminal. You can move on to ["Getting started"](#getting-started).
### Advanced installation
elAPI can be used both as a CLI tool and as a Python library. If you are interested in simply using elAPI's
off-the-shelf features from the command-line, install elAPI as a CLI tool (see ["Installation"](#installation)). If you
intend to write automation script for eLabFTW, you should install elAPI as a library inside a virtual environment. Of
course, if you're interested in both, you can have elAPI installed in both ways.
> [!NOTE]
> Support for installing Python packages with `pip install --user` has been deprecated with the adoption
> of [PEP 688](https://peps.python.org/pep-0668/) on many systems
> like [Debian 12](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030335#5).
### Installing elAPI as a library
It is recommended to install elAPI inside a Python virtual environment with your preferred package manager (`pip`,
`poetry`, `pipenv`, `rye`, `uv`, etc.) for use of its rich APIs for
working with eLabFTW. From inside a virtual environment, elAPI CLI can be invoked with `python -m elapi.cli`.
At the moment, though, the documentation about using elAPI as a library is severely lacking.
## Getting started
Once you have elAPI [installed](#installation), to **quickly** get started, run `elapi init`. You will be prompted with
questions about your eLabFTW server with examples to help you fill in the answers. Here's a demo:
```shell
$ elapi init
```
<video src='https://github.com/user-attachments/assets/8d5f69ed-b644-4d75-b816-d06d4e937105'> </video>
<p align="center">elapi init demo</p>
That's all! Run [`elapi show-config`](#show-config) to view your configuration details.
## Compatibility
elAPI is compatible with the following Python versions: `3.9`, `3.10`, `3.11`, `3.12`. elAPI supports
the [eLabFTW REST API v2](https://doc.elabftw.net/api/v2/), and can be used with the following eLabFTW
versions: `4.5`, `4.6`, `4.7`, `4.8`, `4.9`, `4.10`, `5.0`, `5.1`.
## Configuration
elAPI needs to be configured first before you can do anything useful with it. Mainly, elAPI needs to know your eLabFTW
server's API URL and your API key (or token) for access. See quick configuration method
in "[Getting started](#getting-started)" before you dive into the advanced settings.
### Advanced configuration
elAPI supports a YAML configuration file in
the following locations.
- Current directory: `./elapi.yml`
- User directory: `$HOME/.config/elapi.yml`
- Root directory: `/etc/elapi.yml`
elAPI supports configuration overloading. I.e., a keyword set in root configuration file `/etc/elapi.yml` can be
overridden by setting a different value in user configuration file `$HOME/.config/elapi.yml`. In terms of precedence,
configuration file present in the currently active directory has the highest priority, and configuration in root
directory has the lowest.
The following parameters are currently configurable, with `host` and `api_token` being the required fields. For testing
purposes, it would be safe to store everything in `$HOME/.config/elapi.yml`.
```yaml
# elAPI configuration
# Saved in `$HOME/.config/elapi.yml`
host: <host API url>
# Example: https://demo.elabftw.net/api/v2/
# Note the host URL ends with the API endpoint
api_token: <token with at least read-access>
# "A.k.a API key". You can generate an API token from eLabFTW user panel -> API keys tab.
export_dir: ~/Downloads/elAPI
unsafe_api_token_warning: true
enable_http2: false
verify_ssl: true
timeout: 90
```
- `export_dir` is where elAPI will export response content to if no path is explicitly provided to `--export/-E`.
- When `unsafe_api_token_warning` is `True`, elAPI will show a warning if you're storing `elapi.yml` in the current
working directory, as it typically happens that developers accidentally commit and push configuration files with
secrets.
- `enable_http2` enables HTTP/2 protocol support which by default is turned off. Be aware
of [known issues](https://github.com/encode/httpx/discussions/2112) with HTTP/2 if you are making async requests with
a heavy load.
- `verify_ssl` can be turned off with value `False` if you are
trying out a development server that doesn't provide a valid SSL certificate.
- `timeout` can be modified to your needs. E.g., a poor internet connection might benefit from a higher timeout number.
The default timeout is `90` seconds.
### `show-config`
You can get an overview of detected configuration with `elapi show-config`. `show-config` makes it easier to verify
which configuration values are actually used by elAPI, if you are working with multiple configuration files.
```shell
$ elapi show-config # system username: "culdesac"
```
If both `host` and `api_token` are detected, you are good to go!
### Overriding configuration
elAPI now supports `--override/--OC` as a global option that can be used to override the configuration parameters
as detected by `elapi show-cofig`. All plugins will also automatically listen to the overridden configuration. This can
be useful to set certain configurations temporarily. E.g., `elapi --OC '{"timeout": 300"}' get info` will override
the `timeout` from the configuration files.
## Usage
elAPI can be invoked from the command-line.
```shell
$ elapi --help
```
### `GET` requests
Request an overview of running eLabFTW server:
```shell
$ elapi get info -F yml
# Here -F (or --format) defines the output format
```
You can request a list o all active experiments and export it to a `JSON` file.
```shell
$ elapi get experiments --export ~/Downoads/experiments.json
```
Enable built-in syntax highlighting with `--highlight` or `-H`. Here, the following command will fetch team information
of team with team ID 1.
```shell
$ elapi get -H teams --id 1
```
### `POST` requests
Create a new user by the name 'John Doe':
```shell
$ elapi post users --id <user id> -d '{"firstname": "John", "lastname": "Doe", "email": "test_test@itnerd.de"}'
```
### `PATCH` requests
Update an existing user's email address:
```shell
$ elapi patch users --id <user id> -d '{"email": "new_email@itnerd.de"}'
```
`patch` command allows us to make changes to eLabFTW server settings. E.g., you can update the time (in minutes)
after which the authentication cookie will expire.
```shell
$ elapi patch config -d '{"cookie_validity_time": 43200}'
```
You can publish an announcement to all the members.
```shell
$ elapi patch config -d '{"announcement": "Notice: Server will be down tomorrow at midnight due to scheduled maintenance."}'
```
### `DELETE` requests
Delete all the tags associated to an experiment:
```shell
$ elapi delete experiments -i <experiment ID> --sub tags
```
You can reset the configuration to default values.
```shell
$ elapi delete config
```
### `experiments` built-in plugin
`experiments` plugin enables experiments-specific actions. You can download an experiment in PDF by its "Unique eLabID"
to `~/Downloads` directory.
```shell
$ elapi experiments get -i <experiment unique elabid> -F pdf --export ~/Downloads/
```
Append text in markdown to an existing experiment by its ID:
```shell
$ elapi experiments append --id <experiment ID> -M -t "**New content.**"
```
You can also upload an attachment to an experiment.
```shell
$ elapi experiments upload-attachment --id <experiment ID> --path <path to attachment file> --comment <comment for your attachment>
```
## Creating a plugin
elAPI has seamless support with tight-integration for third-party plugins. A simple third-party plugin can be created in
a few easy steps:
1. Create a new subfolder under `~/.local/share/elapi/plugins` with the name for your new plugin (e.g, a folder named
"test")
2. Create a `cli.py` in the subfolder with the following snippet:
```python
from elapi.plugins.commons import Typer
app = Typer(name="test", help="Test plugin.")
```
3. Run `elapi` again to see your plugin name under `Third-party plugins` list
Plugins are integrated in a way such that a plugin will **not** fail elAPI. So, even if one erroneous plugin is loaded,
all
other plugins and elAPI itself will remain unaffected. elAPI will show the error message on the "Message" panel.
If you try to import a package that is not a dependency of elAPI inside `cli.py`, your plugin will fail. In that case,
you want to create a plugin metadata file `elapi_plugin_metadata.yml` (notice only `.yml` extension is allowed), and
define the virtual environment that your plugin specifically requires.
```python
import requests # A third-party dependency
from elapi.api import GETRequest
from elapi.plugins.commons import Typer
# Plugin metadata
app = Typer(name="awesome", help="An awesome elAPI plugin.")
@app.command(name="get-request", short_help=f"Make a GET request")
def get_request(endpoint_name):
r = GETRequest()
print(r(endpoint_name).json())
@app.command(name="get-wiki-status", short_help=f"Show status of Wikipedia")
def wiki_status():
r = requests.get("https://wikipedia.org")
print(r)
```
And the path to virtual environment will be defined in the metadata file:
```yaml
# elapi_plugin_metadata.yml
plugin_name: awesome
cli_script: ~/awesome/cli.py # Path to the cli.py script
venv_dir: ~/awesome/.venv # Path to the virtual environment
project_dir: ~/awesome # Path to the project root directory where the plugin is located
```
This metadata file of plugin `awesome` must be placed inside `~/.local/share/elapi/plugins/awesome`. Notice, the plugin
name must also match the parent directory name of `elapi_plugin_metadata.yml`. This way we ensure a plugin name remains
unique.
Raw data
{
"_id": null,
"home_page": "https://www.urz.uni-heidelberg.de/en/service-catalogue/software-and-applications/elabftw",
"name": "elapi",
"maintainer": "Mahadi Xion",
"docs_url": null,
"requires_python": "<4.0.0,>=3.9.0",
"maintainer_email": "mahadi.xion@urz.uni-heidelberg.de",
"keywords": "elabftw, api",
"author": "Alexander Haller, Mahadi Xion",
"author_email": "elabftw@uni-heidelberg.de",
"download_url": "https://files.pythonhosted.org/packages/4f/53/ee69c53839d2e2de0124488322c37b384daba63656aa8c2b27f48ca5ae90/elapi-2.2.0.tar.gz",
"platform": null,
"description": "<p align=\"center\">\n<img src=\"https://heibox.uni-heidelberg.de/f/43bdc63b9458478e949f/?dl=1\" alt=\"elAPI logo\" width=120 />\n</p>\n\n<p align=\"center\">\n <a href=\"https://pypi.org/project/elapi\">\n<img alt=\"Package version\" src=\"https://badge.fury.io/py/elapi.svg/?branch=main\" />\n </a>\n<a href=\"#compatibility\">\n <img alt=\"Static Badge\" src=\"https://img.shields.io/badge/python-3.9%20%7C%203.10%20%7C%203.11%20%7C%203.12-%230d7dbe\">\n <img alt=\"Static Badge\" src=\"https://img.shields.io/badge/eLabFTW%20support-4.5%2B%20%7C%205.0%20%7C%205.1-%2323b3be\">\n</a>\n</p>\n\nelAPI is a powerful, extensible API client for [eLabFTW](https://www.elabftw.net/) developed at\nthe [University Computing Centre](https://www.urz.uni-heidelberg.de/en)\n(URZ, [FIRE](https://www.urz.uni-heidelberg.de/en/node/64/organisation/future-it-research-education) division) of\n[University of Heidelberg](https://www.uni-heidelberg.de/en). It supports serving all kinds of requests documented in\n[eLabFTW API documentation](https://doc.elabftw.net/api/v2/) with ease. elAPI provides a simple interface via its CLI\nexecutable, and numerous advanced APIs when it is used directly as a Python package.\n\n<img src=\"https://heibox.uni-heidelberg.de/f/7714c7eeb0f54a3ba318/?dl=1\" alt=\"elAPI features in a nutshell\" />\n\n**Example:**\n\nFrom [the documentation](https://doc.elabftw.net/api/v2/#/Users/read-user):\n> GET /users/{id}\n\nWith elAPI you can do the following:\n\n```sh\n$ elapi get experiments --format csv --export ~/Downloads/\n```\n\nOnce the command is run, in the background, elAPI will read host (eLab server) address, API key and various other\nsettings (see [configuration](#configuration)) from the configuration file `elapi.yml`, perform validation (e.g.,\nwhether the server address is valid), fetch all _experiments_ list, convert them to `CSV`, and export them to your\nlocal `~/Downloads/` folder.\n\n## Installation\n\nWe recommend [`pipx`](https://pipx.pypa.io/stable/) for installing elAPI for use of its CLI functionalities. Pipx\ninstalls packages in isolated virtual environments, so Pipx-installed elAPI should not conflict with elAPI installed\ninside other virtual environments.\n\n```shell\n$ pipx install elapi\n```\n\nAfter installation with Pipx is complete, you would also be able to run elAPI just by entering the `elapi` command on\nthe terminal. You can move on to [\"Getting started\"](#getting-started).\n\n### Advanced installation\n\nelAPI can be used both as a CLI tool and as a Python library. If you are interested in simply using elAPI's\noff-the-shelf features from the command-line, install elAPI as a CLI tool (see [\"Installation\"](#installation)). If you\nintend to write automation script for eLabFTW, you should install elAPI as a library inside a virtual environment. Of\ncourse, if you're interested in both, you can have elAPI installed in both ways.\n\n> [!NOTE]\n> Support for installing Python packages with `pip install --user` has been deprecated with the adoption\n> of [PEP 688](https://peps.python.org/pep-0668/) on many systems\n> like [Debian 12](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030335#5).\n\n### Installing elAPI as a library\n\nIt is recommended to install elAPI inside a Python virtual environment with your preferred package manager (`pip`,\n`poetry`, `pipenv`, `rye`, `uv`, etc.) for use of its rich APIs for\nworking with eLabFTW. From inside a virtual environment, elAPI CLI can be invoked with `python -m elapi.cli`.\nAt the moment, though, the documentation about using elAPI as a library is severely lacking.\n\n## Getting started\n\nOnce you have elAPI [installed](#installation), to **quickly** get started, run `elapi init`. You will be prompted with\nquestions about your eLabFTW server with examples to help you fill in the answers. Here's a demo:\n\n```shell\n$ elapi init\n```\n\n<video src='https://github.com/user-attachments/assets/8d5f69ed-b644-4d75-b816-d06d4e937105'> </video>\n<p align=\"center\">elapi init demo</p>\n\nThat's all! Run [`elapi show-config`](#show-config) to view your configuration details.\n\n## Compatibility\n\nelAPI is compatible with the following Python versions: `3.9`, `3.10`, `3.11`, `3.12`. elAPI supports\nthe [eLabFTW REST API v2](https://doc.elabftw.net/api/v2/), and can be used with the following eLabFTW\nversions: `4.5`, `4.6`, `4.7`, `4.8`, `4.9`, `4.10`, `5.0`, `5.1`.\n\n## Configuration\n\nelAPI needs to be configured first before you can do anything useful with it. Mainly, elAPI needs to know your eLabFTW\nserver's API URL and your API key (or token) for access. See quick configuration method\nin \"[Getting started](#getting-started)\" before you dive into the advanced settings.\n\n### Advanced configuration\n\nelAPI supports a YAML configuration file in\nthe following locations.\n\n- Current directory: `./elapi.yml`\n- User directory: `$HOME/.config/elapi.yml`\n- Root directory: `/etc/elapi.yml`\n\nelAPI supports configuration overloading. I.e., a keyword set in root configuration file `/etc/elapi.yml` can be\noverridden by setting a different value in user configuration file `$HOME/.config/elapi.yml`. In terms of precedence,\nconfiguration file present in the currently active directory has the highest priority, and configuration in root\ndirectory has the lowest.\n\nThe following parameters are currently configurable, with `host` and `api_token` being the required fields. For testing\npurposes, it would be safe to store everything in `$HOME/.config/elapi.yml`.\n\n```yaml\n# elAPI configuration\n# Saved in `$HOME/.config/elapi.yml`\n\nhost: <host API url>\n# Example: https://demo.elabftw.net/api/v2/\n# Note the host URL ends with the API endpoint\napi_token: <token with at least read-access>\n# \"A.k.a API key\". You can generate an API token from eLabFTW user panel -> API keys tab.\nexport_dir: ~/Downloads/elAPI\nunsafe_api_token_warning: true\nenable_http2: false\nverify_ssl: true\ntimeout: 90\n```\n\n- `export_dir` is where elAPI will export response content to if no path is explicitly provided to `--export/-E`.\n- When `unsafe_api_token_warning` is `True`, elAPI will show a warning if you're storing `elapi.yml` in the current\n working directory, as it typically happens that developers accidentally commit and push configuration files with\n secrets.\n- `enable_http2` enables HTTP/2 protocol support which by default is turned off. Be aware\n of [known issues](https://github.com/encode/httpx/discussions/2112) with HTTP/2 if you are making async requests with\n a heavy load.\n- `verify_ssl` can be turned off with value `False` if you are\n trying out a development server that doesn't provide a valid SSL certificate.\n- `timeout` can be modified to your needs. E.g., a poor internet connection might benefit from a higher timeout number.\n The default timeout is `90` seconds.\n\n### `show-config`\n\nYou can get an overview of detected configuration with `elapi show-config`. `show-config` makes it easier to verify\nwhich configuration values are actually used by elAPI, if you are working with multiple configuration files.\n\n```shell\n$ elapi show-config # system username: \"culdesac\" \n```\n\n\n\nIf both `host` and `api_token` are detected, you are good to go!\n\n### Overriding configuration\n\nelAPI now supports `--override/--OC` as a global option that can be used to override the configuration parameters\nas detected by `elapi show-cofig`. All plugins will also automatically listen to the overridden configuration. This can\nbe useful to set certain configurations temporarily. E.g., `elapi --OC '{\"timeout\": 300\"}' get info` will override\nthe `timeout` from the configuration files.\n\n## Usage\n\nelAPI can be invoked from the command-line.\n\n```shell\n$ elapi --help \n```\n\n### `GET` requests\n\nRequest an overview of running eLabFTW server:\n\n```shell\n$ elapi get info -F yml\n# Here -F (or --format) defines the output format\n```\n\nYou can request a list o all active experiments and export it to a `JSON` file.\n\n```shell\n$ elapi get experiments --export ~/Downoads/experiments.json\n```\n\nEnable built-in syntax highlighting with `--highlight` or `-H`. Here, the following command will fetch team information\nof team with team ID 1.\n\n```shell\n$ elapi get -H teams --id 1\n```\n\n### `POST` requests\n\nCreate a new user by the name 'John Doe':\n\n```shell\n$ elapi post users --id <user id> -d '{\"firstname\": \"John\", \"lastname\": \"Doe\", \"email\": \"test_test@itnerd.de\"}'\n```\n\n### `PATCH` requests\n\nUpdate an existing user's email address:\n\n```shell\n$ elapi patch users --id <user id> -d '{\"email\": \"new_email@itnerd.de\"}'\n```\n\n`patch` command allows us to make changes to eLabFTW server settings. E.g., you can update the time (in minutes)\nafter which the authentication cookie will expire.\n\n```shell\n$ elapi patch config -d '{\"cookie_validity_time\": 43200}'\n```\n\nYou can publish an announcement to all the members.\n\n```shell\n$ elapi patch config -d '{\"announcement\": \"Notice: Server will be down tomorrow at midnight due to scheduled maintenance.\"}'\n```\n\n### `DELETE` requests\n\nDelete all the tags associated to an experiment:\n\n```shell\n$ elapi delete experiments -i <experiment ID> --sub tags\n```\n\nYou can reset the configuration to default values.\n\n```shell\n$ elapi delete config\n```\n\n### `experiments` built-in plugin\n\n`experiments` plugin enables experiments-specific actions. You can download an experiment in PDF by its \"Unique eLabID\"\nto `~/Downloads` directory.\n\n```shell\n$ elapi experiments get -i <experiment unique elabid> -F pdf --export ~/Downloads/\n```\n\nAppend text in markdown to an existing experiment by its ID:\n\n```shell\n$ elapi experiments append --id <experiment ID> -M -t \"**New content.**\"\n```\n\nYou can also upload an attachment to an experiment.\n\n```shell\n$ elapi experiments upload-attachment --id <experiment ID> --path <path to attachment file> --comment <comment for your attachment>\n```\n\n## Creating a plugin\n\nelAPI has seamless support with tight-integration for third-party plugins. A simple third-party plugin can be created in\na few easy steps:\n\n1. Create a new subfolder under `~/.local/share/elapi/plugins` with the name for your new plugin (e.g, a folder named\n \"test\")\n2. Create a `cli.py` in the subfolder with the following snippet:\n\n```python\nfrom elapi.plugins.commons import Typer\n\napp = Typer(name=\"test\", help=\"Test plugin.\")\n\n```\n\n3. Run `elapi` again to see your plugin name under `Third-party plugins` list\n\nPlugins are integrated in a way such that a plugin will **not** fail elAPI. So, even if one erroneous plugin is loaded,\nall\nother plugins and elAPI itself will remain unaffected. elAPI will show the error message on the \"Message\" panel.\n\nIf you try to import a package that is not a dependency of elAPI inside `cli.py`, your plugin will fail. In that case,\nyou want to create a plugin metadata file `elapi_plugin_metadata.yml` (notice only `.yml` extension is allowed), and\ndefine the virtual environment that your plugin specifically requires.\n\n```python\nimport requests # A third-party dependency\n\nfrom elapi.api import GETRequest\nfrom elapi.plugins.commons import Typer\n\n# Plugin metadata\napp = Typer(name=\"awesome\", help=\"An awesome elAPI plugin.\")\n\n\n@app.command(name=\"get-request\", short_help=f\"Make a GET request\")\ndef get_request(endpoint_name):\n r = GETRequest()\n print(r(endpoint_name).json())\n\n\n@app.command(name=\"get-wiki-status\", short_help=f\"Show status of Wikipedia\")\ndef wiki_status():\n r = requests.get(\"https://wikipedia.org\")\n print(r)\n```\n\nAnd the path to virtual environment will be defined in the metadata file:\n\n```yaml\n# elapi_plugin_metadata.yml\nplugin_name: awesome\ncli_script: ~/awesome/cli.py # Path to the cli.py script\nvenv_dir: ~/awesome/.venv # Path to the virtual environment\nproject_dir: ~/awesome # Path to the project root directory where the plugin is located\n```\n\nThis metadata file of plugin `awesome` must be placed inside `~/.local/share/elapi/plugins/awesome`. Notice, the plugin\nname must also match the parent directory name of `elapi_plugin_metadata.yml`. This way we ensure a plugin name remains\nunique.\n",
"bugtrack_url": null,
"license": "AGPL-3.0-only",
"summary": "elAPI is a powerful, extensible API client for eLabFTW.",
"version": "2.2.0",
"project_urls": {
"Homepage": "https://www.urz.uni-heidelberg.de/en/service-catalogue/software-and-applications/elabftw",
"Repository": "https://github.com/uhd-urz/elAPI/"
},
"split_keywords": [
"elabftw",
" api"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "be66e79dc5b99c68d13b1230d86987c26a7f8a3e88bd585359ed9b6347ae7c79",
"md5": "a857e7504a0dcc82fb86fc927bedfb9e",
"sha256": "b66b085c1e7351477b3c64cae264c95fbc0da17cc33501b06124b29e400fe713"
},
"downloads": -1,
"filename": "elapi-2.2.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "a857e7504a0dcc82fb86fc927bedfb9e",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4.0.0,>=3.9.0",
"size": 108193,
"upload_time": "2024-09-04T15:25:44",
"upload_time_iso_8601": "2024-09-04T15:25:44.787180Z",
"url": "https://files.pythonhosted.org/packages/be/66/e79dc5b99c68d13b1230d86987c26a7f8a3e88bd585359ed9b6347ae7c79/elapi-2.2.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "4f53ee69c53839d2e2de0124488322c37b384daba63656aa8c2b27f48ca5ae90",
"md5": "0f57e747cbb5c44b556014b8e5b9d4f7",
"sha256": "396695972713dcc31f429d583082f2f5ba3a826d3ff3a737ae6fce80d00e6d6c"
},
"downloads": -1,
"filename": "elapi-2.2.0.tar.gz",
"has_sig": false,
"md5_digest": "0f57e747cbb5c44b556014b8e5b9d4f7",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4.0.0,>=3.9.0",
"size": 91154,
"upload_time": "2024-09-04T15:25:46",
"upload_time_iso_8601": "2024-09-04T15:25:46.351311Z",
"url": "https://files.pythonhosted.org/packages/4f/53/ee69c53839d2e2de0124488322c37b384daba63656aa8c2b27f48ca5ae90/elapi-2.2.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-09-04 15:25:46",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "uhd-urz",
"github_project": "elAPI",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"lcname": "elapi"
}
JSON
