GraphQL Changes — Branch AINT-38

This document covers all GraphQL additions and changes introduced in this branch. The branch implements a full Engagement Events and Event Applications feature, including payment flows, attendance tracking, QR code ticket generation, comments, tags, and favourites.

Table of Contents

1. New Queries
2. New Mutations
3. New Objects
4. Modified Objects
5. New Input Types
6. New Enum Types

New Queries

engagementEvents

Returns a paginated list of engagement events, filterable by status, office, tags, favourites, etc.

Returns: EngagementEventList (paginated)

Arguments:

Example:

query {
  engagementEvents(
    filters: {
      statuses: [published]
      hostOfficeIds: [1, 2]
      tagIds: [10, 11]
      tagFilterOperator: "AND"
      my: "managed"
      isFavourited: false
    }
    pagination: { page: 1, perPage: 10 }
  ) {
    data {
      id
      title
      description
      status
      startTime
      endTime
      applicationDeadline
      location
      googlePlaceId
      contactInformation
      eventGuideline
      refundPolicy
      feeCents
      currency {
        id
        name
      }
      hostOffice {
        id
        name
      }
      managers {
        id
        fullName
      }
      engagementEventSpeakers {
        id
        name
        description
        profilePicture {
          url
        }
      }
      engagementEventDayActivities {
        id
        day
        title
        description
        startTime
        endTime
        engagementEventSpeakers {
          id
          name
        }
      }
      coverImage {
        url
      }
      comments {
        id
        body
      }
      tagLists {
        id
        name
      }
      isFavourited
      permissions {
        canPublish
        canUnpublish
        canUpdate
        canCreateComment
        canDeleteComment
        canManageTags
        canFavourite
      }
      createdAt
      updatedAt
    }
    paging {
      totalCount
      totalPages
      currentPage
    }
  }
}

engagementEvent

Fetches a single engagement event by ID.

Returns: EngagementEvent

Arguments:

Example:

query {
  engagementEvent(id: "42") {
    id
    title
    description
    status
    startTime
    endTime
    applicationDeadline
    location
    eventGuideline
    refundPolicy
    feeCents
    currency {
      id
      name
    }
    engagementEventSpeakers {
      id
      name
    }
    engagementEventDayActivities {
      id
      day
      title
    }
    permissions {
      canUpdate
      canPublish
      canCreateComment
      canFavourite
    }
  }
}

eventApplications

Returns a paginated, filterable list of event applications. Supports filtering by status, event, person, date range, and sorting.

Returns: EventApplicationList (paginated)

Arguments:

Example:

query {
  eventApplications(
    filters: {
      statuses: [in_review, accepted]
      engagementEventIds: [42]
      personIds: [101]
      startTime: { from: "2026-01-01", to: "2026-06-30" }
      endTime: { from: "2026-01-01", to: "2026-12-31" }
      my: "applied"
      sort: start_time
      sortDirection: DESC
    }
    pagination: { page: 1, perPage: 20 }
  ) {
    data {
      id
      status
      additionalDetails
      ticketId
      inReviewAt
      engagementEvent {
        id
        title
      }
      person {
        id
        fullName
      }
      cv {
        url
      }
      ticketPdf {
        url
      }
      qrCode {
        url
      }
      permissions {
        canUpdate
        canAccept
        canReject
        canConfirmPayment
        canWithdraw
        canDownloadTicket
        canAbsent
      }
      createdAt
      updatedAt
    }
    paging {
      totalCount
      totalPages
      currentPage
    }
  }
}

eventApplication

Fetches a single event application by ID.

Returns: EventApplication

Arguments:

Example:

query {
  eventApplication(id: "7") {
    id
    status
    ticketId
    ticketPdf {
      url
    }
    qrCode {
      url
    }
    permissions {
      canAccept
      canReject
      canWithdraw
      canDownloadTicket
    }
  }
}

New Mutations

createEngagementEvent

Creates a new engagement event. The current user is automatically set as creator and first manager. Speakers can be nested inline.

Returns: EngagementEvent

Arguments:

Example:

