An email address for your user.

When enabled, all data is submitted and validated by Cardly, however no contact records will be deleted.

The list to remove this specified contact from.

One of: the Cardly unique ID, your external (ie, CRM) unique ID, or an email address for a contact to delete, matched in this order of priority. We highly recommend using external IDs from your CRM or other system that are unique to each user to manage contacts.

When enabled, all data is submitted and validated by Cardly, however no contact records will be deleted.

An email address for your user.

Provide the user's given name if available, saving them needing to provide this at signup.

Provide the user's surname if available, saving them needing to provide this at signup.

When enabled, the user may send as many cards as your total credit pool allows. Otherwise, they will be restricted to your per-user account settings.

When enabled, the user may use your organisation's stored credit card (if saved) to pay for card sends.

When enabled, all data is submitted and validated by Cardly, however no contact records will be deleted.

The first/given name of the person this card is addressed to. This will appear on the envelope.

The surname of your recipient.

If your recipient's address is for a company, adding the company name can result in more reliable delivery.

The two character ISO code for the country your recipient resides in. Note that sending outside the US, UK and Australia adds a small postage cost to a send.

The recipient's street address, including street number and street name. For example, 282 Wickham St.

This is where any apartment, suite or floor number goes, if required. For example, Level 2, Suite 1361.

The suburb or city for the recipient, as it should appear on the envelope. For example, Fortitude Valley.

The ZIP or postal code for your recipient, formatted as required for the destination country. For example, 4006 or 90210.

When enabled, allows you to specify sender details that are different to your account's default return address.

When enabled, the sender's address will not appear on the the envelope.

If specified, denotes the target date for the recipient to receive a card. We'll automatically ship far enough in advance to aim for this date.

To allow you to match orders against an external system, send through your order other reference code here.

When enabled, all data is submitted and validated by Cardly, however no orders will actually be created or credit consumed.

The list to create this contact in.

Highly recommended: An identifer from your database, CRM or other source that uniquely identifies this contact. Please note: this is the most reliable way to sync contacts between your source system and Cardly.

Ideally this field contains only the contact's first name, however may also accept the contact's full name and we'll attempt to split it for you.

The contact's surname if available.

An email address for your contact. Optional, however this can be utilised as a unique identifier for your contacts if supplied.

The company this contact belongs to, if known.

The contact's street address, including street number and street name. For example, 282 Wickham St.

This is where any apartment, suite or floor number goes, if required. For example, Level 2, Suite 1361.

The suburb or city for the contact, as it should appear on the envelope. For example, Fortitude Valley.

The abbreviated state or region for the contact, as it should appear on the envelope, if required by the destination country. For example, QLD or NY. You can send through the full, human-readable name if needed and we'll attempt to map it to the right code.

The two character ISO code for the country the contact resides in. Note that sending outside the US, UK and Australia adds a small postage cost to a send.

The ZIP or postal code for your contact, formatted as required for the contact's country. For example, 4006 or 90210.

When enabled, all data is submitted and validated by Cardly, however no contact records will be deleted.

The list to sync this contact with.

If available: Cardly's internal identifier for this contact, which is supplied in the return data for a contact addition. If you don't store this, that's ok - but you'll need either an external ID (preferred) or email address below instead to correctly identify the contact to sync.

Highly recommended: An identifer from your database, CRM or other source that uniquely identifies this contact. Please note: this is the most reliable way to sync contacts between your source system and Cardly.

Ideally this field contains only the contact's first name, however may also accept the contact's full name and we'll attempt to split it for you.

The contact's surname if available.

Conditionally required: An email address for your contact. Optional, however this can be utilised as a unique identifier for your contacts if supplied.

The company this contact belongs to, if known.

The contact's street address, including street number and street name. For example, 282 Wickham St.

This is where any apartment, suite or floor number goes, if required. For example, Level 2, Suite 1361.

The suburb or city for the contact, as it should appear on the envelope. For example, Fortitude Valley.

The abbreviated state or region for the contact, as it should appear on the envelope, if required by the destination country. For example, QLD or NY. You can send through the full, human-readable name if needed and we'll attempt to map it to the right code.

The two character ISO code for the country the contact resides in. Note that sending outside the US, UK and Australia adds a small postage cost to a send.

The ZIP or postal code for your contact, formatted as required for the contact's country. For example, 4006 or 90210.

When enabled, all data is submitted and validated by Cardly, however no contact records will be deleted.

A descriptive name for the contacts in this list, such as Recent Orders or Current Employees.

Notes or extended information on this list - entirely optional, this is just to help you manage your data.

Dynamically create custom fields for this list. Please be careful here!

When enabled, all data is submitted and validated by Cardly, however no lists will actually be created.