Account Connections
Overview
The Account Connection object represents the relationship between your enterprise and a creator. It includes such details as the creator’s name, how they’ve connected (Manifest or ACH), and what permissions they have granted you.
For a typical integration, you’ll create one Account Connection for each creator in your system, and store the ID with your creator data. You can do this ahead of time, say during creator enrollment in your system, or right after a creator requests to be paid by Manifest. Either way, an Account Connection must be created before a Connect Link can be generated or a Connect Invite can be sent.
Methods
POST
  /account-connection
Create a new account connection under your enterprise.
Body Parameters
Legal first name from your records.
Legal last name from your records.
Optional user identifier from your system. If set, Manifest will enforce uniqueness, e.g. attempts to create a second account connection for the same user will fail.
This should be a stable value like a User ID, not something that might change like an email address or phone number. This value should not contain any sensitive information.
Email address from your records. See sandbox testing for more information about using emails in sandbox.
Legal business name from your records.
Array of permissions to request from the user during the Connect flow. See below for details.
Text to prompt your users for their verification answer. Examples below.
Required answer to the verification prompt. Manifest will correct for case sensitivity and trim excess white space before comparing the user’s entered value. Any special formatting requirements should either be avoided or included in the verification prompt itself.
You can set a legacy payment method on new account connections. See below for available options and required fields.
User defined data that can be attached to the object. See the User Data page for details.
Example
Properties
Identifier for this account connection.
Type of account connection. One of direct
or ach
. This field will be populated once the creator has connected to your enterprise and selected a payout method.
Status of account connection. One of created
, active
, or deleted
. Only users can activate their connection (through the Connect flow).
Array of permissions to request from the user during the Connect flow. Possible values:
Permission | Description |
---|---|
payment.credit | Deposit to creator accounts. |
payment.debit | Debit creator accounts. (type direct connections only) |
Only ask for permissions you need to use; asking for more than you need might cause users to opt-out of connecting to you.
List of permissions granted by the creator during the Connect flow. Each permission object includes a name
and an optional expires_at
.
Legal first name from your records.
Legal last name from your records.
Optional user identifier from your system. If set, Manifest will enforce uniqueness, e.g. attempts to create a second account connection for the same user will fail.
This should be a stable value like a User ID, not something that might change like an email address or phone number. This value should not contain any sensitive information.
Email address from your records. Note, this does not need to match the user’s Manifest account email address, this is just an email address you use to communicate with this user. See sandbox testing for more information about using emails in sandbox.
Legal business name from your records.
Text to prompt your users for their verification answer. Examples:
- Please enter the last 4 digits of your tax ID.
- Please enter your Triangle Artist ID.
- Please enter the last 4 digits of the bank account number where you currently receive your Triangle payments.
Required answer to the verification prompt. Manifest will correct for case sensitivity and trim excess white space before comparing the user’s entered value. Any special formatting requirements should either be avoided or included in the verification prompt itself.
An optional object describing legacy payout method details that can be set on new account connections. Used to migrate a creator’s existing payout method to Manifest. Details:
A plaintext label of the current destination account, suitable for display. (Not included in list endpoints.)
User defined data that can be attached to the object. See the User Data page for details.