Skip to main content

Eventbrite to iPaaS.com Attendance Mapping Documentation

How each person's attendance at an Eventbrite event reaches iPaaS.com as a Ticket transaction, one line per ticket, with a status that follows check-ins and cancellations.

Summary

Each person's attendance at each Eventbrite event can be transferred TO iPaaS.com as an attendance record: an iPaaS.com transaction of type Ticket, with no amounts, on the person's own customer. It is sent automatically right after the person is sent as a customer, by the order and attendee webhooks or a Manual Sync. Each record holds one line per ticket the person holds for the event, written by the child collection Add/Update Eventbrite Attendance Ticket TO iPaaS.com, and its status follows the person's attendance: Pending while registered, Complete once checked in, Cancelled or Refunded.

ID Format

Manual Sync ID Format

Enter the Eventbrite event id and the person's email address joined by a vertical bar, under Transaction: {event id}|{email}, for example 2004666506485|pat@example.com. A record sent on its own this way holds only the tickets on the orders the person placed for the event. To refresh a record with every ticket, resend the person's attendee under Customer (the event id and attendee id joined by a vertical bar, for example 2004666506485|22902212229) or the order by its order number (for example 16096958843): the attendance record follows.

An ID in another form fails with an error. A value that is not an id at all gives "… is not an Eventbrite order id. Use the order number (for example 1234567890) or, for an attendee, "{event id}|{attendee id}"." That message does not show the attendance form: for an attendance record, enter the event id and the email as shown above. An attendee id sent where an order or attendance record belongs gives "… is an attendee id; an order is transferred by its order number, an attendance record by "{event id}|{email}"."

External ID Format

After a successful transfer, iPaaS.com saves {event id}|{email}, with the email lowercased, as the external ID on a dedicated external ID record, for example 2004666506485|pat@example.com. Later transfers of the same person at the same event find the record through it and update it instead of creating another. The same value is also mapped into TransactionNumber for visibility.

Each line of the Attendance Ticket child collection is saved with the event id and the attendee (ticket) id joined by a vertical bar, {event id}|{attendee id}, for example 2004666506485|22902212229, so a later transfer of the same attendance record updates the same line. The order's line for the same ticket is saved with the order number and the attendee id, for example 16096958843|22902212229, so the two lines never share a link. A line has no Manual Sync of its own: resend the attendee or the order, and the attendance record and its lines follow.

Deleted Record Support

Delete is not supported: this collection only adds and updates transactions, and nothing is deleted in iPaaS.com or in Eventbrite. When the person no longer holds a ticket for the event, the record stays in iPaaS.com with status Refunded (every ticket refunded) or Cancelled. In the orders observed when this documentation was written, Eventbrite recorded a cancelled free order as refunded, so a cancelled free registration becomes Refunded. A cancelled or refunded ticket keeps its line, with line status Cancelled or Refunded.

Custom Field Support

The default template writes three iPaaS.com transaction custom fields: Eventbrite Event Id, Eventbrite Event Name and Eventbrite Event Start (see the field table below).

Answers to the event's custom registration questions can be read with the EventbriteAnswer mapping function in a Dynamic Formula mapping, for example return EventbriteAnswer(Answers, "Dietary requirements");. The question is matched by its text, ignoring case, or by its Eventbrite question id; the function returns the answer as text, or an empty value when the question was not asked or not answered. On an attendance record the answers are those of the person's first ticket for the event. Subscribers should validate this behavior in a staging environment before relying on it in production. See Eventbrite Mapping Functions for the function.

