⚠️ Airbyte API Integration Update (future breaking change notice) (Standalone Server Deprecation and Migration to Airbyte Server) > We’re deprecating the standalone Airbyte API server and moving the routes into the Airbyte server. This will allow us to increase reliability (no more cross server HTTP calls) as well as decrease Airbyte’s deployment footprint. You should now be able to access the Airbyte API directly from the Airbyte server and all Airbyte API updates going forward will be made to that version of the API. Please review the documentation page for information on how to swap over to the new URLs by the target deprecation date. The

server

service will be deprecated on June 14. You can access the new endpoints (

airbyte-server

) now to update your applications and ensure seamless integration with future releases. For detailed instructions and more information, please click here.

@Marcos Marx (Airbyte) the documentation doesn't mention the minimum version that supports this. Can a note be added? I appreciate the cutover window, but it's hard to take advantage of if we don't know when it started!

@Jon Tan (Airbyte) do you have this information? 🙏

Is there any information about how this will affect usage of Airflow operators? I believe the existing ones use the soon-to-be-deprecated config API - are there alternatives for orchestrating OSS Airbyte syncs in Airflow using the new API?

Added a note about the minimum version - thanks for the feedback @Adam Bloom!

Thanks for the response! I think I'm a bit confused about the impact of the change. The deprecation notice suggests that our OSS deployment will need to be tweaked to update the API where it is making requests. But are you saying that no changes need to be made for Airflow orchestration to work?

There were two server containers running previously - the

airbyte-server

where the config API lives, and the

airbyte-api-server

where the Airbyte API (public API) lives. The

airbyte-server

is remaining and the

airbyte-api-server

is going away. If you were using the Airbyte API, you will have to update callers to point to

airbyte-server/api/public

as the base URL. Anything already pointing to the

airbyte-server

needs no change which seems to be what you’re describing with the Airflow operators.

Hi, I’ve upgraded to

0.59.0

(which according to the doc seems like it should support the new way of using the api) but am not getting the results I expect Deployed locally with

run-ab-platform.sh

curl -v -u airbyte:password <http://127.0.0.1:8001/api/public/health>
*   Trying 127.0.0.1:8001...
* Connected to 127.0.0.1 (127.0.0.1) port 8001
* Server auth using Basic with user 'airbyte'
> GET /api/public/health HTTP/1.1
> Host: 127.0.0.1:8001
> Authorization: Basic YWlyYnl0ZTpwYXNzd29yZA==
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Server: nginx/1.25.3
< Date: Thu, 09 May 2024 09:15:37 GMT
< Content-Type: application/json
< Content-Length: 17
< Connection: keep-alive
<
* Connection #0 to host 127.0.0.1 left intact
Object not found.%

Running the old health checkpoint gives the expected 200:

curl -u airbyte:password -v <http://localhost:8006/health>
*   Trying [::1]:8006...
* Connected to localhost (::1) port 8006
* Server auth using Basic with user 'airbyte'
> GET /health HTTP/1.1
> Host: localhost:8006
> Authorization: Basic YWlyYnl0ZTpwYXNzd29yZA==
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.25.3
< Date: Thu, 09 May 2024 09:17:47 GMT
< Content-Type: application/json
< Content-Length: 20
< Connection: keep-alive
<
* Connection #0 to host localhost left intact
Successful operation%

Hi @Jon Tan (Airbyte), I'm in the same boat as @Matthew Martin! And I can't get the new API to work using v59. I'd appreciate any clarification or a working example.

I have eyes on this, just want to let you know that I will add an update by Monday EOD.

Hi @Jon Tan (Airbyte), I have upgraded to version 0.62.1 and I still have the same issue. This is my curl command.

curl -v -u airbyte:password <http://127.0.0.1:8000/api/public/health>

When you say > I’ve updated the docs to reflect that the earliest version to switch is v0.59.1 Where is this change reflected? Is this here?

New page: https://reference.airbyte.com/reference/standalone-server-deprecation-and-migration-to-airbyte-server

hi, thank you for sharing 🙂 all the links in this thread are broken for me.. do they work for anyone else?

It appears that our docs are down - I’m looking into it now.

the link Marcos posted works for me now, thank you!