Skip to content

Airbyte Configuration API API

by airbyte.local

Bearer tokenHTTPSDevelopment
Open documentation ↗

Overview

Airbyte Configuration API [https://airbyte.io](https://airbyte.io). This API is a collection of HTTP RPC-style methods. While it is not a REST API, those familiar with REST should find the conventions of this API recognizable. Here are some conventions that this API follows: * All endpoints are http POST methods. * All endpoints accept data via `application/json` request bodies. The API does not accept any data via query params. * The naming convention for endpoints is: localhost:8000/{VERSION}/{METHOD_FAMILY}/{METHOD_NAME} e.g. `localhost:8000/v1/connections/create`. * For all `update` methods, the whole object must be passed in, even the fields that did not change. Authentication (OSS): * When authenticating to the Configuration API, you must use Basic Authentication by setting the Authentication Header to Basic and base64 encoding the username and password (which are `airbyte` and `password` by default - so base64 encoding `airbyte:password` results in `YWlyYnl0ZTpwYXNzd29yZA==`). So the full header reads `'Authorization': "Basic YWlyYnl0ZTpwYXNzd29yZA=="`

Airbyte Configuration API is a development API from airbyte.local. Requests are authenticated with a bearer token. It is served over HTTPS. Its OpenAPI description documents 102 endpoints.

At a glance

Authentication
Bearer token
HTTPS
Yes
CORS
Unknown
Category
Development
Base URL
http://airbyte.local
Version
1.0.0
Endpoints
102
Spec updated
2023-03-06

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "http://airbyte.local/v1/health" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN"
JavaScript
const response = await fetch("http://airbyte.local/v1/health", {
  method: "GET",
  headers: {
    "Accept": "application/json",
    "Authorization": "Bearer YOUR_TOKEN",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "http://airbyte.local/v1/health",
    headers={
    "Accept": "application/json",
    "Authorization": "Bearer YOUR_TOKEN",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
POST/v1/attempt/save_statsFor worker to set sync stats of a running attempt.
POST/v1/attempt/save_sync_configFor worker to save the AttemptSyncConfig for an attempt.
POST/v1/attempt/set_workflow_in_attemptFor worker to register the workflow id in attempt.
POST/v1/connections/createCreate a connection between a source and a destination
POST/v1/connections/deleteDelete a connection
POST/v1/connections/getGet a connection
POST/v1/connections/listReturns all connections for a workspace.
POST/v1/connections/list_allReturns all connections for a workspace, including deleted connections.
POST/v1/connections/resetReset the data for the connection. Deletes data generated by the connection in the destination. Resets any cursors back to initial state.
POST/v1/connections/searchSearch connections
POST/v1/connections/syncTrigger a manual sync of the connection
POST/v1/connections/updateUpdate a connection
POST/v1/destination_definition_specifications/getGet specification for a destinationDefinition
POST/v1/destination_definitions/create_customCreates a custom destinationDefinition for the given workspace
POST/v1/destination_definitions/deleteDelete a destination definition
POST/v1/destination_definitions/getGet destinationDefinition
POST/v1/destination_definitions/get_for_workspaceGet a destinationDefinition that is configured for the given workspace
POST/v1/destination_definitions/grant_definitiongrant a private, non-custom destinationDefinition to a given workspace
POST/v1/destination_definitions/listList all the destinationDefinitions the current Airbyte deployment is configured to use
POST/v1/destination_definitions/list_for_workspaceList all the destinationDefinitions the given workspace is configured to use
POST/v1/destination_definitions/list_latestList the latest destinationDefinitions Airbyte supports
POST/v1/destination_definitions/list_privateList all private, non-custom destinationDefinitions, and for each indicate whether the given workspace has a grant for using the definition. Used by admins to v
POST/v1/destination_definitions/revoke_definitionrevoke a grant to a private, non-custom destinationDefinition from a given workspace
POST/v1/destination_definitions/updateUpdate destinationDefinition
POST/v1/destination_oauths/complete_oauthGiven a destination def ID generate an access/refresh token etc.
POST/v1/destination_oauths/get_consent_urlGiven a destination connector definition ID, return the URL to the consent screen where to redirect the user to.
POST/v1/destination_oauths/oauth_params/createSets instancewide variables to be used for the oauth flow when creating this destination. When set, these variables will be injected into a connector's configur
POST/v1/destinations/check_connectionCheck connection to the destination
POST/v1/destinations/check_connection_for_updateCheck connection for a proposed update to a destination
POST/v1/destinations/cloneClone destination
POST/v1/destinations/createCreate a destination
POST/v1/destinations/deleteDelete the destination
POST/v1/destinations/getGet configured destination
POST/v1/destinations/listList configured destinations for a workspace
POST/v1/destinations/searchSearch destinations
POST/v1/destinations/updateUpdate a destination
GET/v1/healthHealth Check
POST/v1/jobs/cancelCancels a job
POST/v1/jobs/getGet information about a job
POST/v1/jobs/get_debug_infoGets all information needed to debug this job
POST/v1/jobs/get_last_replication_jobgetLastReplicationJob
POST/v1/jobs/get_lightGet information about a job excluding attempt info and logs
POST/v1/jobs/get_normalization_statusGet normalization status to determine if we can bypass normalization phase
POST/v1/jobs/listReturns recent jobs for a connection. Jobs are returned in descending order by createdAt.
POST/v1/logs/getGet logs
POST/v1/notifications/tryTry sending a notifications
GET/v1/openapiReturns the openapi specification
POST/v1/operations/checkCheck if an operation to be created is valid
POST/v1/operations/createCreate an operation to be applied as part of a connection pipeline
POST/v1/operations/deleteDelete an operation
POST/v1/operations/getReturns an operation
POST/v1/operations/listReturns all operations for a connection.
POST/v1/operations/updateUpdate an operation
POST/v1/scheduler/destinations/check_connectionRun check connection for a given destination configuration
POST/v1/scheduler/sources/check_connectionRun check connection for a given source configuration
POST/v1/scheduler/sources/discover_schemaRun discover schema for a given source a source configuration
POST/v1/source_definition_specifications/getGet specification for a SourceDefinition.
POST/v1/source_definitions/create_customCreates a custom sourceDefinition for the given workspace
POST/v1/source_definitions/deleteDelete a source definition
POST/v1/source_definitions/getGet source
POST/v1/source_definitions/get_for_workspaceGet a sourceDefinition that is configured for the given workspace
POST/v1/source_definitions/grant_definitiongrant a private, non-custom sourceDefinition to a given workspace
POST/v1/source_definitions/listList all the sourceDefinitions the current Airbyte deployment is configured to use
POST/v1/source_definitions/list_for_workspaceList all the sourceDefinitions the given workspace is configured to use
POST/v1/source_definitions/list_latestList the latest sourceDefinitions Airbyte supports
POST/v1/source_definitions/list_privateList all private, non-custom sourceDefinitions, and for each indicate whether the given workspace has a grant for using the definition. Used by admins to view a
POST/v1/source_definitions/revoke_definitionrevoke a grant to a private, non-custom sourceDefinition from a given workspace
POST/v1/source_definitions/updateUpdate a sourceDefinition
POST/v1/source_oauths/complete_oauthGiven a source def ID generate an access/refresh token etc.
POST/v1/source_oauths/get_consent_urlGiven a source connector definition ID, return the URL to the consent screen where to redirect the user to.
POST/v1/source_oauths/oauth_params/createSets instancewide variables to be used for the oauth flow when creating this source. When set, these variables will be injected into a connector's configuration
POST/v1/sources/check_connectionCheck connection to the source
POST/v1/sources/check_connection_for_updateCheck connection for a proposed update to a source
POST/v1/sources/cloneClone source
POST/v1/sources/createCreate a source
POST/v1/sources/deleteDelete a source
POST/v1/sources/discover_schemaDiscover the schema catalog of the source
POST/v1/sources/getGet source
POST/v1/sources/listList sources for workspace
POST/v1/sources/most_recent_source_actor_catalogGet most recent ActorCatalog for source
POST/v1/sources/searchSearch sources
POST/v1/sources/updateUpdate a source
POST/v1/sources/write_discover_catalog_resultShould only called from worker, to write result from discover activity back to DB.
POST/v1/state/create_or_updateCreate or update the state for a connection.
POST/v1/state/getFetch the current state for a connection.
POST/v1/web_backend/check_updatesReturns a summary of source and destination definitions that could be updated.
POST/v1/web_backend/connections/createCreate a connection
POST/v1/web_backend/connections/getGet a connection
POST/v1/web_backend/connections/listReturns all non-deleted connections for a workspace.
POST/v1/web_backend/connections/updateUpdate a connection
POST/v1/web_backend/geographies/listReturns available geographies can be selected to run data syncs in a particular geography. The 'auto' entry indicates that the sync will be automatically assign
POST/v1/web_backend/state/get_typeFetch the current state type for a connection.
POST/v1/web_backend/workspace/stateReturns the current state of a workspace
POST/v1/workspaces/createCreates a workspace
POST/v1/workspaces/deleteDeletes a workspace
POST/v1/workspaces/getFind workspace by ID
POST/v1/workspaces/get_by_connection_idFind workspace by connection id
POST/v1/workspaces/get_by_slugFind workspace by slug
POST/v1/workspaces/listList all workspaces registered in the current Airbyte deployment
POST/v1/workspaces/tag_feedback_status_as_doneUpdate workspace feedback state

Showing the first 100 of 102 endpoints; the full list is in the documentation.

Questions

Does the Airbyte Configuration API API need an API key?

Yes. The Airbyte Configuration API API uses Bearer token authentication; the documentation explains how to get credentials.

Does the Airbyte Configuration API API support HTTPS?

Yes, the Airbyte Configuration API API is served over HTTPS.

How many endpoints does the Airbyte Configuration API API have?

Its OpenAPI description lists 102 endpoints in version 1.0.0. The first 100 are shown on this page.

What are alternatives to the Airbyte Configuration API API?

Other Development APIs include Cloudflare, Azure DevOps, IPify, App Store Connect API, StackExchange.

Compare alternatives →

Listed from APIs.guru (CC0).