jilebi-sdk
Programmatic API for jilebi microVMs, routes, SSH keys, nodes and billing.
Authenticate with an API key (X-API-Key header or Authorization: Bearer <key>), or with a browser session cookie. API keys carry scopes — see the POST /api/v1/api-keys endpoint for the full list.
This Python package is automatically generated by the OpenAPI Generator project:
- API version: 1.0.0
- Package version: 0.6.2
- Generator version: 7.26.0
- Build package: org.openapitools.codegen.languages.PythonClientCodegen
Requirements.
Python 3.10+
Packaging uses standard [project] metadata and [dependency-groups] (PEP 621/735).
Install the package with python -m pip install .; install development dependencies
with Poetry 2.2 or newer using poetry install, or pip 25.1 or newer using
python -m pip install --group dev. The latter installs the group, not the package.
Installation & Usage
pip install
If the python package is hosted on a repository, you can install directly using:
pip install git+https://github.com/Datron/jilebi.git
(you may need to run pip with root permission: sudo pip install git+https://github.com/Datron/jilebi.git)
Then import the package:
import jilebi_sdk
Setuptools
Install via Setuptools.
python setup.py install --user
(or sudo python setup.py install to install the package for all users)
Then import the package:
import jilebi_sdk
Tests
Execute pytest to run the tests.
Getting Started
Please follow the installation procedure and then run the following:
import jilebi_sdk
from jilebi_sdk.rest import ApiException
from pprint import pprint
# Defining the host is optional and defaults to https://jilebi.ai
# See configuration.py for a list of all supported configuration parameters.
configuration = jilebi_sdk.Configuration(
host = "https://jilebi.ai"
)
# The client must configure the authentication and authorization parameters
# in accordance with the API server security policy.
# Examples for each auth method are provided below, use the example that
# satisfies your auth use case.
# Configure API key authorization: apiKey
configuration.api_key['apiKey'] = os.environ["API_KEY"]
# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
# configuration.api_key_prefix['apiKey'] = 'Bearer'
# Configure API key authorization: sessionCookie
configuration.api_key['sessionCookie'] = os.environ["API_KEY"]
# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed
# configuration.api_key_prefix['sessionCookie'] = 'Bearer'
# Configure Bearer authorization (API key): bearerAuth
configuration = jilebi_sdk.Configuration(
access_token = os.environ["BEARER_TOKEN"]
)
# Enter a context with an instance of the API client
with jilebi_sdk.ApiClient(configuration) as api_client:
# Create an instance of the API class
api_instance = jilebi_sdk.APIKeysApi(api_client)
id = 'id_example' # str | Id of the API key.
try:
# Revoke an API key
api_response = api_instance.delete_api_v1_api_keys_by_id(id)
print("The response of APIKeysApi->delete_api_v1_api_keys_by_id:\n")
pprint(api_response)
except ApiException as e:
print("Exception when calling APIKeysApi->delete_api_v1_api_keys_by_id: %s\n" % e)
Documentation for API Endpoints
All URIs are relative to https://jilebi.ai
| Class | Method | HTTP request | Description |
|---|---|---|---|
| APIKeysApi | delete_api_v1_api_keys_by_id | DELETE /api/v1/api-keys/{id} | Revoke an API key |
| APIKeysApi | get_api_v1_api_keys | GET /api/v1/api-keys | List API keys |
| APIKeysApi | post_api_v1_api_keys | POST /api/v1/api-keys | Create an API key |
| AccountApi | get_api_me | GET /api/me | Get the current user and session |
| BillingApi | get_api_v1_billing_admin_users | GET /api/v1/billing/admin/users | List billable users |
| BillingApi | post_api_v1_billing_admin_generate_by_username | POST /api/v1/billing/admin/generate/{username} | Generate an invoice |
| BillingApi | post_api_v1_billing_admin_reset_dodo_by_username | POST /api/v1/billing/admin/reset-dodo/{username} | Reset a user's Dodo data |
| BillingApi | post_api_v1_billing_pay_by_bill_id | POST /api/v1/billing/pay/{billId} | Pay an invoice |
| MicroVMsApi | delete_api_v1_vmm_by_machine_name | DELETE /api/v1/vmm/{machine_name} | Delete a microVM |
| MicroVMsApi | get_api_v1_vmm | GET /api/v1/vmm | List microVMs |
| MicroVMsApi | get_api_v1_vmm_by_machine_name | GET /api/v1/vmm/{machine_name} | Get a microVM |
| MicroVMsApi | post_api_v1_vmm_by_machine_name | POST /api/v1/vmm/{machine_name} | Create a microVM |
| MicroVMsApi | post_api_v1_vmm_by_machine_name_clone | POST /api/v1/vmm/{machine_name}/clone | Clone a microVM |
| MicroVMsApi | put_api_v1_vmm_by_machine_name | PUT /api/v1/vmm/{machine_name} | Resize a microVM |
| MicroVMsApi | put_api_v1_vmm_by_machine_name_pause | PUT /api/v1/vmm/{machine_name}/pause | Pause a microVM |
| MicroVMsApi | put_api_v1_vmm_by_machine_name_restart | PUT /api/v1/vmm/{machine_name}/restart | Restart a microVM |
| MicroVMsApi | put_api_v1_vmm_by_machine_name_restore | PUT /api/v1/vmm/{machine_name}/restore | Restore a microVM from a snapshot |
| MicroVMsApi | put_api_v1_vmm_by_machine_name_shutdown | PUT /api/v1/vmm/{machine_name}/shutdown | Shut down a microVM |
| MicroVMsApi | put_api_v1_vmm_by_machine_name_snapshot | PUT /api/v1/vmm/{machine_name}/snapshot | Snapshot a microVM |
| MicroVMsApi | put_api_v1_vmm_by_machine_name_start | PUT /api/v1/vmm/{machine_name}/start | Start a microVM |
| NodesApi | delete_api_v1_nodes_by_name | DELETE /api/v1/nodes/{name} | Delete a node |
| NodesApi | get_api_v1_nodes | GET /api/v1/nodes | List nodes |
| NodesApi | get_api_v1_nodes_by_name | GET /api/v1/nodes/{name} | Get a node |
| NodesApi | post_api_v1_nodes | POST /api/v1/nodes | Register a node |
| NodesApi | post_api_v1_nodes_by_name_health | POST /api/v1/nodes/{name}/health | Check node health |
| NodesApi | post_api_v1_nodes_by_name_refresh | POST /api/v1/nodes/{name}/refresh | Refresh node resources |
| NodesApi | post_api_v1_nodes_by_name_reinitialize | POST /api/v1/nodes/{name}/reinitialize | Reinitialize a node |
| NodesApi | put_api_v1_nodes_by_name | PUT /api/v1/nodes/{name} | Update a node |
| RoutesApi | delete_api_v1_routes_by_name | DELETE /api/v1/routes/{name} | Delete a route |
| RoutesApi | get_api_v1_routes | GET /api/v1/routes | List routes |
| RoutesApi | post_api_v1_routes | POST /api/v1/routes | Create a route |
| RoutesApi | put_api_v1_routes_by_name | PUT /api/v1/routes/{name} | Update a route |
| SSHKeysApi | delete_api_v1_keys_by_id | DELETE /api/v1/keys/{id} | Delete an SSH key |
| SSHKeysApi | get_api_v1_keys | GET /api/v1/keys | List SSH keys |
| SSHKeysApi | post_api_v1_keys | POST /api/v1/keys | Add an SSH key |
| SSHKeysApi | put_api_v1_keys_by_id | PUT /api/v1/keys/{id} | Rename an SSH key |
| SoftwareCatalogApi | delete_api_v1_software_by_id | DELETE /api/v1/software/{id} | Delete software |
| SoftwareCatalogApi | get_api_v1_software | GET /api/v1/software | List software |
| SoftwareCatalogApi | get_api_v1_software_by_id | GET /api/v1/software/{id} | Get software |
| SoftwareCatalogApi | post_api_v1_software | POST /api/v1/software | Add software |
| SoftwareCatalogApi | put_api_v1_software_by_id | PUT /api/v1/software/{id} | Update software |
Documentation For Models
- ApiBillingGenerateResponse
- ApiBillingGenerateResponseBillsInner
- ApiBillingResetDodoResponse
- ApiBillingUser
- ApiBillingUsersResponse
- ApiError
- ApiKey
- ApiKeyCreateRequest
- ApiKeyCreateRequestExpiresIn
- ApiKeyCreateResponse
- ApiMeResponse
- ApiNode
- ApiNodeCreateRequest
- ApiNodeHealthResponse
- ApiNodeRefreshResponse
- ApiNodeReinitializeResponse
- ApiNodeStatus
- ApiNodeUpdateRequest
- ApiRoute
- ApiRouteCreateRequest
- ApiRouteCreateResponse
- ApiRouteListResponse
- ApiRouteUpdateRequest
- ApiSoftware
- ApiSoftwareCreateRequest
- ApiSoftwareUpdateRequest
- ApiSshKey
- ApiSshKeyCreateRequest
- ApiSshKeyCreateResponse
- ApiSshKeyUpdateRequest
- ApiSuccess
- ApiVm
- ApiVmCloneRequest
- ApiVmCloneResponse
- ApiVmCreateRequest
- ApiVmCreateResponse
- ApiVmGetResponse
- ApiVmRestoreRequest
- ApiVmRestoreResponse
- ApiVmSnapshotRequest
- ApiVmSnapshotResponse
- ApiVmState
- ApiVmUpdateRequest
- DeviceNode
- ProvisionedVm
- SharedUser
- VmInfo
Documentation For Authorization
Authentication schemes defined for the API:
apiKey
- Type: API key
- API key parameter name: X-API-Key
- Location: HTTP header
bearerAuth
- Type: Bearer authentication (API key)
sessionCookie
- Type: API key
- API key parameter name: better-auth.session_token
- Location:
Author
Metadata
Release files for jilebi-sdk 0.6.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 | Actions |
|---|---|---|---|---|
| jilebi_sdk-0.6.2.tar.gz | 62.6 kB | With provenance | Details for jilebi_sdk-0.6.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jilebi_sdk-0.6.2-py3-none-any.whl | Python 3 | none | any | Details for jilebi_sdk-0.6.2-py3-none-any.whl |
Total release size: 185.8 kB
Release files / jilebi_sdk-0.6.2.tar.gz
| Download URL | jilebi_sdk-0.6.2.tar.gz |
|---|---|
| Size | 62.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86c44be6b69acc462ddbf94a65f4b5ae75073606ff1fe4d8790c8b34cb9e13c3
|
|
BLAKE2b-256 checksum How to use checksums |
24386b28ecd28bc817576905e67e1dcde90f76adae8f2c7dec2e5b78a4256e56
|
| 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 20, 2026.
Transparency logRelease files / jilebi_sdk-0.6.2-py3-none-any.whl
| Download URL | jilebi_sdk-0.6.2-py3-none-any.whl |
|---|---|
| Size | 123.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebb4446c2f0a267ba63861c601433d6d057a790f759548761d2899f25757630f
|
|
BLAKE2b-256 checksum How to use checksums |
548959c6dc74795b0c743deca3f6ba3494485f074abe0d784a3bc4deed8e19a5
|
| 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 20, 2026.
Transparency logSecurity for jilebi-sdk 0.6.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for jilebi_sdk-0.6.2.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 20, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.