Getting Started with Swagger Petstore
Introduction
This is a sample server Petstore server. You can find out more about Swagger at http://swagger.io or on irc.freenode.net, #swagger. For this sample, you can use the api key special-key to test the authorization filters.
Find out more about Swagger: http://swagger.io
Install the Package
The package is compatible with Python versions 3 >=3.7, <= 3.9.
Install the package from PyPi using the following pip command:
pip install petstore-test==1.0.0
You can also view the package at: https://pypi.python.org/pypi/petstore-test
Initialize the API Client
Note: Documentation for the client can be found here.
The following parameters are configurable for the API Client:
| Parameter | Type | Description |
|---|---|---|
environment |
Environment | The API environment. Default: Environment.PRODUCTION |
http_client_instance |
HttpClient |
The Http Client passed from the sdk user for making requests |
override_http_client_configuration |
bool |
The value which determines to override properties of the passed Http Client from the sdk user |
http_call_back |
HttpCallBack |
The callback value that is invoked before and after an HTTP call is made to an endpoint |
timeout |
float |
The value to use for connection timeout. Default: 60 |
max_retries |
int |
The number of times to retry an endpoint call if it fails. Default: 0 |
backoff_factor |
float |
A backoff factor to apply between attempts after the second try. Default: 2 |
retry_statuses |
Array of int |
The http statuses on which retry is to be done. Default: [408, 413, 429, 500, 502, 503, 504, 521, 522, 524] |
retry_methods |
Array of string |
The http methods on which retry is to be done. Default: ['GET', 'PUT'] |
custom_header_api_key |
string |
|
o_auth_client_id |
string |
OAuth 2 Client ID |
o_auth_redirect_uri |
string |
OAuth 2 Redirection endpoint or Callback Uri |
o_auth_token |
OAuthToken |
Object for storing information about the OAuth token |
o_auth_scopes |
OAuthScopeEnum |
The API client can be initialized as follows:
from swaggerpetstore.swaggerpetstore_client import SwaggerpetstoreClient
from swaggerpetstore.configuration import Environment
client = SwaggerpetstoreClient(
custom_header_api_key='CustomHeaderApiKey',
o_auth_client_id='OAuthClientId',
o_auth_redirect_uri='OAuthRedirectUri',
o_auth_scopes = [OAuthScopeEnum.READPETS, OAuthScopeEnum.WRITEPETS],
environment=Environment.PRODUCTION,)
Authorization
This API uses Custom Header Signature, OAuth 2 Implicit Grant.
Implicit Grant
Your application must obtain user authorization before it can execute an endpoint call incase this SDK chooses to use OAuth 2.0 Implicit Grant to obtain a user's consent to perform an API request on user's behalf. This authorization includes the following steps
This process requires the presence of a client-side JavaScript code on the redirect URI page to receive the access token after the consent step is completed.
1. Obtain user consent
To obtain user's consent, you must redirect the user to the authorization page. The get_authorization_url() method creates the URL to the authorization page. You must pass the scopes for which you need permission to access.
auth_url = client.auth_managers['petstoreAuth'].get_authorization_url()
2. Handle the OAuth server response
Once the user responds to the consent request, the OAuth 2.0 server responds to your application's access request by redirecting the user to the redirect URI specified set in Configuration.
The redirect URI will receive the access token as the token argument in the URL fragment.
https://example.com/oauth/callback#token=XXXXXXXXXXXXXXXXXXXXXXXXX
The access token must be extracted by the client-side JavaScript code. The access token can be used to authorize any further endpoint calls by the JavaScript code.
Scopes
Scopes enable your application to only request access to the resources it needs while enabling users to control the amount of access they grant to your application. Available scopes are defined in the OAuthScopeEnum enumeration.
| Scope Name | Description |
|---|---|
READPETS |
read your pets |
WRITEPETS |
modify pets in your account |
List of APIs
Classes Documentation
Metadata
Release files for petstore-test 1.0.0
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 | |
|---|---|---|---|---|
| petstore-test-1.0.0.tar.gz | 23.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| petstore_test-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 63.7 kB
Release files / petstore-test-1.0.0.tar.gz
| Download URL | petstore-test-1.0.0.tar.gz |
|---|---|
| Size | 23.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbdb157cbb4c596c2b5a41f673734c0bba0c9a56e4c378607931b1bc197bba4e
|
|
BLAKE2b-256 checksum How to use checksums |
b9bb99cb893fd2c556780858fc3d287970a7f26b9f2070d7abfb95146179c2e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.34.0 CPython/3.6.8
|
Release files / petstore_test-1.0.0-py3-none-any.whl
| Download URL | petstore_test-1.0.0-py3-none-any.whl |
|---|---|
| Size | 39.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8661aa157443d50e1d5190e3b7d259bb9b8711cc4ab5583e394c75adfc0197d7
|
|
BLAKE2b-256 checksum How to use checksums |
b96e4ccc9bad401b8bcb721962005654f0c5282cc081bc1c1dee6df9803c7878
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.34.0 CPython/3.6.8
|
Security for petstore-test 1.0.0
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.