More attendance values can be mapped with Field mappings, for example AttendanceState (the person's attendance before translation), ActiveTicketCount (tickets still held), AttendedTicketCount, EventTimezone, EventUrl and EmailOptIn. On an attendance record, BuyerName, BuyerFirstName, BuyerLastName and BuyerEmail hold the person's own name and email.

Mapping Collection Status

  • Status: Enabled. Turn the collection off to stop attendance records; orders and customers are not affected.

  • Trigger Events: an attendance record has no webhook scope of its own. It is sent right after its person is written as a customer. Every person transfer, whatever started it (a webhook scope, an initialization, an order's people or a Manual Sync), is followed by that person's attendance record for the event, unless no ticket at the event carries the person's email (cancelled and refunded tickets still count, giving a Cancelled or Refunded record), for example a buyer who bought tickets only for others. Subscribers or their MiSP turn these scopes on under the subscription's Inbound Data Flows; no automatic transfers occur until they are enabled. A record can also be sent on its own by Manual Sync.

  • Attendance Ticket (child): Enabled, with no trigger of its own: its lines are written with each attendance record. Turning the parent collection off stops them.

Duplicate or Conflicting Mappings

  • Add/Update Eventbrite Order TO iPaaS.com: orders and attendance records arrive through the same Eventbrite data. This collection's filter takes only records whose RecordKind is Attendance, and the order collection's filter takes the rest, so each record goes to exactly one of them. Keep both conditions: an order collection without its condition also takes attendance records and writes them as orders. An attendance record is separate from the order. The order's transaction, from Add/Update Eventbrite Order TO iPaaS.com, belongs to the buyer and carries the money; the attendance record belongs to the person who holds the tickets, guests included, and carries none, so revenue is counted once.

  • Other systems' transaction collections FROM iPaaS.com (a store, ERP, accounting or point-of-sale system) can pick up attendance records, because they are iPaaS.com transactions. Their type is Ticket, so a filter that takes only type Order already skips them. To skip every Eventbrite record, add this condition to those collections' filters: string.IsNullOrEmpty(Convert.ToString(GetCustomFieldValue(CustomFields, "Eventbrite Event Id"))). Keep the Eventbrite Event Id mapping in this collection: that condition relies on it. Subscribers should validate this behavior in a staging environment before relying on it in production.

  • Add/Update Eventbrite Order Ticket TO iPaaS.com writes a line for the same ticket on the order's transaction, with its price. The attendance line and the order's line have different external IDs, so they never overwrite each other, and only the order's line carries an amount. Keep UnitPrice and ExtendedPrice at 0 in the Attendance Ticket collection; mapping an amount there would count the ticket's revenue a second time.

Important: Review the filters of every transaction collection FROM iPaaS.com in the company before turning this collection on, and decide which system is the source of truth for event records.

Record Matching and Duplicates

This collection has no Collision Handling Method. The external ID record is what matches a person's record at an event: a repeated webhook, an initialization, or the same person arriving another way (as the order's buyer and as an attendee) updates the same record and never creates a second one. If another transaction already holds the same transaction number without being linked to this record, iPaaS.com refuses the transfer as a duplicate rather than linking to it. Keep one Eventbrite subscription per Eventbrite organization. Subscribers should validate this behavior in a staging environment before relying on it in production. The Attendance Ticket child collection has no Collision Handling Method either: each line is matched by its {event id}|{attendee id} link.

Unmapped Field Overwrite Risk

Warning — Unmapped Field Overwrite Risk: An update replaces the whole iPaaS.com transaction, lines included. The following transaction fields are not mapped in Add/Update Eventbrite Attendance TO iPaaS.com, so any value another system or a user has put in them on an attendance record is cleared each time the record transfers again:

  • Subtotal

  • TaxAmount

Attendance records carry no amounts, so both are 0 by design. The other unmapped fields (Id, ParentId and CompanyId) are identifiers iPaaS.com manages. The template already keeps the existing value for DiscountAmount and ShippingAmount; keep those two formulas, because removing one sets that amount to 0 on every update. The following line fields are not mapped in Add/Update Eventbrite Attendance Ticket TO iPaaS.com, so any existing value in them on an attendance line is cleared each time the attendance record transfers again:

  • DiscountAmount

  • DiscountPercent

  • EstimatedTaxAmount

  • LineInfo

  • OriginalUnitPrice

  • QtyShipped

  • SequenceNumber

  • TaxPercent

  • Weight

If another system or a user fills any of these record or line fields, add a Dynamic Formula mapping to the collection that writes it, keeping the existing value with the DestinationValue function, in the same form as the DiscountAmount and ShippingAmount mappings: for example return DestinationValue != null ? DestinationValue.Subtotal : 0; for Subtotal in this collection, or return DestinationValue != null ? DestinationValue.DiscountAmount : 0; for a line's DiscountAmount in the Attendance Ticket collection. Subscribers should validate this behavior in a staging environment before relying on it in production.

Supported Child Collections

  • Add/Update Eventbrite Attendance Ticket TO iPaaS.com: one line for each ticket the person holds for the event, with that ticket's attendance as the line status and no amounts. Lines are written with their attendance record and are never transferred on their own. Each line has quantity 1, names the one event-ticket product set in its Sku mapping, and carries the ticket type, the attendee's name and email, the ticket's attendance and whether it was checked in. Each line is linked as {event id}|{attendee id}. Its mappings are in the Add/Update Eventbrite Attendance Ticket TO iPaaS.com (Child) section below. You must set one value before turning it on: its Sku mapping holds REPLACE with your event ticket SKU; replace it with the SKU of your iPaaS.com event-ticket product, the same one as in Add/Update Eventbrite Order Ticket TO iPaaS.com.

System Caveats

Eventbrite Caveats

  • Attendance across tickets: the person is Attended when any ticket they still hold was checked in or its barcode was used; otherwise Registered while they hold any ticket; otherwise Refunded when every ticket was refunded; otherwise Cancelled.

  • Check-in, undo and check-out: a check-in makes the record Complete. Undoing a check-in, and checking an attendee out in Eventbrite's organizer screens, both reset the ticket in Eventbrite in the check-ins observed when this documentation was written (checked in false, barcode unused), and the record returns to Pending while the person holds the ticket. The two look the same to iPaaS.com. If Eventbrite still reports the barcode as used after a check-out, the ticket still counts as attended.

  • Ticket attendance (lines): a ticket is Refunded when Eventbrite marks it refunded; otherwise Cancelled when it was cancelled or Eventbrite reports it as not attending or deleted; otherwise Attended when it was checked in or its barcode was used; otherwise Registered. A check-in makes the line Complete with Eventbrite Checked In true; an undo or a check-out that resets the ticket returns it to Pending with Eventbrite Checked In false.

  • Cancellations: cancelling one of several tickets returns the person to Registered while they hold another ticket at the event; the cancelled ticket's line becomes Refunded when Eventbrite refunds it. In the orders observed when this documentation was written, Eventbrite recorded a cancelled free order as refunded, so the record becomes Refunded when that was the person's only order for the event.

  • Which tickets the record holds: the tickets the person's transfer just read, plus the tickets on the orders the person placed for the event. The integration finds the person's orders by the email of the person who placed them, so a ticket someone else bought for the person is included when the person is sent from that order or ticket, but not when the record is sent on its own later. To refresh a record with every ticket, resend the attendee or the order.

  • Buyer-only events: as the Eventbrite API reference describes (Attendee object), when an event collects details from the buyer only, every ticket carries the buyer's email, so all of them are on the buyer's record and guests have none of their own.

  • Rate limiting: Eventbrite allows a default of 2,000 API calls per hour per private token, shared by everything that uses the token. When the limit is reached, iPaaS.com holds the transfer and sends it automatically once the hour resets; no subscriber action is required. An attendance record adds little Eventbrite traffic, because it reuses what the person's transfer read moments before.

iPaaS.com Caveats

  • Event-ticket product: every line needs an existing iPaaS.com product. Until the Sku mapping of the Attendance Ticket collection names one, every attendance record is refused with NFND-1003, while the people are still sent as customers. A line that fails fails its whole attendance record.

  • One product for every ticket: every line uses the product set in Sku. The ticket type travels in the line's Description and in Eventbrite Ticket Class.

  • The person comes first: the record is sent right after its person is written as a customer, and its CustomerId formula finds that customer by email. A person with no email address is not sent as a customer, so they have no attendance record. A buyer who holds no ticket in their own email for the event has no attendance record either.

  • One record per email per event: the email is part of the transaction number. People who share an email share one record, and a person whose email changes gets new records under the new email.

  • The chain ends here: an attendance record starts no further transfers.

  • Event Start format: at the time this documentation was written, Eventbrite Event Start appears in iPaaS.com as a US-formatted date and time (for example 03/15/2027 10:00:00), not in ISO 8601 form. It is in the event's local time, with no time zone.

Setup Requirements

For the full setup steps see Eventbrite Installation Instructions and Eventbrite Connections and Settings. For attendance records:

  • Attendee collection: set up and turn on Add/Update Eventbrite Attendee TO iPaaS.com. Attendance records follow each person.

  • Event-ticket product: create one iPaaS.com product for event tickets, for example SKU EVENT-TICKET or GA-ADMISSION, or use an existing product. Use the same product as for the order lines of Add/Update Eventbrite Order Ticket TO iPaaS.com.

  • Replace the SKU: in Add/Update Eventbrite Attendance Ticket TO iPaaS.com, edit the Sku mapping and replace REPLACE with your event ticket SKU with that product's SKU, exactly as it is in iPaaS.com.

  • Webhook scopes: turn on the order and attendee scopes you use for people under Inbound Data Flows. No extra scope is needed for attendance records.

  • Exclusion filter: add the Eventbrite exclusion condition to every transaction collection FROM iPaaS.com that must not receive event records. Subscribers should validate this behavior in a staging environment before relying on it in production.

Integration Flow

  1. A person is sent: an order or attendee webhook or a Manual Sync sends a person TO iPaaS.com as a customer.

  2. The attendance record follows: Right after the person is written, the integration sends that person's attendance record, {event id}|{email}. Every person transfer, whatever started it (a webhook scope, an initialization, an order's people or a Manual Sync), is followed by that person's attendance record for the event, unless no ticket at the event carries the person's email (cancelled and refunded tickets still count, giving a Cancelled or Refunded record), for example a buyer who bought tickets only for others. A Manual Sync can also send the record directly.

  3. Tickets are gathered: The integration takes the person's tickets at the event that the person's transfer just read, and reads the orders the person placed for the event. When no ticket carries the email, nothing is written.

  4. Attendance is worked out: across those tickets: Attended, else Registered, else Refunded when every ticket was refunded, else Cancelled.

  5. The lines are built: Each ticket becomes one line of the Attendance Ticket child collection, with quantity 1 and no amounts, linked as {event id}|{attendee id}, with its own attendance: Refunded, else Cancelled, else Attended, else Registered.

  6. The record is mapped and written: The record goes through this collection's filter and mappings and each line through the child collection's mappings, and the transaction is written TO iPaaS.com with its lines as an Add or an Update, found by its external ID.

  7. The chain ends: The attendance record starts no further transfers.

