Auctria Zapier API & Webhooks

Auctria Zapier API & Webhooks

API and webhook documentation for connecting Auctria event activity to Zapier workflows.

The Auctria Zapier integration lets an authenticated Auctria organization connect event activity to Zapier. Zapier subscribes to Auctria webhook events, receives signed webhook deliveries through Svix, and uses the event payload to start automated workflows in other applications.

Integration summary

• Zapier app type: Trigger-only webhook integration
• Authentication: Custom auth with an application ID and integration key
• Delivery provider: Svix signed webhooks
• Primary use: Start Zaps when fundraising event records are created in Auctria

---

Authentication

The Zapier integration uses custom authentication. Auctria users load the required values from their Auctria organization automation settings and paste them into Zapier when connecting the Auctria app.

Zapier field	Type	Required	Description
application_id	string	Yes	The Svix application ID for the connected Auctria organization.
integration_key	password	Yes	The secret integration key Zapier uses to manage webhook subscriptions.

---

Webhook events

Each supported Auctria webhook event is available as a separate Zapier trigger. Supported events may expand over time; integrations should use the event type value in each payload to identify the event that was delivered.

participant.registered

Triggers when a new participant is added to an Auctria event.

Field	Value
Auctria change	Insert Participant
Primary payload object	payload.participant
Common fields	id, type, createdAt, organization, event, payload
Selected output fields	Participant ID, number, first name, last name, email, phone number, and address fields.

item.added

Triggers when a new auction item is added to an Auctria event.

Field	Value
Auctria change	Insert Item
Primary payload object	payload.item
Common fields	id, type, createdAt, organization, event, payload
Selected output fields	Item ID, number, title, description, type, and value.

transaction.added

Triggers when a new transaction is recorded in an Auctria event.

Field	Value
Auctria change	Insert Transaction
Primary payload object	payload.transaction
Common fields	id, type, createdAt, organization, event, payload
Selected output fields	Transaction ID, amount, quantity, origin, notes, item details, and participant details.

sales-order.created

Triggers when a new sales order is created in an Auctria event.

Field	Value
Auctria change	Insert SalesOrder
Primary payload object	payload.salesOrder
Common fields	id, type, createdAt, organization, event, payload
Selected output fields	Sales order ID, reference, origin, notes, event details, participant details, and transaction line items.

---

Webhook payload format

All Zapier triggers receive a JSON webhook payload with a common envelope. The payload object changes based on the event type.

{
  "id": "6aa5c78b-ad5d-4ebb-a2fe-f4fdda3851a3",
  "type": "transaction.added",
  "createdAt": "2026-04-01T18:37:02.7253615Z",
  "organization": {
    "id": "ac2f9f80-c0fc-4003-a13d-a96751c8085a",
    "name": "Auctria"
  },
  "event": {
    "id": "16300146-f692-480d-9f8e-72078ca9810b",
    "name": "Spring Gala"
  },
  "payload": {
    "transaction": {
      "id": "bd28d4b4-1333-4a29-9705-09fff0d84aee",
      "quantity": 1,
      "amount": "100.00",
      "origin": "User"
    }
  }
}

Sales order example

The sales-order.created trigger includes the sales order, participant, and transaction line items.

{
  "id": "f7c4fcc0-d8d0-46a2-8f0a-3b32f65c71b2",
  "type": "sales-order.created",
  "createdAt": "2026-04-20T16:42:13.0000000Z",
  "organization": {
    "id": "ac2f9f80-c0fc-4003-a13d-a96751c8085a",
    "name": "Auctria"
  },
  "event": {
    "id": "16300146-f692-480d-9f8e-72078ca9810b",
    "name": "Spring Gala"
  },
  "payload": {
    "salesOrder": {
      "id": "5386fc18-9d1d-4d90-a948-276834a44795",
      "reference": "SO-1001",
      "origin": "Online",
      "notes": "Created from online checkout",
      "participant": {
        "id": "4539dd75-f3c3-4549-a865-5cd3837c0642",
        "number": "1",
        "firstName": "Avery",
        "lastName": "Smith",
        "email": "donor@example.org"
      },
      "transactions": [
        {
          "id": "bd28d4b4-1333-4a29-9705-09fff0d84aee",
          "amount": "100.00",
          "quantity": 1,
          "salesTax1": "0.00",
          "salesTax2": "0.00",
          "salesTax3": "0.00",
          "item": {
            "id": "58f38341-81bd-4bed-9825-98dd22a7aa5f",
            "number": "4",
            "title": "Silent Auction Painting",
            "type": "Online"
          }
        }
      ]
    }
  }
}

