Automate Airbyte Configuration
HumDay reads Airbyte Configuration’s own published API description and derives 102 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Airbyte Configuration is
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 a
API host: airbyte.local
What HumDay can do in Airbyte Configuration
100 documented operations change something in Airbyte Configuration. The 98 most useful are listed here.
- POSTCreates a workspace
/v1/workspaces/create - POSTReturns recent jobs for a connection.
/v1/jobs/list - POSTList sources for workspace
/v1/sources/list - POSTCreate a source
/v1/sources/create - POSTSearch sources
/v1/sources/search - POSTReturns all operations for a connection.
/v1/operations/list - POSTList all workspaces registered in the current Airbyte deployment
/v1/workspaces/list - POSTReturns all connections for a workspace.
/v1/connections/list - POSTList configured destinations for a workspace
/v1/destinations/list - POSTCreate an operation to be applied as part of a connection pipeline
/v1/operations/create - POSTCreate a connection between a source and a destination
/v1/connections/create - POSTSearch connections
/v1/connections/search - POSTCreate a destination
/v1/destinations/create - POSTSearch destinations
/v1/destinations/search - POSTCreate or update the state for a connection.
/v1/state/create_or_update - POSTList all the sourceDefinitions the current Airbyte deployment is configured to use
/v1/source_definitions/list - POSTList all the destinationDefinitions the current Airbyte deployment is configured to use
/v1/destination_definitions/list - POSTGiven a source connector definition ID, return the URL to the consent screen where to redirect the user to.
/v1/source_oauths/get_consent_url - POSTList the latest sourceDefinitions Airbyte supports
/v1/source_definitions/list_latest - POSTList all private, non-custom sourceDefinitions, and for each indicate whether the given workspace has a grant for using the definition.
/v1/source_definitions/list_private - POSTCreates a custom sourceDefinition for the given workspace
/v1/source_definitions/create_custom - POSTGiven a destination connector definition ID, return the URL to the consent screen where to redirect the user to.
/v1/destination_oauths/get_consent_url - POSTList the latest destinationDefinitions Airbyte supports
/v1/destination_definitions/list_latest - POSTList all private, non-custom destinationDefinitions, and for each indicate whether the given workspace has a grant for using the definition.
/v1/destination_definitions/list_private - POSTCreates a custom destinationDefinition for the given workspace
/v1/destination_definitions/create_custom - POSTList all the sourceDefinitions the given workspace is configured to use
/v1/source_definitions/list_for_workspace - POSTList all the destinationDefinitions the given workspace is configured to use
/v1/destination_definitions/list_for_workspace - POSTReturns all non-deleted connections for a workspace.
/v1/web_backend/connections/list - POSTReturns available geographies can be selected to run data syncs in a particular geography.
/v1/web_backend/geographies/list - POSTCreate a connection
/v1/web_backend/connections/create - POSTGet information about a job
/v1/jobs/get - POSTGet logs
/v1/logs/get - POSTFetch the current state for a connection.
/v1/state/get - POSTCancels a job
/v1/jobs/cancel - POSTGet source
/v1/sources/get - POSTClone source
/v1/sources/clone - POSTGet information about a job excluding attempt info and logs
/v1/jobs/get_light - POSTReturns an operation
/v1/operations/get - POSTDelete a source
/v1/sources/delete - POSTUpdate a source
/v1/sources/update - POSTFind workspace by ID
/v1/workspaces/get - POSTGet a connection
/v1/connections/get - POSTTrigger a manual sync of the connection
/v1/connections/sync - POSTGet configured destination
/v1/destinations/get - POSTCheck if an operation to be created is valid
/v1/operations/check - POSTReset the data for the connection.
/v1/connections/reset - POSTTry sending a notifications
/v1/notifications/try - POSTDelete an operation
/v1/operations/delete - POSTUpdate an operation
/v1/operations/update - POSTDeletes a workspace
/v1/workspaces/delete - POSTUpdate workspace state
/v1/workspaces/update - POSTFor worker to set sync stats of a running attempt.
/v1/attempt/save_stats - POSTDelete a connection
/v1/connections/delete - POSTUpdate a connection
/v1/connections/update - POSTClone destination
/v1/destinations/clone - POSTDelete the destination
/v1/destinations/delete - POSTUpdate a destination
/v1/destinations/update - POSTReturns all connections for a workspace, including deleted connections.
/v1/connections/list_all - POSTGet source
/v1/source_definitions/get - POSTFind workspace by slug
/v1/workspaces/get_by_slug - POSTUpdate workspace name
/v1/workspaces/update_name - POSTDiscover the schema catalog of the source
/v1/sources/discover_schema - POSTFor worker to save the AttemptSyncConfig for an attempt.
/v1/attempt/save_sync_config - POSTCheck connection to the source
/v1/sources/check_connection - POSTDelete a source definition
/v1/source_definitions/delete - POSTUpdate a sourceDefinition
/v1/source_definitions/update - POSTReturns a summary of source and destination definitions that could be updated.
/v1/web_backend/check_updates - POSTGet destinationDefinition
/v1/destination_definitions/get - POSTGiven a source def ID generate an access/refresh token etc.
/v1/source_oauths/complete_oauth - POSTCheck connection to the destination
/v1/destinations/check_connection - POSTGet normalization status to determine if we can bypass normalization phase
/v1/jobs/get_normalization_status - POSTDelete a destination definition
/v1/destination_definitions/delete - POSTUpdate destinationDefinition
/v1/destination_definitions/update - POSTFor worker to register the workflow id in attempt.
/v1/attempt/set_workflow_in_attempt - POSTFind workspace by connection id
/v1/workspaces/get_by_connection_id - POSTGiven a destination def ID generate an access/refresh token etc.
/v1/destination_oauths/complete_oauth - POSTgrant a private, non-custom sourceDefinition to a given workspace
/v1/source_definitions/grant_definition - POSTCheck connection for a proposed update to a source
/v1/sources/check_connection_for_update - POSTGet specification for a SourceDefinition.
/v1/source_definition_specifications/get - POSTGet a sourceDefinition that is configured for the given workspace
/v1/source_definitions/get_for_workspace - POSTrevoke a grant to a private, non-custom sourceDefinition from a given workspace
/v1/source_definitions/revoke_definition - POSTShould only called from worker, to write result from discover activity back to DB.
/v1/sources/write_discover_catalog_result - POSTUpdate workspace feedback state
/v1/workspaces/tag_feedback_status_as_done - POSTgrant a private, non-custom destinationDefinition to a given workspace
/v1/destination_definitions/grant_definition - POSTCheck connection for a proposed update to a destination
/v1/destinations/check_connection_for_update - POSTGet most recent ActorCatalog for source
/v1/sources/most_recent_source_actor_catalog - POSTGet specification for a destinationDefinition
/v1/destination_definition_specifications/get - POSTGet a destinationDefinition that is configured for the given workspace
/v1/destination_definitions/get_for_workspace - POSTrevoke a grant to a private, non-custom destinationDefinition from a given workspace
/v1/destination_definitions/revoke_definition - POSTFetch the current state type for a connection.
/v1/web_backend/state/get_type - POSTGet a connection
/v1/web_backend/connections/get - POSTReturns the current state of a workspace
/v1/web_backend/workspace/state - POSTUpdate a connection
/v1/web_backend/connections/update - POSTRun discover schema for a given source a source configuration
/v1/scheduler/sources/discover_schema - POSTRun check connection for a given source configuration
/v1/scheduler/sources/check_connection - POSTRun check connection for a given destination configuration
/v1/scheduler/destinations/check_connection - POSTSets instancewide variables to be used for the oauth flow when creating this source.
/v1/source_oauths/oauth_params/create - POSTSets instancewide variables to be used for the oauth flow when creating this destination.
/v1/destination_oauths/oauth_params/create
What HumDay can read from Airbyte Configuration
These are the operations a schedule or a trigger can watch.
- GETHealth Check
/v1/health - GETReturns the openapi specification
/v1/openapi
How automating Airbyte Configuration works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Airbyte Configuration account.
- Grant access, then go live. You approve the specific Airbyte Configuration operations it may use — and only those.
Automate Airbyte Configuration with these
- OData for namespace microsoft.graph11412 operations
- GitHub811 operations
- Atlassian The Jira Cloud platform474 operations
- Gitlab358 operations
- JIRA 7.6.1324 operations
- Appcenter App Center Client323 operations
- Gitea .321 operations
- Bitbucket292 operations
- Keycloak Admin281 operations
- Apple App Store Connect251 operations
- Files.com222 operations
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about Airbyte Configuration automation
- Can HumDay connect to Airbyte Configuration?
- Yes. HumDay reads Airbyte Configuration's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 102 operations are documented.
- Do I need to write code to automate Airbyte Configuration?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Airbyte Configuration account.
- What can HumDay do in Airbyte Configuration?
- 100 of the 102 documented operations change something in Airbyte Configuration, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Airbyte Configuration account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Airbyte Configuration is held behind that approval.
Where this came from
The operations above are read from a published API description for Airbyte Configuration at raw.githubusercontent.com/airbytehq/airbyte/master/airbyte-api/src/main/openapi/config.yam. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.