Name	Description
Address	A contact's address. A Contact can have multiple addresses but must always have at least one address. Each Contact must have exactly one address where each of the following properties is true: IsMailing, IsBilling and IsDelivery. Note that these can all be set on one address or spread across multiple addresses.
ConsentDetails	The Consent Details attached to a consent preference.
ConsentPreference	The Contact's Consent Preferences.
ContactCheck	Information about a contact from the checking process.
ContactData	Pre-defined information about a contact.
CPDDetails	A Contact's CPD Details. There will only be one set of CPD Details for an individual Contact.
CPDItem	A Contact's CPD Item. A Contact can have multiple CPD Items.
Event	The basic details of an event within SubscriberCRM.
EventVenue	The details of a venue for events within SubscriberCRM.
EventWebsiteSettings	The contact types contained in SubscriberCRM.
Group	The groups contained in SubscriberCRM.
GroupMember	Information about a Contacts membership to a Group.
HoldingAddress	Either a new contact's address or an existing contact's holding address. A Contact can have multiple addresses but must always have at least one address. Each Contact must have exactly one address where each of the following properties is true: IsMailing, IsBilling and IsDelivery. Note that these can all be set on one address or spread across multiple addresses.
HoldingBooking	A new booking for an event.
HoldingDelegate	A new delegate (attendee) on a new event booking.
HoldingGroupMember	Information about a Contacts membership to a Group.
HoldingNewContact	A new contact to be added to SubscriberCRM. This will go into the 'Web Sync - New Contacts' area for processing. This is the best method of adding a new contact rather than manually adding the individual elements.
HoldingPayment	The details of a Payment belonging to a new Contact.
HoldingPersonalDetails	The Contact's personal details.
HoldingProfile	A Contact's profile data. Profiles are user-defined data structures that can contain many different types of data. There are two types of Profile - Single and Multiple. The Single profile type can contain any number of fields, but only a single value for each field (i.e. 1 row in a table). The Multiple profile type can contain many entries (i.e. many rows in a table).
HoldingProfileRow
HoldingSubEventBooking	An individual element of an event that a new delegate has booked.
HoldingSubscriptionDetails	The details of a holding subscription belonging to a Contact or new Contact.
NewContact	A new contact to be added to SubscriberCRM. This will create a new contact directly. This is the best method of adding a new contact rather than manually adding the individual elements.
Payment	The details of a Payment for an existing Contact.
PaymentDemand	An amount of money that is/was owed by the Contact.
PersonalDetails	The Contact's personal details.
Profile	A Contact's profile data. Profiles are user-defined data structures that can contain many different types of data. There are two types of Profile - Single and Multiple. The Single profile type can contain any number of fields, but only a single value for each field (i.e. 1 row in a table). The Multiple profile type can contain many entries (i.e. many rows in a table).
ProfileField	A contact's address. A Contact can have multiple addresses but must always have at least one address. Each Contact must have exactly one address where each of the following properties is true: IsMailing, IsBilling and IsDelivery. Note that these can all be set on one address or spread across multiple addresses.
ProfileRow
SubEvent	An individual element of an event that can be booked - e.g. a ticket, workshop/session place, dinner option.
SubscriptionDetails	The details of a subscription belonging to a Contact.
SubscriptionPayment	The details of a Payment for an existing Contact.

The SubscriberCRM API uses HTTP Basic authentication. The credentials are authenticated against the SusbcriberCRM users.