mutation {
  createEngagementEvent(
    engagementEvent: {
      title: "AIESEC Leadership Summit"
      description: "Annual leadership event"
      startTime: "2026-09-01T09:00:00Z"
      endTime: "2026-09-03T18:00:00Z"
      applicationDeadline: "2026-08-15T23:59:00Z"
      hostOfficeId: "5"
      location: "Cairo, Egypt"
      googlePlaceId: "ChIJxxxxxxxxx"
      contactInformation: "events@aiesec.org"
      eventGuideline: "Bring your student ID"
      refundPolicy: "Non-refundable"
      feeCents: 5000
      currencyId: "1"
      managerIds: ["101", "102"]
      coverImage: {
        content: "data:image/png;base64,..."
        filename: "cover.png"
      }
      engagementEventSpeakersAttributes: [
        {
          name: "Jane Doe"
          description: "Keynote speaker"
          profilePicture: {
            content: "data:image/png;base64,..."
            filename: "jane.png"
          }
        }
      ]
      engagementEventDayActivitiesAttributes: [
        {
          day: 1
          title: "Opening Ceremony"
          description: "Welcome and introductions"
          startTime: "2026-09-01T09:00:00Z"
          endTime: "2026-09-01T11:00:00Z"
          engagementEventSpeakerIds: ["1"]
        }
      ]
    }
  ) {
    id
    title
    status
  }
}

updateEngagementEvent

Updates an existing engagement event. Speakers and day activities support nested upsert/destroy via _destroy: true.

Returns: EngagementEvent

Arguments:

Example:

mutation {
  updateEngagementEvent(
    id: "42"
    engagementEvent: {
      title: "Updated Summit Title"
      feeCents: 7500
      engagementEventSpeakersAttributes: [
        { id: "3", _destroy: true }
        { name: "New Speaker", description: "New session" }
      ]
    }
  ) {
    id
    title
    feeCents
  }
}

inReviewEngagementEvent

Transitions an engagement event to in_review status, marking it ready for publishing approval.

Returns: EngagementEvent

Arguments:

Example:

mutation {
  inReviewEngagementEvent(id: "42") {
    id
    status
  }
}

publishEngagementEvent

Publishes an engagement event (must be in in_review status). Records published_at and published_by.

Returns: EngagementEvent

Arguments:

Example:

mutation {
  publishEngagementEvent(id: "42") {
    id
    status
  }
}

bulkAssignManagersForEvents

Bulk-assigns one or more managers to multiple engagement events. Only events the current user can update are affected.

Returns: [EngagementEvent]

Arguments:

Example:

mutation {
  bulkAssignManagersForEvents(ids: ["42", "43"], managerIds: [101, 102]) {
    id
    managers {
      id
      fullName
    }
  }
}

bulkUnassignManagersForEvents

Bulk-unassigns managers from multiple engagement events. Passing an empty managerIds removes all managers.

Returns: [EngagementEvent]

Arguments:

Example:

mutation {
  bulkUnassignManagersForEvents(ids: ["42", "43"], managerIds: [101]) {
    id
    managers {
      id
      fullName
    }
  }
}

createCommentForEngagementEvent

Creates a comment on an engagement event. The author is automatically set to the current user.

Returns: Comment

Arguments:

Example:

mutation {
  createCommentForEngagementEvent(
    engagementEventId: "42"
    comment: { body: "Looking forward to this event!" }
  ) {
    id
    body
  }
}

bulkTagUpdateForEngagementEvents

Replaces the tag list for multiple engagement events in bulk. Only events the current user can update are affected.

Returns: [EngagementEvent]

Arguments:

Example:

mutation {
  bulkTagUpdateForEngagementEvents(ids: [42, 43], tagListIds: [10, 11, 12]) {
    id
    tagLists {
      id
      name
    }
  }
}

favouriteEngagementEvent

Marks an engagement event as favourited by the current user.

Returns: EngagementEvent

Arguments:

Example:

mutation {
  favouriteEngagementEvent(id: "42") {
    id
    isFavourited
  }
}

unfavouriteEngagementEvent

Removes the current user's favourite from an engagement event.

Returns: EngagementEvent

Arguments:

Example:

mutation {
  unfavouriteEngagementEvent(id: "42") {
    id
    isFavourited
  }
}

createEventApplication

