Skip to main content

ArangoDB

Overview​

The ArangoDB connector lets you authenticate to an ArangoDB deployment and (eventually) load data into it as a Reverse ETL destination.

At this time, the destination connector is in development: credential validation is supported, but loading data is not yet implemented.

Setup​

Prerequisites​

  • An accessible ArangoDB HTTP endpoint (for example, http://localhost:8529 or https://arangodb.example.com:8529)
  • A username and password that can authenticate to the ArangoDB instance

Network access​

Ensure the ArangoDB endpoint is reachable from the environment running the connector.

Authentication​

The connector uses HTTP Basic Authentication (username + password) and validates credentials by calling:

  • GET /_api/database/current

If authentication fails, the connector will report a credential validation error.

Configuration​

FieldTypeRequiredDescription
endpointstring✅Base URL for your ArangoDB deployment (for example, http://localhost:8529).
usernamestring✅ArangoDB username used for Basic Auth.
passwordstring✅ArangoDB password used for Basic Auth.

Hashing and normalization​

This connector does not currently expose field-level hashing controls.

Data contract​

Loading data into ArangoDB is not yet implemented for this destination connector, so there is no stable, user-facing data contract to document at this time.

Streams​

This is a destination connector. It does not expose source streams.

Limitations​

  • Destination loading is not yet supported. Runs will fail at load time with an “in development” error.
  • Only credential validation (Basic Auth against /_api/database/current) is currently implemented.