Mappings

Add/Update Eventbrite Attendance TO iPaaS.com

iPaaS.com data type: Transaction

Mapping Filter:

// Event Attendance records only: orders go to the Order collection.return RecordKind == "Attendance";

Filter Description: the filter passes a record when its RecordKind is Attendance (an attendance record) and skips every other record, which is an order and belongs to Add/Update Eventbrite Order TO iPaaS.com. A skipped record logs no error. Keep this condition in any filter you write for this collection.

Description: writes each person's attendance at each event as a Ticket transaction with no amounts on the person's own customer.

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Dynamic Formula

SpaceportSystemId

SystemId

Required. Links the transaction to this subscription. Do not change it.

Field

Id

TransactionNumber

Required. The event id and the person's lowercased email joined by a vertical bar: one record per person per event. iPaaS.com keeps the same value on the external ID record, which is how later transfers find this record; this field is mapped for visibility and is what the duplicate check compares.

Static

"Ticket"

Type

Required. Sets attendance records apart from orders (type Order). Keep the value Ticket. Allowed values: Order, Shipment, Invoice, Hold, Quote, Ticket, Return, Validated Return, Job and Fulfillment.

Lookup Translation

Lookup Translation: Eventbrite Attendance -> iPaaS.com Transaction Status

Status

Required. The person's attendance at the event translated to a status (table below).

