Create External Connection
/users/{user_id}/connectionsCreates a customer-managed connection for pushing your own transaction data (bring-your-own-data). Only type: external may be created directly. card, store, and benefit_account connections are established through a connect_account hosted session. Requires the connections key scope. External connections support only the expenses product.
Path Parameters
The Sail user id.
Body application/json
Must be external — the only type creatable directly via this endpoint.
Customer-declared label for the upstream source, shown wherever a provider name would appear (e.g. “Acme Budgeting · Plaid feed”).
Products enabled on this connection. Currently only expenses is supported.
Response
Connection created.
The Sail connection id.
The Sail user this connection belongs to.
The kind of data source this connection links to.
The connection’s current sync/authentication status.
Capabilities enabled on this connection.
Embedded summaries of the accounts under this connection, so account ids are discoverable without a second call. Populated for benefit_account connections (a single administrator login can hold multiple benefit accounts, e.g. HSA + LPFSA); empty for connection types whose accounts are not exposed. Full detail — balances, numbers, contributions — lives at /users/{user_id}/accounts/{account_id}.
The external party this connection links to.
Present when the connection is in an error state. Null otherwise.
When this connection last completed a sync. Null if it has never synced.
When the connection was created.
When the connection was last updated.
invalid_request: type must be external.
Standard error envelope covering 400, 401, 403, 404, 429, and 500.
The error detail.