---

Errors and support

If credentials cannot be loaded, Auctria returns an API outcome with Success = false and a message such as:

• Webhooks integration is not configured.
• Unable to load Zapier credentials.

For help connecting Auctria to Zapier, contact Auctria support through the Auctria contact page:

https://www.auctria.com/contact

---

Svix API endpoints

The Auctria Zapier integration does not call an Auctria API directly. Instead, it communicates with the Svix webhook platform API to manage webhook subscriptions and retrieve message samples. Svix (https://svix.com) is a licensed webhook-infrastructure vendor that Auctria uses to handle endpoint registration, signing, retry, and delivery.

The integration makes exactly 5 API calls to Svix. All use:

• Base URL: https://api.us.svix.com
• Authentication: Authorization: Bearer {integration_key}
• Content-Type: application/json

Full Svix API reference: https://api.svix.com/docs

#	Operation	Method	Endpoint	Zapier trigger lifecycle
1	Subscribe	POST	/api/v1/app/{application_id}/endpoint/	When a user enables a trigger
2	Get endpoint secret	GET	/api/v1/app/{application_id}/endpoint/{endpoint_id}/secret/	Immediately after subscribing
3	List messages	GET	/api/v1/app/{application_id}/msg/?event_types={eventType}&limit=1	When a user tests a trigger or loads a sample
4	Get message	GET	/api/v1/app/{application_id}/msg/{message_id}/	After listing, to get the full payload
5	Unsubscribe	DELETE	/api/v1/app/{application_id}/endpoint/{endpoint_id}/	When a user disables a trigger

1. Subscribe (Create Endpoint)

Called when a user enables a Zapier trigger. Creates a Svix endpoint that will receive webhook deliveries for the specified event type.

curl -X POST \
  'https://api.us.svix.com/api/v1/app/YOUR_APPLICATION_ID/endpoint/' \
  -H 'Authorization: Bearer YOUR_INTEGRATION_KEY' \
  -H 'Content-Type: application/json' \
  -H 'accept: application/json' \
  -d '{
    "url": "https://hooks.zapier.com/hooks/catch/0000000/0000000/",
    "version": "1",
    "rateLimit": 10,
    "filterTypes": ["participant.registered"]
  }'

The url is the Zapier webhook target URL. The filterTypes array specifies which event types this endpoint will receive. Available event types: participant.registered, item.added, transaction.added, sales-order.created.

Example response (201 Created):

{
  "id": "ep_1srOrx2ZWZBpBUvZwXKQmoEYga2",
  "url": "https://hooks.zapier.com/hooks/catch/0000000/0000000/",
  "version": 1,
  "rateLimit": 10,
  "filterTypes": ["participant.registered"],
  "disabled": false,
  "createdAt": "2026-07-29T12:00:00Z",
  "updatedAt": "2026-07-29T12:00:00Z"
}

2. Get Endpoint Secret

Called immediately after subscribing. Retrieves the signing secret used to verify incoming webhook deliveries.

curl -X GET \
  'https://api.us.svix.com/api/v1/app/YOUR_APPLICATION_ID/endpoint/ep_1srOrx2ZWZBpBUvZwXKQmoEYga2/secret/' \
  -H 'Authorization: Bearer YOUR_INTEGRATION_KEY' \
  -H 'Content-Type: application/json' \
  -H 'accept: application/json'

Example response (200 OK):

{
  "key": "whsec_C2FVsBQIhrscChlQIMV+b5sSYspob7oD"
}

The secret is used by the Svix webhook verification library to verify the svix-id, svix-timestamp, and svix-signature headers on incoming webhook deliveries.

3. List Messages

Called when a user tests a trigger or loads a sample. Retrieves the most recent message for the specified event type.

curl -X GET \
  'https://api.us.svix.com/api/v1/app/YOUR_APPLICATION_ID/msg/?event_types=participant.registered&limit=1' \
  -H 'Authorization: Bearer YOUR_INTEGRATION_KEY' \
  -H 'Content-Type: application/json' \
  -H 'accept: application/json'

Change the event_types query parameter to match the event you want to sample.

Example response (200 OK, with messages):