Field

BuyerEmail

EmailAddress

Required. iPaaS.com needs an email address on a transaction that has no customer. The attendee's own email address, lowercased; on an attendance record, BuyerEmail holds the attendee's email.

Dynamic Formula

return await EventbriteCustomerId(BuyerEmail);

CustomerId

Required. Keep this mapping: the integration uses it to link the attendance record to the person's own customer in iPaaS.com, the iPaaS.com customer with the attendee's email, matched ignoring case. The value itself can be empty: when no customer, or more than one customer, has the email, it is left empty and the record is written with its email address only.

Dynamic Formula

return DestinationValue != null ? DestinationValue.DiscountAmount : 0;

DiscountAmount

Required. Keeps the discount amount the transaction already has, else 0; an attendance record carries no amounts (the order's discount is on the order's transaction). Removing it sets the amount to 0 on every update.

Dynamic Formula

return DestinationValue != null ? DestinationValue.ShippingAmount : 0;

ShippingAmount

Required. Keeps the shipping amount the transaction already has, else 0. Removing it sets the amount to 0 on every update.

Field

Gross

Total

Optional. Always 0: the money is on the order's transaction.

Field

TicketCount

TotalQty

Recommended. The number of the person's tickets for the event on the record, one per line, including any later cancelled or refunded.

