account_balance_get
ChatGPTGet the signed-in account's Mazoom credit balance. Adding a guest to an event uses one credit (and, on some accounts, one per companion). Test invitations, and reminders or thank-you messages after each guest's free one, also use credits.
account_confirmation_status_get
ChatGPTCheck whether the signed-in account is confirmed. Mazoom requires a confirmed account to create events; accounts that signed up with a phone number are confirmed automatically.
account_profile_get
ChatGPTGet the signed-in account's profile: name, email, phone, language, credit balance, and whether it has premium.
account_profile_update
ChatGPTChange the signed-in account's name, sign-in email, or language. Fields you leave out stay the same. Changing the email changes the address used to sign in. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
attendance_guest_get
ChatGPTGet a guest's check-in details for an event: how many people they may bring, how many confirmed, and how many are already checked in.
contacts_create
ChatGPTSave one person to the signed-in account's address book. This doesn't add them to any event. If the number belonged to a deleted contact, that contact comes back with these details.
contacts_import
ChatGPTSave many people to the address book at once, from rows typed in the conversation or from a spreadsheet. It runs in the background: new contacts appear in contacts_list within a minute. People already saved with the same phone or email are skipped. This doesn't add anyone to an event. Provide exactly one of: rows, file_url, file_upload. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
contacts_list
ChatGPTList and search the signed-in account's saved contacts (address book). These aren't the guests of a particular event; use event_guests_list for those.
contacts_update
ChatGPTChange a saved contact's name, title, phone or email. Fields you leave out keep their current values. The change shows wherever this person is a guest.
event_guests_add
ChatGPTAdd one person to an event's guest list, or update them if their number is already on it. A new guest uses Mazoom invitation credits: one for the guest, and possibly one per companion depending on the account's settings. No invitation is sent. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
event_guests_import_contacts
ChatGPTAdd people from the signed-in account's address book to an event's guest list. Each person new to the event uses one Mazoom invitation credit; people already on it are skipped at no charge. No invitation is sent. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
event_guests_import_file
ChatGPTAdd many guests to an event at once, from rows typed in the conversation or from a spreadsheet. It runs in the background: guests appear in event_guests_list within a minute. Each person new to the event uses one Mazoom invitation credit, and the whole import is refused if the balance can't cover it. No invitation is sent. Provide exactly one of: rows, file_url, file_upload. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
event_guests_list
ChatGPTList an event's guests with their RSVP and delivery state. guest_list_state is the simplest way to filter: not_sent, sending, sent, delivered, read, waiting (invited, no reply yet), confirmed, declined, scanned (checked in) or failed.
event_guests_quantity_update
ChatGPTSet how many companions (0 to 10) and which seating zone chosen guests have. Guests who already confirmed are messaged on WhatsApp to confirm again, which uses their free reminder or 1 credit; that part is refused unless this connector may message guests. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
event_guests_quantity_update_all
ChatGPTGive every guest on an event the same companion allowance (0 to 10), including guests who already confirmed. Nobody is messaged. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
event_guests_update
ChatGPTChange one guest's name, title, phone or email, or their companions and seating zone. Fields you leave out stay the same. Name, phone and email changes apply to the person's contact, so every event they're on shows them. Changing the companions of a guest who already confirmed messages them to confirm again, so it's refused unless this connector may message guests.
events_copy
ChatGPTCreate a regular, invitation-only copy of an open event, with everyone who registered added as a guest who hasn't been invited yet. Works only for open events. No credits are used and nothing is sent.
events_create
ChatGPTCreate an event without an invitation image, for example while the design isn't ready. Add the image with events_repair_complete before sending invitations. To create a ready-to-send event in one step, use events_create_complete. Nothing is sent to guests.
events_create_complete
ChatGPTCreate a ready-to-send event in one step: save the details, upload the invitation image, attach it, and check that the saved date, venue and map location match. Nothing is sent to guests. Provide exactly one of: image_url, image_upload.
events_design_upsert
ChatGPTSet an event's invitation design: its image (pattern_id), border, logo, background colour and opacity. Fields you leave out keep their current values. Get pattern_id from events_image_upload or events_patterns_list.
events_get
ChatGPTGet one event's details: name, host, date and time, venue and map location, invitation design and message texts, settings, and guest counts by RSVP and delivery state.
events_image_upload
ChatGPTUpload a JPG or PNG to use as an event's invitation image and return its Mazoom file ID. Images larger than 300 KB are converted to a web-sized JPEG first. To attach it, pass the returned id as pattern_id to events_design_upsert. Provide exactly one of: image_url, image_upload.
events_list
ChatGPTList events the signed-in account hosts, with each event's ID, name, date and guest counts. Use timeframe to get upcoming or past events.
events_patterns_list
ChatGPTList Mazoom's ready-made invitation backgrounds (patterns) and borders. Pass an id as pattern_id or border_id to events_design_upsert.
events_premium_status_get
ChatGPTCheck whether an event is on Mazoom's premium plan.
events_preview_get
ChatGPTGet the WhatsApp message texts this account's invitations use, in English and Arabic: the invitation, and the replies guests get when they accept or decline. For one event's texts, use events_get.
events_received_list
ChatGPTList the invitations the signed-in user has received as a guest, split into upcoming and past, with each event's date, place and the user's RSVP.
events_repair_complete
ChatGPTReplace an existing event's date and time, venue, map location and invitation image, then check that it is ready to send. Other event settings are kept. Nothing is sent to guests. Provide exactly one of: image_url, image_upload.
events_update
ChatGPTChange an event's details. Only the fields you provide change; everything else is kept. Nothing is sent to guests. When the event's date, time or venue changes after invitations have gone out, it runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
gallery_events_list
ChatGPTList event photo galleries (Mazoom POV) that the signed-in user has joined or uploaded to, with photo counts.
gallery_photo_upload
ChatGPTAdd a photo to an event's photo gallery. Uploads open on the event's date, and each plan allows a set number of photos per event. Provide exactly one of: image_url, image_upload.
gallery_photos_list
ChatGPTList photos in an event's photo gallery, with each photo's link, caption and uploader's name.
gallery_settings_update
ChatGPTAllow or stop guests uploading photos to an event's photo gallery (Mazoom POV). Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
invitations_send_all
ChatGPTSend the event's invitation to every guest who hasn't received it and hasn't replied: by WhatsApp, and by email to guests with an email address. Guests whose delivery failed are tried again. No credits are used; they were used when guests were added. This messages real people. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
invitations_send_bulk
ChatGPTSend the event's WhatsApp invitation to the chosen guests, none of whom may have received it already. No credits are used; they were used when guests were added. This messages real people. The event and guests are checked first, as in invitations_send_preflight. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
invitations_send_preflight
ChatGPTCheck whether an event and the chosen guests are ready for invitations: date, venue, map location, invitation image, and each guest's eligibility. Sends nothing, and also reports the account's credit balance.
invitations_send_single
ChatGPTSend the event's WhatsApp invitation to one guest who hasn't received it yet. No credits are used. This messages a real person. The event and guest are checked first, as in invitations_send_preflight. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
invitations_send_test
ChatGPTSend a test of the event's WhatsApp invitation to one phone number, usually the host's own, addressed to the name given. Uses 1 credit when it's delivered. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
invitations_send_undelivered_qr
ChatGPTResend entry QR codes by WhatsApp, in Arabic, to guests whose QR code failed or isn't marked delivered yet, so some guests may get a second copy. No credits are used. This messages real people. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
invitations_test_status_get
ChatGPTGet whether the latest test invitation for an event was sent, delivered or read, or why it failed. Returns an error if no test has been sent.
messages_conversation_get
ChatGPTRead the WhatsApp messages exchanged with one guest, across all of the signed-in account's events.
messages_list
ChatGPTList the signed-in account's events with guests' latest WhatsApp messages and unread counts. In each conversation, contact.id is the guest's contact ID for messages_conversation_get and messages_send.
messages_mark_all_read
ChatGPTMark all messages from one guest as read. The guest sees WhatsApp read receipts on their latest message. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
open_events_options_create
ChatGPTAdd a choice to a list question (type 1) on an open event. A question can have up to 10 choices.
open_events_options_list
ChatGPTList the answer choices for one open-event registration question.
open_events_options_update
ChatGPTChange the text or position of one answer choice.
open_events_questions_create
ChatGPTAdd a question people must answer when they register for an open event. Accounts without premium can have one question per event; premium accounts can have up to 10. For a list question (type 1), include the options.
open_events_questions_list
ChatGPTList the questions people answer when they register for an open event.
open_events_questions_update
ChatGPTChange a registration question's text, type or position. Its answer options stay as they are; change them with the option tools.
open_events_registration_settings_update
ChatGPTChoose what people must give when they register for an open event: an email address, and how many companions they're bringing, up to a maximum.
qr_designs_create
ChatGPTCreate an entry QR card design: where the guest's name, the number of guests and the QR code appear on the card, and how they look. Positions and sizes are percentages of the card image. Then upload the card image with qr_designs_upload_image; a design without an image is removed the first time it's used.
qr_designs_get
ChatGPTGet one saved entry QR card design, including the position and style of each element.
qr_designs_image_get
ChatGPTGet the background image of a saved entry QR card design.
qr_designs_list
ChatGPTList the entry QR card designs saved in the signed-in account, with where each shows the guest's name, the number of guests and the QR code.
qr_designs_update
ChatGPTReplace a saved entry QR card design's layout. Send the full design: every block you leave out is removed.
qr_designs_upload_image
ChatGPTUpload the background image for a saved entry QR card design, replacing any current image. Provide exactly one of: image_url, image_upload.
reminders_preview_get
ChatGPTShow the reminder message guests of an event would receive. Sends nothing.
reminders_send
ChatGPTSend a WhatsApp reminder to chosen guests or all guests: reminder_type 0 is a reminder with the location, 1 asks guests to accept or decline, 2 is an event-day message with each guest's entry QR code and event_date_text. Each guest's first reminder is free; later ones use 1 credit each. all_guests includes guests who declined, and sending again messages the same people again. Provide exactly one of: guest_ids, all_guests. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
reminders_send_confirmed_qr
ChatGPTSend entry QR codes by WhatsApp, with the date text you give, to chosen guests or, with all_confirmed, to every guest who confirmed. Each guest's first reminder is free; later ones use 1 credit each. This messages real people. Provide exactly one of: guest_ids, all_confirmed. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.
reports_attendance_summary
ChatGPTCount how many guests and people have checked in to an event.
reports_delivery_summary
ChatGPTCount an event's WhatsApp invitations and QR codes by delivery state: unsent, sent, delivered, read and failed.
reports_event_summary
ChatGPTSummarise an event: guest and people counts, RSVP status counts, invitation and QR delivery, and attendance.
thank_you_preview_get
ChatGPTShow the thank-you message guests of an event would receive. Sends nothing.
thank_you_send
ChatGPTSend a WhatsApp thank-you with your own text, up to 255 characters, to chosen guests, using the event's invitation image. Each guest's first thank-you is free; repeats cost 1 credit each, charged straight away. This messages real people. Runs in two steps so the user can approve it: the first call changes nothing and returns a summary with a confirmation_token, and calling again with the same input and that token carries it out.