Grant integration access
Records that the user has invited Finta as a user in the provider’s own app, for a
grant_access connection method whose connect_via is provider_app in
GET /integrations. Finta can’t see the invite, so it relies on this. Call it only
once the user says the invite is sent.
Granting access also closes the Finta inbox item that asked for it, such as Mercury
Treasury’s or Ramp Checking’s grant_access item. Calling it again once access is
granted changes nothing and returns the same integration.
Carta and Pulley also need url, the company’s page at the provider, such as
https://app.carta.com/corporations/12345 or https://pulley.com/companies/1234.
Finta then checks the invite in the background (for Carta from that page, for Pulley
once Pulley’s invite email arrives), and the integration’s status is connecting
until it has. Other integrations reject url.
For Gusto and Rippling, granting access connects the payroll integration: its status
and its grant_access method read connected, and Finta’s team is told to review it.
Any other integration, or Mercury and Ramp while Finta isn’t asking for access, returns
400 integration_not_grantable.
Authorizations
Body
Response
The integration, as GET /integrations lists it, with its grant_access method granted (connecting for Carta and Pulley, connected for Gusto and Rippling).
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.
not_connected, connected, connecting, requires_reconnect 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.
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.
great, good, third_party