​
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

​
first_name
string
required
Legal first name from your records.
​
last_name
string
required
Legal last name from your records.
​
external_id
string
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
string
required
Email address from your records. See sandbox testing for more information about using emails in sandbox.
​
business_name
string
Legal business name of the creator from your records, if applicable.
​
display_name
string
Display name, visible to the creator. Examples: a band name, online persona, or shortened version of the business name.
​
requested_permissions
string[]
required
Array of permissions to request from the user during the Connect flow. See below for details.
​
verification_prompt
string
required
Text to prompt your users for their verification answer. Examples below.
​
verification_answer
string
required
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.
​
legacy_payout_method
string
You can set a legacy payment method on new account connections. See below for available options and required fields.
​
user_data
object
User defined data that can be attached to the object. See the User Data page for details.

​
Example

// POST /account-connection
{
    "first_name": "Paul",
    "last_name": "McCartney",
    "email": "paul@thebeatles.com",
    "display_name": "The Beatles",
    "requested_permissions": ["payment.credit"],
    "verification_prompt": "Please enter the last 4 digits of your tax ID.",
    "verification_answer": "1234"
}

​
Properties

​
id
string
Identifier for this account connection.
​
type
string
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
string
Status of account connection. One of created, active, or deleted. Only users can activate their connection (through the Connect flow).
​
requested_permissions
string[]
Array of permissions to request from the user during the Connect flow. Possible values:
PermissionDescription
payment.creditDeposit to creator accounts.
payment.debitDebit creator accounts. (type direct connections only)
checkoutProcess payments on behalf of creators. (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.
​
permissions
object[]
List of permissions granted by the creator during the Connect flow. Each permission object includes a name and an optional expires_at.
​
first_name
string
Legal first name from your records.
​
last_name
string
Legal last name from your records.
​
external_id
string
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
string
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.
​
display_name
string
Display name, visible to the creator. Examples are a band name, an online persona, or shortened version of the business name.
​
business_name
string
Legal business name from your records.
​
verification_prompt
string
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.
​
verification_answer
string
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.
​
legacy_payout_method
object
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:
​
destination
string
A plaintext label of the current destination account, suitable for display. (Not included in list endpoints.)
​
user_data
object
User defined data that can be attached to the object. See the User Data page for details.