{
  "data": [
    {
      "id": "msg_1srOrx2ZWZBpBUvZwXKQmoEYga2",
      "eventType": "participant.registered",
      "payload": {
        "createdAt": "2026-04-01T18:37:21.6151313Z",
        "event": {
          "id": "16300146-f692-480d-9f8e-72078ca9810b",
          "name": "NEW 12"
        },
        "id": "d233b19e-b0a2-45ca-bd2c-fd346dbfffc5",
        "organization": {
          "id": "ac2f9f80-c0fc-4003-a13d-a96751c8085a",
          "name": "Auctria"
        },
        "payload": {
          "participant": {
            "firstName": "Test",
            "lastName": "participant1",
            "number": "72",
            "email": "",
            "id": "af15d186-17b5-4f56-a539-83fff77210fc"
          }
        },
        "type": "participant.registered"
      },
      "createdAt": "2026-04-01T18:37:21.6151313Z",
      "status": "Success"
    }
  ],
  "done": true,
  "iterator": null,
  "prevIterator": null
}

If no messages have been delivered yet, the data array will be empty. In that case, the Zapier app falls back to a static sample payload from the webhook event catalog.

4. Get Message

Called after listing messages, to retrieve the complete message payload.

curl -X GET \
  'https://api.us.svix.com/api/v1/app/YOUR_APPLICATION_ID/msg/msg_1srOrx2ZWZBpBUvZwXKQmoEYga2/' \
  -H 'Authorization: Bearer YOUR_INTEGRATION_KEY' \
  -H 'Content-Type: application/json' \
  -H 'accept: application/json'

Example response (200 OK):

{
  "id": "msg_1srOrx2ZWZBpBUvZwXKQmoEYga2",
  "eventType": "participant.registered",
  "payload": {
    "createdAt": "2026-04-01T18:37:21.6151313Z",
    "event": {
      "id": "16300146-f692-480d-9f8e-72078ca9810b",
      "name": "NEW 12"
    },
    "id": "d233b19e-b0a2-45ca-bd2c-fd346dbfffc5",
    "organization": {
      "id": "ac2f9f80-c0fc-4003-a13d-a96751c8085a",
      "name": "Auctria"
    },
    "payload": {
      "participant": {
        "firstName": "Test",
        "lastName": "participant1",
        "number": "72",
        "email": "",
        "id": "af15d186-17b5-4f56-a539-83fff77210fc"
      }
    },
    "type": "participant.registered"
  },
  "createdAt": "2026-04-01T18:37:21.6151313Z",
  "status": "Success"
}

5. Unsubscribe (Delete Endpoint)

Called when a user disables a Zapier trigger. Removes the Svix endpoint so no further webhook deliveries are sent.

curl -X DELETE \
  'https://api.us.svix.com/api/v1/app/YOUR_APPLICATION_ID/endpoint/ep_1srOrx2ZWZBpBUvZwXKQmoEYga2/' \
  -H 'Authorization: Bearer YOUR_INTEGRATION_KEY' \
  -H 'Content-Type: application/json' \
  -H 'accept: application/json' \
  -d '{}'

Example response: 204 No Content (empty body).

---

Postman collection

A Postman collection with all 5 endpoints above is available for download:

Download Auctria Zapier Svix API Postman Collection

How to use the collection

1. Download the .postman_collection.json file
2. Open Postman and click Import
3. Select the downloaded file
4. Set the following collection variables:
   • application_id — Your Svix application ID (from the Auctria application portal)
   • integration_key — Your Svix integration key (from the Auctria application portal)
5. The svix_base_url variable defaults to https://api.us.svix.com — change it only if you are using a different Svix region
6. Run the requests in order: Subscribe → Get Secret → List Messages → Get Message → Unsubscribe

The collection automatically saves the endpoint_id from the Subscribe response and the message_id from the List Messages response, so subsequent requests work without manual variable entry.

---

Webhook signature verification

Incoming webhook deliveries from Svix are signed using the Standard Webhooks specification. Each delivery includes three headers:

Header	Description
svix-id	Unique message ID
svix-timestamp	Unix timestamp of delivery
svix-signature	HMAC-SHA256 signature using the endpoint secret

The Zapier app verifies each incoming delivery using the Svix SDK (svix.Webhook.verify) with the endpoint secret retrieved in step 2. If verification fails, the delivery is rejected.

---

Last reviewed: June 2026

guide.auctria.com/redirect?id=AuctriaZapierAPIWebhooks

AuctriaZapierAPIWebhooks

/zapier_integration/

zapier_integration

Auctria Zapier API & Webhooks