Changes in Airbyte API endpoint

Summary

The user is inquiring about changes in the Airbyte API endpoint, noticing discrepancies in the documentation regarding the API connection URL. They have observed that the API still appears to be at port 8006 despite the documentation mentioning a different port. The user wants to confirm if there is a need to change API endpoints/configuration for their EC2 deployment if they upgrade.


Question

Hello Airbyte Team

Has the way to work with the Airbyte API on OSS changed?

https://reference.airbyte.com/reference/start|This page now mentions connecting via <http://localhost:8001/api/public/v1/><endpoint> , however, a couple of days ago it said to use <http://localhost:8006> (wayback machine <https://web.archive.org/web/20240329105718/https://reference.airbyte.com/reference/start|confirms this> as of last month, however i was looking at this doc yesterday and it still said :8006)

I’ve cleared out everything locally and reinstalled using ./run-ab-platform.sh and confirm that the api still appears to be at 8006 :

*   Trying 127.0.0.1:8006...
* Connected to 127.0.0.1 (127.0.0.1) port 8006
* Server auth using Basic with user 'airbyte'
> GET /health HTTP/1.1
> Host: 127.0.0.1:8006
> Authorization: Basic YWlyYnl0ZTpwYXNzd29yZA==
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.25.3
< Date: Thu, 25 Apr 2024 12:10:01 GMT
< Content-Type: application/json
< Content-Length: 20
< Connection: keep-alive
<
* Connection #0 to host 127.0.0.1 left intact
Successful operation%
❯ curl -v -u airbyte:password 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, 25 Apr 2024 12:10:14 GMT
< Content-Type: application/json
< Content-Length: 17
< Connection: keep-alive
<
* Connection #0 to host 127.0.0.1 left intact
Object not found.%```
I just want to confirm if we need to change api endpoints/configuration for our ec2 deployment if we upgrade (currently on `0.57.3`). We are newly trialing using Airbyte so don’t want to configure something that has already changed.

TIA :pray:

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1714047538909069) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte-api", "documentation", "endpoint-change", "ec2-deployment", "upgrade"]
</sub>