POST /beta/partner/customer/v1/create

Default value: "application/json"

Your Plaid API client_id. The client_id is required and may be provided either in the PLAID-CLIENT-ID header or as part of a request body.

The questionnaires for the end customer.

The CRA questionnaire for the end customer.

Denotes whether the third party is involved.

A map of permissible purposes to their corresponding use cases.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

The list of use cases associated with a given permissible purpose.

List of use cases for the given permissible purpose.

Denotes whether the technical service provider is involved.

The name of the end customer's application. This will be shown to end users when they go through the Plaid Link flow. The application name must be unique and cannot match the name of another application already registered with Plaid.

The end customer's website.

The end customer's legal name. This will be shared with financial institutions as part of the OAuth registration process. It will not be shown to end users.

The billing contact for the end customer. Defaults to partner's billing contact if omitted.

The bank addendum acceptance for the end customer.

The timestamp of when the end customer accepted the bank addendum in ISO 8601 format (YYYY-MM-DDTHH:mm:ssZ).

Denotes whether the end customer has accepted the bank addendum terms.

The IP address of the end customer when they accepted the bank addendum.

This information is public. Users of your app will see this information when managing connections between your app and their bank accounts in Plaid Portal. Defaults to partner's customer support info if omitted. This field is mandatory for partners whose Plaid accounts were created after November 26, 2024 and will be mandatory for all partners by the 1033 compliance deadline.

This field is mandatory for partners whose Plaid accounts were created after November 26, 2024 and will be mandatory for all partners by the 1033 compliance deadline.

The products to be enabled for the end customer. If empty or null, this field will default to the products enabled for the reseller at the time this endpoint is called.

Base64-encoded representation of the end customer's logo. Must be a PNG of size 1024x1024 under 4MB. The logo will be shared with financial institutions and shown to the end user during Link flows. A logo is required if create_link_customization is true. If create_link_customization is false and the logo is omitted, the partner's logo will be used if one exists, otherwise a stock logo will be used.

Denotes whether or not the partner has completed attestation of diligence for the end customer to be created.

The company name of the end customer being created. This will be used to display the end customer in the Plaid Dashboard. It will not be shown to end users.

If true, the end customer's default Link customization will be set to match the partner's. You can always change the end customer's Link customization in the Plaid Dashboard. See the Link Customization docs for more information. If you require the ability to programmatically create end customers using multiple different Link customization profiles, contact your Plaid Account Manager for assistance.

Important: Data Transparency Messaging (DTM) use cases will not be copied to the end customer's Link customization unless the Publish changes button is clicked after the use cases are applied. Link will not work in Production unless the end customer's DTM use cases are configured. For more details, see Data Transparency Messaging.

Your Plaid API secret. The secret is required and may be provided either in the PLAID-SECRET header or as part of a request body.

The technical contact for the end customer. Defaults to partner's technical contact if omitted.

The end customer's address.

ISO-3166-1 alpha-2 country code standard.

A list of URIs indicating the destination(s) where a user can be forwarded after completing the Link flow; used to support OAuth authentication flows when launching Link in the browser or another app. URIs should not contain any query parameters. When used in Production, URIs must use https. To specify any subdomain, use * as a wildcard character, e.g. https://*.example.com/oauth.html. To modify redirect URIs for an end customer after creating them, go to the end customer's API page in the Dashboard.