allegro-api
pyAllegro is a framework, that provides a simple way to use Allegro Web API and Rest AP. You don't need to know how RESTful, SOAP or oauth 2.0 works.
As for now it's prepared for getting data from allegro - not for managing your account or bidding.
Get started:
- Go to https://apps.developer.allegro.pl/ and register your app. You need to setup redirecion url to
http://localhost:8000- it will be your local server that recive your autorization data (oauth 2.0), - Generate your app password here,
- Install pyAllegro with
pip install pyAllegro - Import
from pyAllegro.api import AllegroRestApi, AllegroWebApi - Setup credentials that you recived from allegro (by default it's saved here: '/Users/{user}/.allegroApiConfig'):
WebApi = AllegroWebApi()
WebApi.credentials_set(
appName='<credentials from allegro>',
clientId='<credentials from allegro>',
clientSecred='<credentials from allegro>',
userLogin='<allegro login>',
redirectUrl='<redirect uri - the same you provided during app registration on allegro >',
appPassword='<app password>'
)
RestApi = AllegroRestApi()
RestApi.credentials_set(
appName='<credentials from allegro>',
clientId='<credentials from allegro>',
clientSecred='<credentials from allegro>',
redirectUrl='http://localhost:8000'
)
How to use pyAllegro:
Allegro api documentation:
References
Thanks to:
- https://cwsi.pl/ecommerce/allegro/podstawy-obslugi-web-api-allegro-pl-web-services-i-modul-suds-jurko-w-pythonie
- https://cwsi.pl/ecommerce/allegro/allegro-pl-rest-api-w-pythonie-wprowadzenie/
To do
- publish package on pypi
- RestApi put
- RestApi delete
- restApi post
Changelog
ver. 0.1.0:
- automatic token refreshing
ver. 0.1.1, 0.2.0:
- load token automatically in
RestApi.resource_get()method
ver. 0.3.0:
- added
response2JSON()function in WebApi - convert suds response to JSON.
Metadata
Release files for pyAllegro 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyAllegro-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for pyAllegro-0.3.1-py3-none-any.whl |
Release files / pyAllegro-0.3.1-py3-none-any.whl
| Download URL | pyAllegro-0.3.1-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c23a2ea6853302a16383229e9bded01c469315685e3f1affc788f7a8d0f59d70
|
|
BLAKE2b-256 checksum How to use checksums |
36c4a58c543a525d613c9589187f5d7df5712b72e4c930a11234976c2492f4e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.1.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.6.4
|
Security for pyAllegro 0.3.1
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.