Cal.com

Attify reads Cal.com through its API, read-only, with OAuth or an API token, for sales meetings and bookings. It is the customer's own system, so what Attify reads there is connected data: the strongest provenance, and what a vendor verification rests on.

As a crm or calendar, for sales meetings, bookings

ItemCal.com
idbooking uid
started_atcreatedAt
updated_atupdatedAt, else createdAt
start, endstart, end
statusaccepted: booked; pending, awaiting_host: pending; cancelled, rejected:
cancelled (an unknown status reads as pending, never as booked)
cancelled_atupdatedAt of a cancelled booking (its last change, the cancellation)
cancelled_bycancelledByEmail: a host's address is "host", an attendee's "invitee";
a rejected booking is the host's
rescheduled_*rescheduledFromUid (or fromReschedule), rescheduledToUid
created_byinvitee, unless metadata carries an app marker (source, app, agent,
integration, created_by, booked_by): app, id that value (caller-set)
changesthe cancellation by cancelledByEmail, the reschedule by
rescheduledByEmail: a host is "user", an attendee "invitee"
ainull: Cal.com does not say
attendancemark, no_show when every attendee is absent. absentHost (the host did
not come) is not the customer's no-show and is not read
serviceeventType.title, else eventType.slug
duration_minutesduration, else end minus start
price, currencynull: not in the documented booking response (the event type holds them,
at today's price, not the booked one)
provider,the first host's email
organizer
attendeesattendees[] (accepted) and guests (none)
location, titlelocation, title
linksical:<icsUid>