airbyte-api-python-sdk
airbyte-api-python-sdk copied to clipboard
airbytehq
With our library of 300+ sources and 60+ destinations, certain API endpoints should return a "configuration" that is typed to the correct source or destination class, but they don't properly...
When calling directly the API ```bash curl --request GET \ --url 'https://api.airbyte.com/v1/streams?sourceId=03604837-98e**********8b8c7e4a&destinationId=d89fd9a*********6d6-85c8-ddc30e7a85ec' \ --header 'accept: application/json' \ --header 'authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cC **************FnxpQVDlmiwxee0PpoSQ' ``` it nicely returns sync_modes info: ```json [...
> [!IMPORTANT] > Linting report available at: > OpenAPI Change report available at: # SDK update ## Versioning Version Bump Type: [patch] - 🤖 (automated) ## OpenAPI Change Summary ```...
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot] avatar"){kind=avatar}
The use of urljoin on the do_token_request was creating a bug for the base configuration. When the self.base_url was the default "https://api.airbyte.com/v1" and credentials was the default "/applications/token", it did...
Hi team, I'm using the SDK and got this error why trying to init Airbyte Client using SchemeBasicAuth: ``` DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): airbyte.staging.data-engineering.myteksi.net:443 send: b'GET /api/v1/health HTTP/1.1\r\nHost: \r\nuser-agent:...
Proper headed Content-Type with value `application/json` was added to the token requests
[Speakeasy says](https://www.speakeasy.com/docs/languages/python/methodology-python#async-vs-sync-methods), they are using httpx to provide both async and non async client, how does one use airbyte-api-python-sdk in Async?
Every request to the Airbyte for token generation fails with 401 error code. It happens because airbyte is waiting for requests with content-type `application/json` but the library sends default header.