Dynamic Formula

return string.IsNullOrEmpty(Created) ? (DateTimeOffset?)null : DateTimeOffset.Parse(Created, System.Globalization.CultureInfo.InvariantCulture, System.Globalization.DateTimeStyles.AssumeUniversal);

TransactionCreatedDateTime

Recommended. When the person's earliest ticket for the event was created in Eventbrite (UTC). Empty when Eventbrite gives no date.

Dynamic Formula

return string.IsNullOrEmpty(Changed) ? (DateTimeOffset?)null : DateTimeOffset.Parse(Changed, System.Globalization.CultureInfo.InvariantCulture, System.Globalization.DateTimeStyles.AssumeUniversal);

TransactionUpdatedDateTime

Optional. When one of the person's tickets for the event last changed in Eventbrite (UTC).

Field

EventId

Eventbrite Event Id (Custom Field)

Required. Do not remove or rename it. The Eventbrite event id. It marks the transaction as an event record; the exclusion filter relies on it.

Field

EventName

Eventbrite Event Name (Custom Field)

Recommended. The event's name.

Field

EventStart

Eventbrite Event Start (Custom Field)

Recommended. At the time this documentation was written, Eventbrite Event Start appears in iPaaS.com as a US-formatted date and time (for example 03/15/2027 10:00:00), not in ISO 8601 form. It is the event's local start date and time, with no time zone. Add a Field mapping of EventTimezone to a custom field when receiving systems need the time zone.

Lookup Translation Tables

Eventbrite Attendance -> iPaaS.com Transaction Status

Source Value (Eventbrite)

Destination Value (iPaaS.com)

Notes

Registered

Pending

The person holds at least one ticket and none of their held tickets was checked in or had its barcode used.

Attended

Complete

A ticket the person holds was checked in or its barcode was used.

Cancelled

Cancelled

The person holds no ticket, and not every ticket was refunded.

Refunded

Refunded

Every ticket the person had was refunded, including a cancelled free order.

Subscribers or their MiSP can change the destination values to the statuses their other systems expect. The translation has no default row. Keep a row for each of the four values. A value with no translation row is refused by iPaaS.com: nothing is written, the transfer is refused, and Dashboard / Integration Monitoring / Error Logs shows an error that includes "VALD-1024 - Required property 'status' not found in JSON" with a link to the iPaaS.com help article Request body errors. To fix it, restore the translation row and resend the attendee or the order from Manual Sync.

Add/Update Eventbrite Attendance Ticket TO iPaaS.com (Child)

iPaaS.com data type: Transaction Line

Description: writes each ticket the person holds for the event as one line of the attendance record, as part of the parent's transfer. Lines are never transferred on their own. Each line is saved with the event id and the attendee id joined by a vertical bar as its external ID link, for example 2004666506485|22902212229. This collection has no mapping filter: every ticket on the attendance record becomes a line, including cancelled and refunded tickets.

Mapping Type

Source Field (Eventbrite)

Destination Field (iPaaS.com)

Description

Static

"Product"

Type

Required. Each ticket is a line of type Product, naming the event-ticket product set in Sku. Keep the value Product. Allowed values: Product, Gift Card and Donation.

Static

"REPLACE with your event ticket SKU"

Sku

Required. Placeholder value — replace during implementation. Replace with the SKU of the iPaaS.com product you use for event tickets, for example EVENT-TICKET or GA-ADMISSION, or the SKU of an existing product. The product MUST exist before the first transfer, or every attendance record is refused with NFND-1003 (see the note below the table).

Lookup Translation

Lookup Translation: Eventbrite Ticket Attendance -> iPaaS.com Line Status

Status

Required. The ticket's attendance translated to a line status (table below).

Field

TicketClassName

Description

Recommended. The ticket type's name, for example General Admission or VIP.

Field

Quantity

Qty

Required. Always 1: each ticket is one line, so keep this mapping for every line to carry its quantity.

Field

BasePrice

UnitPrice

Optional. Always 0 on attendance lines: the price is on the order's line.

Field

BasePrice

ExtendedPrice

Optional. Always 0 on attendance lines.

Field

AttendanceState

Eventbrite Attendee Status (Custom Field)

Recommended. The ticket's attendance before translation: Attended, Registered, Cancelled or Refunded.

Dynamic Formula

return Attended ? "true" : "false";

Eventbrite Checked In (Custom Field)

Recommended. true when Eventbrite reports the ticket as checked in or its barcode as used, else false. Becomes false again after an undo of the check-in or a check-out that resets the ticket (see Eventbrite Caveats).

Field

AttendeeEmail

Eventbrite Attendee Email (Custom Field)

Recommended. The email on the ticket, lowercased: the person's own email on an attendance record.

Field

AttendeeName

Eventbrite Attendee Name (Custom Field)

Recommended. The name on the ticket.

Field

TicketClassName

Eventbrite Ticket Class (Custom Field)

Optional. The ticket type's name, the same value as Description.

Placeholder value — replace during implementation: the Sku mapping ships with the instruction text "REPLACE with your event ticket SKU". Replace it with the SKU of the iPaaS.com product you use for event tickets, exactly as it is in iPaaS.com, for example EVENT-TICKET or GA-ADMISSION, or the SKU of an existing product in your iPaaS.com catalog.

Pre-install prerequisite — the transfer fails without it. iPaaS.com refuses a line whose SKU is not an existing iPaaS.com product. EITHER (a) create a product in iPaaS.com with the SKU you choose and put that SKU in the Sku mapping, OR (b) put the SKU of a product that already exists in your iPaaS.com catalog in the mapping. One of these MUST be done at install time. Until then, every attendance record fails with an error of this form in Dashboard / Integration Monitoring / Error Logs: "NFND-1003 - Product Id: REPLACE with your event ticket SKU does not exist or can not be found." The people are still sent as customers. Put the same SKU in Add/Update Eventbrite Order Ticket TO iPaaS.com.

Lookup Translation Tables

Eventbrite Ticket Attendance -> iPaaS.com Line Status

Source Value (Eventbrite)

Destination Value (iPaaS.com)

Notes

Attended

Complete

The ticket was checked in or its barcode was used.

Registered

Pending

The ticket is held and not checked in.

Cancelled

Cancelled

The ticket was cancelled, or Eventbrite reports it as not attending or deleted, without a refund.

Refunded

Refunded

Eventbrite marks the ticket refunded, including a cancelled free order or a ticket cancelled on a free event.

Subscribers or their MiSP can change the destination values to the line statuses their other systems expect. The translation has no default row. Keep a row for each of the four values. Status is required on every transaction line, so a value with no translation row is refused by iPaaS.com: nothing is written, the transfer is refused, and Dashboard / Integration Monitoring / Error Logs shows an error that includes "VALD-1024 - Required property 'status' not found in JSON" with a link to the iPaaS.com help article Request body errors. To fix it, restore the translation row and resend the attendee or the order from Manual Sync. Subscribers should validate this behavior in a staging environment before relying on it in production.

Error Handling

Errors from this collection appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs; warnings appear in the transfer's activity log and do not fail the transfer. The full list of the integration's error codes and their resolutions is in the Eventbrite Error Messages article. An attendance record is sent as part of its person's transfer, so its error row carries the person's scope (for example order.updated) and names the record by {event id}|{email}. The person's own customer is still written. The messages most often seen with attendance records (integration error codes are omitted):

  • "NFND-1003 - Product Id: REPLACE with your event ticket SKU does not exist or can not be found.": a line's Sku is not an existing iPaaS.com product, so iPaaS.com refuses the whole attendance record. Resolution: create the event-ticket product and put its SKU in the Sku mapping of the Attendance Ticket collection, then resend the attendee or the order from Manual Sync.

  • "… is not an Eventbrite order id. Use the order number (for example 1234567890) or, for an attendee, "{event id}|{attendee id}"." or "… is an attendee id; an order is transferred by its order number, an attendance record by "{event id}|{email}".": a Manual Sync ID is neither an order number nor {event id}|{email} (or an attendee id was sent where an order or attendance record belongs). Resolution: enter the event id and the person's email joined by a vertical bar, or resend the attendee instead.

  • "VALD-1024 - Required property 'status' not found in JSON. …": a status value has no row in the record's status translation (see the translation tables); nothing is written. Resolution: restore the translation row, then resend the attendee or the order from Manual Sync.

  • No record, no error: a person with no email address is not sent as a customer, and a person with no ticket under their email at the event has no attendance state, so no attendance record is sent for them and nothing is written. Resolution: check the person's email in Eventbrite, then resend the attendee from Manual Sync.

  • "Eventbrite's hourly API limit was reached during …; the transfer resumes at … UTC.": the first gap names what the integration was reading (for example, reading Eventbrite order 16096958843) and the second the date and time, in UTC, when the limit resets (for example, 2026-12-20 15:00). Eventbrite's hourly call limit for the private token was reached. Resolution: no action is needed; iPaaS.com holds the transfer and sends it automatically at the time shown.

Testing & Validation

Test Scenarios

  1. Register for an event with a free ticket. Verify a transaction whose TransactionNumber is the event id and your email: Type Ticket, Status Pending, your CustomerId, Total 0, Eventbrite Event Id, Eventbrite Event Name and Eventbrite Event Start, and one line.

  2. Buy two tickets in one order for yourself and a guest with a different email, on an event that collects details from each attendee. Verify the guest has their own record on the guest's own customer, and yours holds only your ticket.

  3. Register the same person for a second event. Verify a second record on the same customer.

  4. Check the attendee in. Verify the record's Status becomes Complete. Undo the check-in and verify it returns to Pending.

  5. Cancel a free order. Verify the person's record becomes Refunded and the customer is kept.

  6. Resend the attendee from Manual Sync. Verify the same record is updated, not a second one.

  7. Verify the order collection wrote no transaction with the attendance record's TransactionNumber, and that the attendance record's Total, Subtotal and TaxAmount are 0.

  8. On the line of scenario 1, verify Type Product, your event-ticket Sku, the ticket type as Description, Qty 1, UnitPrice 0, Eventbrite Attendee Status Registered and Eventbrite Checked In false; after the check-in of scenario 4, verify the line is Complete with Eventbrite Checked In true.

  9. Hold two tickets for the same event on two orders you placed. Verify your attendance record has two lines.

  10. Cancel one ticket of a multi-ticket order. Verify that line becomes Refunded and the other lines are unchanged.

  11. Send the attendance record on its own from Manual Sync under Transaction with {event id}|{email}. Verify the same record is updated and holds the tickets on the orders the person placed for the event.

  12. Leave the Attendance Ticket Sku as the default value on a test subscription and verify the record is refused with NFND-1003, then set the SKU and verify the record lands.

Validation Checklist

  • The event-ticket product exists in iPaaS.com and its SKU is in the Attendance Ticket collection's Sku mapping.

  • This collection's filter keeps the RecordKind Attendance condition, and the order collection's filter keeps its opposite.

  • Every transaction collection FROM iPaaS.com that must not receive event records has the Eventbrite exclusion condition.

  • The record and line Status translations list the statuses your other systems expect, each with a row for every one of the four values.

  • The Attendance Ticket Sku is the same as in Add/Update Eventbrite Order Ticket TO iPaaS.com, and UnitPrice and ExtendedPrice stay at 0.

  • The DiscountAmount, ShippingAmount and Eventbrite Event Id mappings are in place.

Additional Notes

Known Limitations

  • Not instant: at the time this documentation was written, a check-in reaches iPaaS.com within a few minutes of Eventbrite reporting it, not at the door.

Out of Scope

  • Writing to Eventbrite: nothing is written to Eventbrite.

  • Amounts: totals and line prices are 0 on every attendance record. Event revenue, as Eventbrite reports it, is on the order's transaction.

  • Per-ticket products: ticket types are not mapped to separate iPaaS.com products.

Related Documents

Related Mapping Documentation

External References

Did this answer your question?