Base URL
Authentication
All requests must include a Bearer token in theAuthorization header.
Path Parameters
The unique identifier of the contact to retrieve. This is the same ID referenced as
contact.id in payables.Response
Returns aContact object.
Unique identifier for the contact.
The contact type:
payee or business.The contact’s current status:
active, archived, or revoked.The contact’s display name, if set.
Email addresses associated with the contact. Always empty for
business-type contacts.Phone number for the contact. Always
null for business-type contacts.Indicates the allowed payment direction for this contact. One of:
bidirectional— can both send and receive paymentscan_pay— can only send paymentscan_be_paid— can only receive paymentsnone— no payment capability configured
Net payment terms in days, if configured.
Summary of the contact’s linked bank account.
null if no bank account has been added.Tax information for the contact.
null if no tax info has been provided.Whether this contact can currently receive payments. A contact is payment-ready when a valid bank account is on file and the contact is in
active status.ISO 8601 timestamp of when the contact was created.
ISO 8601 timestamp of the most recent update.
null if the contact has never been updated.ISO 8601 timestamp of when the contact was archived.
null if the contact is not archived.Example Request
curl
Example Response
200
The
paymentReady flag reflects whether a payment can be initiated to this contact right now. A contact may have a bank account on file but still have paymentReady: false if their account is in a non-active status.