@kapa.ai , what is the sync api endpoint to fetch the latest sync_id , currently using /jobs/list

To fetch the latest sync job information (including the job ID), you can use the Airbyte Public API's

GET /jobs

endpoint with filtering by

connectionId

. This will return a list of jobs, and you can sort/limit to get the latest one. Endpoint:

GET https://api.airbyte.com/v1/jobs

Key query parameters: Example cURL:

curl -X GET "https://api.airbyte.com/v1/jobs?connectionId=<your-connection-id>&jobType=sync&limit=1" \
  -H "accept: application/json" \
  -H "Authorization: Bearer {YourApiKey}"

This returns a response with job details including

jobId

,

status

,

startTime

,

rowsSynced

,

bytesSynced

, and

duration

. [listJobs API] Once you have the

jobId

, you can also fetch details for a specific job using:

GET https://api.airbyte.com/v1/jobs/{jobId}

[getJob API] > Note: The

configId

used in the older internal

/api/v1/jobs/list

endpoint is equivalent to the

connectionId

. The public API (

/v1/jobs

) is the recommended approach. [sync history forum] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

jobs/list endpoint gives me records emitted per stream to know which stream changed how to limit that @kapa.ai

Based on the knowledge sources available, I don't have enough information to provide a confident answer about limiting records emitted per stream from the

/jobs/list

endpoint, or filtering sync results by specific streams. What the Airbyte Public API's

GET /jobs

endpoint does support for filtering/limiting is: •

connectionId

– filter by connection •

jobType

– filter by

sync

or

reset

•

status

– filter by job status •

limit

/

offset

– paginate results •

createdAtStart

/

createdAtEnd

– filter by date range •

orderBy

– sort results [listJobs API] However, the knowledge sources do not mention a way to filter or limit results at the stream level within the jobs API response. Stream-level metrics (records emitted per stream) are not described as filterable parameters in the available documentation. For this use case, I'd suggest: 1. Checking the Airbyte API reference directly for any stream-level filtering options not covered here. 2. Posting your question on the Airbyte community forum or Slack, where the team or community members may have a workaround. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.