Skip to content
Cloud infrastructure/devops

airbyte.local:config

Airbyte Configuration sandbox and mock API

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 Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
102
Collections
-
Event types
-
example request
curl https://your-airbyte-local-config.slurry.io/v1/health \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 102.

  • POST/v1/attempt/save_stats
  • POST/v1/attempt/save_sync_config
  • POST/v1/attempt/set_workflow_in_attempt
  • POST/v1/connections/create
  • POST/v1/connections/delete
  • POST/v1/connections/get
  • POST/v1/connections/list
  • POST/v1/connections/list_all
  • POST/v1/connections/reset
  • POST/v1/connections/search
  • POST/v1/connections/sync
  • POST/v1/connections/update