Calendar and trips

Calendars

It takes calendar_id, and archived - 1 to include archived calendars. Each has its calendar_id, calendar_name and calendar_color. Calendars are added with the + beside them on the calendar, and their subscription links stay there.

Events

An event with no client is anyone's, as on the calendar. A client's event needs the Clients area of the key's role: Read to see it - or the key's agent made it or is on it - Modify to make or change one, and Full to delete one (Modify for one its agent made). See Keys and permissions.

Read

A repeating event is one row: event_repeat - Day, Week, Month or Year - every event_repeat_interval, until event_repeat_until, without the days in event_repeat_skip. Each attendee has its kind - agent, contact or guest - name, email and invited_at, when it was sent the invitation.

Fields: event_id, event_title, event_location, event_description, event_start, event_end, event_all_day, event_repeat, event_repeat_interval, event_repeat_until, event_repeat_skip, event_sequence, event_created_at, event_updated_at, event_created_by, event_client_id, event_location_id, event_calendar_id, calendar_name.

Create

The answer has invited, how many it was emailed to.

curl -X POST https://itflow.example.com/api/v1/events/create.php \
  -H "Content-Type: application/json" \
  -d '{"api_key": "YOUR_API_KEY", "client_id": 1, "event_title": "Onsite - patch panel cleanup", "event_calendar_id": 2, "event_start": "2026-11-20 14:00", "event_end": "2026-11-20 16:00", "attendee_user_ids": [2], "attendee_contact_ids": [1], "send_invites": 1}'

Update, send, skip and delete

Each takes event_id and client_id.

• Update takes any of the fields under Create, and changes only what you send. client_id can move it to another client. Sending any of the attendee lists sets who is on it - a list you leave out stays. With send_invites, anyone new gets the invitation, those who have it get the change, and anyone taken off is told it's off for them. The answer has emailed.
• Send emails the invitation, as Email the invitation does: to those not sent it yet, and again, as an update, to those who were. ITFlow has to send mail.
• Skip takes date, one day of a repeating event to leave out, as Skip this one does. Those who have it get the series without that day.
• Delete tells those who have it in their calendar that it's off.

Trips

Anyone logs and changes their own trips. Seeing everyone's needs Read on Financial, logging or changing someone else's Modify, and deleting someone else's Full.

Read

Each trip has its driver_name and client_name. trip_miles is the whole trip - there and back for a round_trip.

Fields: trip_id, trip_date, trip_purpose, trip_source, trip_destination, trip_start_odometer, trip_end_odometer, trip_miles, round_trip, trip_own_vehicle, trip_expense_id, trip_billable, trip_invoice_id, trip_invoice_item_id, trip_created_at, trip_updated_at, trip_user_id, trip_client_id, trip_location_id, trip_ticket_id, trip_created_by, driver_name, client_name.

Create, update and delete

Update takes trip_id and changes only what you send. A trip paid back for keeps its driver, vehicle and distance, and one billed its client and distance. Delete takes trip_id, and a trip paid back for or billed can't be deleted. A field that won't do is refused with 400 and why in message.

{ "api_key": "YOUR_API_KEY", "client_id": 1, "trip_source": "Office", "trip_destination": "Ravenwood Dental, 410 Grant St", "trip_purpose": "Patch panel cleanup", "trip_miles": 12.3, "round_trip": 1, "trip_billable": 1 }