@kapa.ai I am using the airbyte python SDK to deploy sources to a local airbyte instance. Creating and deleting sources occurs without error, but attempts to update a source using either

put_source

or

patch_source

are met with 405 errors. This is occurring even when the same configurations are used as when using

create_source

. What might be happening to create this error?

A 405 error means “method not allowed” on that endpoint, which points to how the API is exposed in your local deployment rather than to your Python SDK code or the config payload. From the public API reference, both

PUT /sources/{sourceId}

(

putSource

) and

PATCH /sources/{sourceId}

(

patchSource

) are valid methods for updating a source in Airbyte OSS. [[Public API sources](https://reference.airbyte.com/reference/start)] However, the reference also shows these operations as not requiring authentication, which suggests they are part of the “public API” surface and may not be enabled or routed the same way as the endpoints you’re successfully using for

create_source

. [[Public API sources](https://reference.airbyte.com/reference/start)] The knowledge sources do not explicitly describe a 405 scenario for `putSource`/`patchSource`, nor how your specific SDK is configured, so I can’t say exactly which of these is happening, but the most likely causes consistent with the docs are: 1. Different base URL / API surface -

create_source

in your SDK may be calling the “internal” OSS API (Micronaut service) that is always available, while

put_source

/

patch_source

are mapped to the public API routes, which might not be exposed or routed in your local deployment (e.g., via

abctl

or ingress). - If the route is not wired to accept `PUT`/`PATCH`, the server will respond with 405 even though

POST

to

/sources

works. 2. Deployment / gateway not allowing PUT/PATCH - Some ingress or proxy configurations only allow `GET`/`POST` by default. In that case,

create_source

(POST) works, but `PUT`/`PATCH` are blocked at the gateway and return 405 before they reach Airbyte. 3. Using the wrong API flavor - Airbyte also has “embedded” and “integrations” APIs with their own update endpoints (

PUT /api/v1/embedded/sources/:id

,

PUT /api/v1/integrations/sources/:id

, etc.), which return 422/400/403/500 but are documented separately. [[Embedded update source](https://docs.airbyte.com/ai-agents/embedded/api-reference/update-embedded-sources-id); [Integrations update source](https://docs.airbyte.com/ai-agents/embedded/api-reference/update-integrations-sources-id)] - If your SDK is pointed at one of these paths but your local instance doesn’t have that API surface enabled, you could also see method/route errors. Because the docs confirm that

PUT /sources/{sourceId}

and

PATCH /sources/{sourceId}

are valid operations, a 405 almost certainly indicates a routing / deployment / gateway configuration issue, not a problem with the request body. Given the limitations of the knowledge sources, I can’t provide a concrete fix, but based on them you should: - Verify which exact URL your SDK is calling for

put_source

/

patch_source

and that it matches the public API spec (

/sources/{sourceId}

). [[Public API sources](https://reference.airbyte.com/reference/start)] - Check your local deployment (reverse proxy / ingress / gateway) to ensure

PUT

and

PATCH

are allowed and routed to the Airbyte API service. - Confirm you’re not accidentally targeting one of the embedded/integrations APIs that may not be enabled in your local OSS instance.