Creates a new event application for the current user. Automatically transitions to pending_payment for paid events or in_review for free events. Supports re-applying for a previously withdrawn application (once). CV can be provided as base64 upload or via an existing attachment ID.

Returns: EventApplication

Arguments:

Example (new application with CV upload):

mutation {
  createEventApplication(
    eventApplication: {
      engagementEventId: "42"
      additionalDetails: "I am very motivated to attend."
      cv: { content: "data:application/pdf;base64,...", filename: "my_cv.pdf" }
    }
  ) {
    id
    status
    ticketId
  }
}

Example (reuse existing CV by attachment ID):

mutation {
  createEventApplication(
    eventApplication: {
      engagementEventId: "42"
      additionalDetails: "I am very motivated to attend."
      cvId: "88"
    }
  ) {
    id
    status
  }
}

updateEventApplication

Updates an existing event application's details. Requires :update permission on the application.

Returns: EventApplication

Arguments:

Example:

mutation {
  updateEventApplication(
    id: "7"
    eventApplication: { additionalDetails: "Updated motivation statement." }
  ) {
    id
    additionalDetails
  }
}

acceptEventApplication

Accepts an event application in in_review status. On acceptance, a unique ticket_id is generated and a QR code + PDF ticket are generated asynchronously.

Returns: EventApplication

Arguments:

Example:

mutation {
  acceptEventApplication(id: "7") {
    id
    status
    ticketId
  }
}

rejectEventApplication

Rejects an event application in in_review status.

Returns: EventApplication

Arguments:

Example:

mutation {
  rejectEventApplication(id: "7") {
    id
    status
  }
}

withdrawEventApplication

Allows an applicant to withdraw their application while it is in applied, pending_payment, in_review, or accepted status.

Returns: EventApplication

Arguments:

Example:

mutation {
  withdrawEventApplication(id: "7") {
    id
    status
  }
}

confirmPaymentEventApplication

Confirms payment for an application in pending_payment status, advancing it to in_review.

Returns: EventApplication

Arguments:

Example:

mutation {
  confirmPaymentEventApplication(id: "7") {
    id
    status
  }
}

attendedEventApplication

Marks an accepted application as attended. The id can be either the application's database ID or its ticket_id string (used for QR scanning at event entry).

Returns: EventApplication

Arguments:

Example (by DB id):

mutation {
  attendedEventApplication(id: "7") {
    id
    status
  }
}

Example (by ticket_id via QR scan):

mutation {
  attendedEventApplication(id: "A3F9C2") {
    id
    status
    ticketId
  }
}

absentEventApplication

Marks an accepted application as absent.

Returns: EventApplication

Arguments:

Example:

mutation {
  absentEventApplication(id: "7") {
    id
    status
  }
}

New Objects

EngagementEvent

Represents an event managed by an AIESEC entity. Entirely new type added in this branch.

EngagementEventList

Paginated wrapper for EngagementEvent. New type added in this branch.

EngagementEventSpeaker

Represents a speaker associated with an engagement event. New type added in this branch.

EngagementEventDayActivity

Represents a scheduled activity within a day of the engagement event. New type added in this branch.

EventApplication

Represents a person's application to an engagement event, including ticket, CV, QR code, and permission state. New type added in this branch.

EventApplicationList

Paginated wrapper for EventApplication. New type added in this branch.

EventApplicationPermissionType

Granular permission flags for actions on an event application. New type added in this branch.

Modified Objects

EventPermission

Newly added fields:

No fields were removed.

New Input Types

EngagementEventInput

Input for creating or updating an engagement event.

EngagementEventSpeakerInput

Nested input for managing speakers. Supports create, update and destroy.

EngagementEventDayActivityInput

Nested input for managing day activities. Supports create, update and destroy.

EngagementEventFilterInput

Filter input for the engagementEvents query.

EventApplicationInput

Input for creating or updating an event application.

EventApplicationFilterInput

Filter input for the eventApplications query.

New Enum Types

EngagementEventStatus

Values are derived from the EngagementEvent model statuses:

EventApplicationStatus

Values are derived from the EventApplication model statuses:

EventApplicationSortOption

Extends BaseSortOption: