Is an easy way to setup mechanism calls for Django projects. For the exchange of data is used JSON. The API is built on the RPC scheme: one URL address - many methods. This scheme allows you to share hard-structured data, such as nested into each other JavaScript objects:
$.quickAPI({
url: "/api/",
data: {
method: "settings.update",
kwargs: { value: {
suppliers: ['s1', 's2', 's33'],
skip_goods: {
s1: ['g123', 'g321'],
s33: ['g098']
}
}
}
},
callback: function(json, status, xhr) {},
})from quickapi.client import BaseClient
api = BaseClient()
api.url = 'https://example.org/api/'
api.username = 'login'
api.password = 'passw'
settings = {
'suppliers': ['s1', 's2', 's33'],
'skip_goods': {
's1': ['g123', 'g321'],
's33': ['g098']
}
}
response = api.method('settings.update', value=settings)Read the documentation for details.
1 maintainer
Metadata
1 maintainer
Release files for django-quickapi 3.7.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 | |
|---|---|---|---|---|
| django-quickapi-3.7.2.tar.gz | 995.6 kB | Without provenance | Details |
Release files / django-quickapi-3.7.2.tar.gz
| Download URL | django-quickapi-3.7.2.tar.gz |
|---|---|
| Size | 995.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3fa22ba6c1359eb97185c74e0f4a4c42e3ee5d5c6d7b53f39298110f446df429
|
|
BLAKE2b-256 checksum How to use checksums |
2336027faca28db40c27179a671331e2abca853b2084a791fd229693db9a972e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-quickapi 3.7.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.
