Skip to main content
POST
Grant integration access

Authorizations

Authorization
string
header
required

An API key prefixed with finta_, or the access token from a Finta CLI browser login (finta login), prefixed with finta_oat_. A CLI login's access token lasts one hour and the CLI renews it itself.

Path Parameters

key
string
required

The integration's key from GET /integrations, e.g. mercury.

Body

application/json
url
string

Carta and Pulley only, and required for them: the company's page URL at the provider, or just its numeric ID there.

Example:

"https://app.carta.com/corporations/12345"

Response

The integration, as GET /integrations lists it, with its grant_access method granted (connecting for Carta and Pulley, connected for Gusto and Rippling).

key
string
required

Stable identifier for the integration, e.g. mercury, ramp, carta.

Example:

"mercury"

object
enum<string>
required
Available options:
integration
name
string
required

Human-readable vendor name.

Example:

"Mercury"

type
enum<string>
required

What kind of integration this is.

Available options:
banking,
cap_table,
payroll,
revenue,
notifications,
legal
status
enum<string>
required

Connection state. connecting means Finta has the connection but isn't done setting it up, such as a Carta or Pulley connection whose invite Finta is still checking. requires_reconnect means a previously working connection needs the user to reauthenticate.

Available options:
not_connected,
connected,
connecting,
requires_reconnect
connection_methods
object[]
required

Each way this integration can be connected, with where it stands. Every integration has the method it connects with. Mercury and Ramp also list a grant_access method once Finta asks the company to invite Finta for Mercury Treasury or Ramp Checking, data their sign-in connection doesn't include. Order is not significant.

quality
enum<string>
required

How reliable this integration's data is, the same rating the Finta web app shows. great is an OAuth or API connection with real-time updates, good is read-only access straight from the source that is not real-time, and third_party is a Plaid-based bank connection whose data can be incomplete or error-prone.

Available options:
great,
good,
third_party
signup_referral
object | null
required

A referral offer for opening an account with this provider. Present only while status is not_connected and the provider has a Finta referral; null otherwise.