Getting Started
Master Accounts
Sub Account Holders
Sub Accounts
Counterparties
Card Holders
Cards
Transactions
- GETList all Transactions
- POSTSub Ledger a Transaction
- POSTOriginate an Intra Account Push
- POSTOriginate an Intra Account Pull
- POSTOriginate an ACH Push
- POSTOriginate an ACH Pull
- POSTOriginate a Domestic Wire
- POSTOriginate an International Wire
- POSTOriginate an RTP Push
- POSTOriginate a FedNow Push
- POSTOriginate a Debit Card Push
- POSTOriginate a Debit Card Pull
- POSTOriginate a Check Send
- POSTOriginate a Check Deposit
- GETRetrieve a Transaction
- PATCHUpdate a Transaction
Attachments
Webhooks
Create a Card Holder
Create a Card Holder
API key is required to call Solid APIs. You can view and manage your API keys in the Solid dashboard.
unique id of the sub account
first name of the person
middle name of the person
last name of the person
type of identity used
- if id_type is ssn, id_number must be full SSN
- if id_type is passport, id_number must be passport number
- if id_type is other, id_number must be unique number of the id
id_number must be unique, as in, you cannot use the same id_number for two different persons
date of birth of the person (YYYY-MM-DD)
phone number of the person (E.164, max 16 chars, starts with +)
email of the person
line 1 of the address
line 2 of the address
city of the address
2-Letter US state abbreviation (ex: CA)
2-letter abbreviated country code (ex: US)
postal code
unique id of the KYC
status of the KYC
sub account holder verification method. It could be an external vendor(Ex: alloy) or Solid
url to the person or business verification result. It could be a link to the external vendor or Solid
unique id of the IDV
status of the IDV
sub account holder IDV method. It could be an external vendor(Ex: plaid) or Solid
url to the identity verification result. It could be a link to the external vendor or Solid
unique id to cross-reference records with external systems
purpose of card holder
Metadata takes free-form key-value pairs. You may send metadata when you create an object (POST) and when updating the object (PATCH). If you would like to remove metadata that is already on an object, you can unset it by passing in the key-value pair with an empty string, like this: {"key": ""}
Headers
API key is required to call Solid APIs. You can view and manage your API keys in the Solid dashboard.
Body
unique id of the sub account
first name of the person
middle name of the person
last name of the person
type of identity used
ssn, passport, other - if id_type is ssn, id_number must be full SSN
- if id_type is passport, id_number must be passport number
- if id_type is other, id_number must be unique number of the id
id_number must be unique, as in, you cannot use the same id_number for two different persons
date of birth of the person (YYYY-MM-DD)
phone number of the person (E.164, max 16 chars, starts with +)
email of the person
line 1 of the address
line 2 of the address
city of the address
2-Letter US state abbreviation (ex: CA)
2-letter abbreviated country code (ex: US)
postal code
unique id of the KYC
status of the KYC
pass, fail, review, not_started sub account holder verification method. It could be an external vendor(Ex: alloy) or Solid
url to the person or business verification result. It could be a link to the external vendor or Solid
unique id of the IDV
status of the IDV
pass, fail, review, not_started sub account holder IDV method. It could be an external vendor(Ex: plaid) or Solid
url to the identity verification result. It could be a link to the external vendor or Solid
unique id to cross-reference records with external systems
purpose of card holder
Metadata takes free-form key-value pairs. You may send metadata when you create an object (POST) and when updating the object (PATCH). If you would like to remove metadata that is already on an object, you can unset it by passing in the key-value pair with an empty string, like this: {"key": ""}
Response
unique id of the card holder
unique id of the client that issued the card
unique id of the master account holder
unique id of the master account
unique id of the sub account holder
unique id of the sub account
first name of the person
middle name of the person
last name of the person
type of identity used
ssn, passport, other - if id_type is ssn, id_number must be full SSN
- if id_type is passport, id_number must be passport number
- if id_type is other, id_number must be unique number of the id
id_number must be unique, as in, you cannot use the same id_number for two different persons
date of birth of the person (YYYY-MM-DD)
phone number of the person (E.164, max 16 chars, starts with +)
email of the person
line 1 of the address
line 2 of the address
city of the address
2-Letter US state abbreviation (ex: CA)
2-letter abbreviated country code (ex: US)
postal code
unique id of the KYC
status of the KYC
pass, fail, review, not_started sub account holder verification method. It could be an external vendor(Ex: alloy) or Solid
url to the person or business verification result. It could be a link to the external vendor or Solid
unique id of the IDV
status of the IDV
pass, fail, review, not_started sub account holder IDV method. It could be an external vendor(Ex: plaid) or Solid
url to the identity verification result. It could be a link to the external vendor or Solid
unique id to cross-reference records with external systems
purpose of card holder
unique id of the attachment created
label of the attachment
Metadata takes free-form key-value pairs. You may send metadata when you create an object (POST) and when updating the object (PATCH). If you would like to remove metadata that is already on an object, you can unset it by passing in the key-value pair with an empty string, like this: {"key": ""}
status of card holder
pending_activation, activated, suspended, deactivated, locked