SkyscannerB2B Python SDK 1.0.0
Welcome to the SkyscannerB2b SDK documentation. This guide will help you get started with integrating and using the SkyscannerB2b SDK in your project.
Versions
- API version:
1.0.0 - SDK version:
1.0.0
About the API
Our Travel APIs are provided to connect partners like yourself to all the data you need to build an innovative website or app using our Skyscanner travel content. We’ve made it easier than ever to develop your website using flexible price search options so you can build exciting tools that will expand your travel search options for your users.
Table of Contents
Setup & Configuration
Supported Language Versions
This SDK is compatible with the following versions: Python >= 3.7
Installation
To get started with the SDK, we recommend installing using pip:
pip install skyscanner-b2b
Authentication
API Key Authentication
The SkyscannerB2b API uses API keys as a form of authentication. An API key is a unique identifier used to authenticate a user, developer, or a program that is calling the API.
Setting the API key
When you initialize the SDK, you can set the API key as follows:
SkyscannerB2b(
api_key="YOUR_API_KEY",
api_key_header="YOUR_API_KEY_HEADER"
)
If you need to set or update the API key after initializing the SDK, you can use:
sdk.set_api_key("YOUR_API_KEY", "YOUR_API_KEY_HEADER")
Services
The SDK provides various services to interact with the API.
Below is a list of all available services with links to their detailed documentation:
| Name |
|---|
| FlightsLivePricesService |
| FlightsIndicativePricesService |
| CultureService |
| GeoService |
| AutosuggestService |
| CarriersService |
Models
The SDK includes several models that represent the data structures used in API requests and responses. These models help in organizing and managing the data efficiently.
Below is a list of all available models with links to their detailed documentation:
License
This SDK is licensed under the MIT License.
See the LICENSE file for more details.
1 maintainer
Metadata
1 maintainer
Release files for skyscanner-b2b 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 | Actions |
|---|---|---|---|---|
| skyscanner-b2b-1.0.0.tar.gz | 19.3 kB | Without provenance | Details for skyscanner-b2b-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| skyscanner_b2b-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for skyscanner_b2b-1.0.0-py3-none-any.whl |
Total release size: 53.6 kB
Release files / skyscanner-b2b-1.0.0.tar.gz
| Download URL | skyscanner-b2b-1.0.0.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e78f8dda5b0a756974acc450755b758241ea1fe35e14cec3e7bc13ffbce306e
|
|
BLAKE2b-256 checksum How to use checksums |
e0146169789dbaae9e6101d6413d8882ae580857e28b70e83061993c12ba6da1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.17
|
Release files / skyscanner_b2b-1.0.0-py3-none-any.whl
| Download URL | skyscanner_b2b-1.0.0-py3-none-any.whl |
|---|---|
| Size | 34.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74b602122552feda649c2004b6aa751da92af7b613ede1069a6101e0e9b4e93b
|
|
BLAKE2b-256 checksum How to use checksums |
0e5757cafca77d1f56cdad6fd184567bf751c509646558db31f6235fef0b0a4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.17
|
Security for skyscanner-b2b 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.
