> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/integrations/crm-donor-management/aegis.md).

# Aegis

Connect Anedot to Aegis Premier Solutions to send donors and recurring payments to Aegis, manage your connection, and review field mapping and payload data.

The **Aegis Premier Solutions** integration in **Settings > Integrations** sends donors, donations and recurring payments from your Action Pages to Aegis, a CRM (customer relationship management) system for donor management. This page covers how to connect Anedot to Aegis, manage your connection, see what Anedot sends, find your data in Aegis, and review field mapping and payload data.

## Before You Begin

* You need **Integrations: Edit permissions** to add, edit, push or delete a connection. Integrations: Edit permissions also require **Action Pages: View permissions** and **Integrations: View permissions**. See [Permission Sets](https://docs.anedot.com/settings/access/permission-sets.md).
* You need an Aegis CRM account. You log in to Aegis at aegispremier.com with the username and password your Aegis administrator assigns.
* You need a Context key. Aegis Premier Technologies assigns this unique value to your organization.
* You need a Fund code that already exists in Aegis. Anedot records every gift and product order from the connection to this fund.
* You need the Aegis API URL. The production URL is `https://connect.aegispremier.com/api`.
* We recommend adding a hidden field named `appeal_id` to each Action Page you'll send, with an appeal code that already exists in Aegis. See [Hidden And Special Fields](https://docs.anedot.com/integrations/crm-donor-management/aegis.md#hidden-and-special-fields).

## Connect Anedot to Aegis

### Step 1: Gather Your Aegis Details

The connection uses the username and password you use to log in to Aegis CRM, plus a Context key that Aegis assigns. You'll enter these values in Anedot, along with a Fund code and the API URL.

To find your Fund code:

1. Go to aegispremier.com and log in with your Aegis username and password.
2. Go to **Funds > Locate Funds**.
3. Find the fund you want gifts recorded to and copy its fund code.

If the fund doesn't exist yet, create it in **Funds > New Fund** first.

{% hint style="info" %}
The menus you see in Aegis depend on the rights your Aegis administrator assigns.
{% endhint %}

Aegis Premier Technologies assigns the Context key. If you don't have one, contact Aegis support at <support@aegispremier.com>.

To attribute gifts to an appeal, find the appeal code in Aegis under **Appeals > Locate Appeal**. You'll add it to your Action Pages in a hidden field named `appeal_id`.

### Step 2: Create the Connection in Anedot

To create the connection:

1. Go to **Settings > Integrations**.
2. Click **New integration**.
3. Choose **Aegis Premier Solutions**.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Aegis Premier Solutions</strong> appears under the <strong>CRM</strong> category with the text "Connect Action Pages to Aegis Premier Solutions."</p></div>
4. Choose the Action Page scope:

   * Keep **All Action Pages** checked to include every Action Page, including pages you add later. (Optional) In **Exclude Pages**, enter a comma separated list of Action Page IDs with no spaces.
   * Uncheck **All Action Pages** and choose pages in **Selected pages** to include only the pages you pick.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>In <strong>Action Pages > Action Pages</strong>, the <strong>Name</strong> column shows an ID chip with the last 7 characters of each page's ID. Hover over the chip to see the full ID, and copy it to see the message "Page ID copied."</p></div>
5. Leave **Team** set to **All teams**.
6. Enter your Context key in **Context key**.
7. Enter your fund code in **Fund code**.
8. Enter your Aegis username in **Aegis Premier Solutions username**.
9. Enter your Aegis password in **Aegis Premier Solutions password**.
10. Enter `https://connect.aegispremier.com/api` in **Aegis Premier Solutions URL**, unless Aegis gave you a different URL.
11. Click **Create integration**.

The connection is created, and Anedot starts sending new qualifying records to Aegis. Anedot shows the message "Integration created."

{% hint style="warning" %}
The **Context key**, **Aegis Premier Solutions username**, **Aegis Premier Solutions password** and **Aegis Premier Solutions URL** can't be viewed or changed after you save. Check each value before you click **Create integration**.
{% endhint %}

{% hint style="info" %}
Anedot doesn't check your credentials when you create the connection. If a value is wrong, you'll see it when the first record is sent.
{% endhint %}

## Manage Your Connection

### Edit Your Connection

You can change the Action Page scope and **Name** on an existing connection. **Provider** is shown but can't be changed.

To edit your connection:

1. Go to **Settings > Integrations**.
2. Click **Edit** on the Aegis Premier Solutions connection.
3. Update the Action Page scope. The first time you edit the connection, enter a **Name**.
4. Leave the **Credentials/details JSON** box as it is.
5. Click **Save integration**.

Anedot saves your changes and shows the message "Integration updated."

The Context key, username, password and URL aren't shown in the Edit form. The Fund code appears only inside the **Credentials/details JSON** box. To change the Context key, username, password, URL or Fund code, delete the connection and connect again with the new values. See [Delete Your Connection](https://docs.anedot.com/integrations/crm-donor-management/aegis.md#delete-your-connection).

### Push Unsent Records

**Push unsent** is on the connection's row in **Settings > Integrations**. It sends submissions, including Lead Page and Event Page submissions, and successful recurring charges in the date range you enter that haven't already been sent successfully.

* Enter a **Start date** and **End date**. The dates default to the last 30 days in your account's time zone.
* The range can be up to 31 days.
* The start date must be within the last 12 months.
* Wait about five minutes between pushes.

When the push begins, Anedot shows the message "Push started." For full steps, see [Push Unsent in Webhooks (API)](https://docs.anedot.com/integrations/integration-automation-tools/webhooks.md#push-unsent).

### Delete Your Connection

To delete your connection:

1. Go to **Settings > Integrations**.
2. Click **Delete** on the Aegis Premier Solutions connection.
3. Confirm the prompt "Delete this integration?".

Anedot stops sending to Aegis and shows the message "Integration deleted." Data already in Aegis isn't changed.

To reconnect, follow the steps in [Connect Anedot to Aegis](https://docs.anedot.com/integrations/crm-donor-management/aegis.md#connect-anedot-to-aegis) again.

## Data Relays

### What Anedot Sends

Anedot sends records to Aegis. It reads from Aegis only to look up a donor or pledge. Aegis stores donors as partners. For each qualifying record, Anedot finds or creates the partner, finds or creates a pledge when the record is part of a commitment, and then creates a paid transaction with `POST transaction/Create`.

* **Donation Pages**: Anedot sends the donation after the payment succeeds. This includes Terminal and offline gifts.
* **Event Pages**: Anedot sends the registration after the charge succeeds. A registration with nothing to charge is sent when it's saved, as a $0 transaction.
* **Lead Pages**: Anedot sends the submission when it's created, as a $0 transaction.
* **Recurring donation payments**: Anedot sends each successful recurring charge when it succeeds. It uses the same Aegis partner and pledge as the original submission.

Each connection uses one Fund code for every gift and product order. Fund allocations from Anedot aren't sent.

Anedot doesn't send refunds, chargebacks, voids, Abandoned Actions, later edits to a submission, or commitment cancellations. See [Commitments](https://docs.anedot.com/finance/management-and-reporting/commitments.md).

#### How Anedot Matches Donors

To find the donor in Aegis, Anedot checks in this order:

1. An Aegis partner ID already saved on the submission.
2. A partner search by first name, last name, address, city and state. For the search, Anedot removes the last word of address line 1, so "123 Main St" becomes "123 Main".
3. A partner lookup by email. Any +tag before the @ is removed for this lookup only.
4. If no partner is found, Anedot creates a new partner with the original email address.

If the search returns more than one partner, Anedot uses the first one. Later gifts from the same person are searched again and reuse the partner when it's found. Recurring charges reuse the partner ID saved on the original submission. Anedot doesn't update partner details in Aegis once the partner exists.

#### How Anedot Matches Pledges

Pledges apply only to commitments. The first submission of a recurring commitment can create an open-ended pledge in Aegis. A recurring payment never creates a pledge. It uses the pledge ID saved on the original submission, a matching pledge on the partner, or the partner's only pledge when there's exactly one.

### Records Anedot Skips

Anedot doesn't send these records, and they don't show a row in **Settings > Integrations > Integration Requests**:

* A Donation Page submission with no completed donation.
* A recurring charge that didn't succeed.
* A submission from an Action Page excluded from the connection.
* A record that has already been sent successfully.

### Delivery Statuses

Each send that goes out shows a row in **Settings > Integrations > Integration Requests** with its status (**Success**, **Failure** or **Error**), the request and the response. See [Integration Requests](https://docs.anedot.com/integrations/relay-data-troubleshooting/integration-requests.md).

* **Success**: The last step returned an HTTP 2xx response, including HTTP 201. Aegis uses HTTP 201 to show that the record was created.
* **Failure**: The last step returned HTTP 301, 302, 400, 401 or 404. These rows aren't tried again automatically. After you fix the cause, use [Push Unsent Records](https://docs.anedot.com/integrations/crm-donor-management/aegis.md#push-unsent-records) to send them again.
* **Error**: Anedot couldn't complete the request, for example because of a connection problem.

Authorization errors don't turn the connection off.

Users with the **Integration sync failed** notification turned on get an email when a send finishes as failed. See [Notifications](https://docs.anedot.com/get-started/security/notifications.md).

## Find Your Data in Aegis

To find a transaction Anedot sent:

1. Log in to Aegis at aegispremier.com.
2. Go to **Donors > Locate Transaction**.
3. Enter your search values, such as Donor ID, **Start Date** and **End Date**, Invoice #, payment amount, or billing or shipping information.
4. Click **Find Transaction**.
5. Click the View icon on the row you want.

The transaction opens in Aegis. Its transaction note starts with "Anedot UID:" followed by the Anedot ID, so you can match it to the record in Anedot. Aegis assigns the invoice number after the transaction is created.

To find the donor's record, go to **Donors > Locate Donor**.

## Field Mapping

| Anedot Source                                                                                                                                              | Aegis Key                                                                                                                                                  |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| First name                                                                                                                                                 | `firstName`                                                                                                                                                |
| Last name                                                                                                                                                  | `lastName`                                                                                                                                                 |
| Email, as entered                                                                                                                                          | `email`                                                                                                                                                    |
| Phone number, sent as the last 10 characters. With no phone, the number is sent as `null`.                                                                 | `partnerPhones.number`                                                                                                                                     |
| Always `"Web"`                                                                                                                                             | `originSource`                                                                                                                                             |
| Address line 1, line 2, city, state (region), postal code and country, sent as stored                                                                      | `address1`, `address2`, `city`, `stateProv`, `postalCode`, `countryCode`                                                                                   |
| Fields whose labels start with `custom_flag`, sent for new partners only                                                                                   | `customFlags`                                                                                                                                              |
| Fields whose labels start with `custom_data_field`, sent for new partners only                                                                             | `customDataFields`                                                                                                                                         |
| The Aegis partner ID Anedot found or created                                                                                                               | `partnerID`                                                                                                                                                |
| The date and time the record was created, in UTC                                                                                                           | `transactionDate`                                                                                                                                          |
| Record total in dollars                                                                                                                                    | `totalTransactionAmount`                                                                                                                                   |
| The `appeal_id` field value, or `null` when there isn't one                                                                                                | `appealCode`                                                                                                                                               |
| Always `"Internet"`                                                                                                                                        | `channel`                                                                                                                                                  |
| Always `"Paid"`                                                                                                                                            | `payment.status`                                                                                                                                           |
| Record total in dollars                                                                                                                                    | `payment.amount`                                                                                                                                           |
| `"ElectronicFundsTransfer"` for bank accounts. `"CreditCard"` for everything else, including checks, cash, PayPal and $0 Lead Page and Event Page records. | `payment.paymentType`                                                                                                                                      |
| Last 4 digits of the card, or `null` for other payment methods                                                                                             | `payment.number`                                                                                                                                           |
| Record total minus page product prices. Recurring charges send the full total.                                                                             | `gifts.giftAmount`                                                                                                                                         |
| The connection's Fund code                                                                                                                                 | `gifts.fundCode`                                                                                                                                           |
| `true` when the record has a pledge, otherwise `false`                                                                                                     | `gifts.applyToPledge`                                                                                                                                      |
| The Aegis pledge ID, when the record has a pledge                                                                                                          | `gifts.pledgeID`                                                                                                                                           |
| Product price                                                                                                                                              | `productOrders.price`                                                                                                                                      |
| `0` when the product price isn't more than the total                                                                                                       | `productOrders.discount`                                                                                                                                   |
| The connection's Fund code                                                                                                                                 | `productOrders.fundCode`                                                                                                                                   |
| The product's internal identifier, or the `product_sku` field value                                                                                        | `productOrders.productSKU`                                                                                                                                 |
| Always `1`                                                                                                                                                 | `productOrders.quantity`                                                                                                                                   |
| First and last name                                                                                                                                        | `shipping.shipto`                                                                                                                                          |
| Address, sent as stored                                                                                                                                    | `shipping.shiptoAddress1`, `shipping.shiptoAddress2`, `shipping.shiptoCity`, `shipping.shiptoState`, `shipping.shiptoPostalCode`, `shipping.shiptoCountry` |
| The Anedot submission ID, or the recurring charge ID for recurring payments                                                                                | `referenceNumber`                                                                                                                                          |
| Two lines: "Anedot UID: \[ID]" and "Online Contribution (Source: \[source code])". When there's no source code, the source is "Web".                       | `transactionNote`                                                                                                                                          |

* **Amounts**: Anedot sends amounts in dollars as decimal numbers. For example, a $25 gift is sent as `25.0`.
* **Product orders**: When the page has products, Anedot sends one line per product. When the page has no products but the record has a `product_sku` field, Anedot sends one line with no price. Recurring charges send one product SKU line per page product. Otherwise `productOrders` is sent as `null`.
* **Country codes**: Country and state are sent as stored. Aegis expects country values as ISO 3166-1 alpha-2 codes, such as US.
* **Not sent**: Other hidden fields, UTM fields, referrer, fund name and other custom field answers aren't sent. The source code appears only in the transaction note.

### Hidden And Special Fields

Anedot reads these fields from your Action Pages by their labels. `appeal_id`, `product_sku`, `partner_id` and `pledge_id` must match exactly. Labels that start with `custom_flag` or `custom_data_field` also match. See [Hidden Fields](https://docs.anedot.com/action-pages/page-builder/hidden-fields.md).

* **appeal\_id**: The value is sent as `appealCode` on the transaction and on a new pledge. It can be a hidden or visible field, and a hidden field is the usual way to set it. Aegis requires the appeal to already exist, so use an appeal code from **Appeals > Locate Appeal**. If the field is missing, `appealCode` is sent as `null`.
* **custom\_flag**: Each field whose label starts with `custom_flag`, such as `custom_flag_1`, becomes one custom flag on a new partner. The field value is the flag name, the flag starts on the day it's sent, and it expires 5 years later. Blank values are still sent as a flag.
* **custom\_data\_field**: Each field whose label starts with `custom_data_field`, such as `custom_data_field_1`, must hold valid JSON. Anedot sends it in `customDataFields` on a new partner. Aegis custom data objects use FieldName, FieldValue and FieldType.
* **product\_sku**: The value is sent as `productSKU` when the page has no products, and on recurring charges. When the page has products, Anedot sends each product's internal identifier instead.
* **partner\_id and pledge\_id**: The integration creates these as hidden custom fields in your account and saves the Aegis IDs on each submission so later sends reuse them. Use a field with one of these labels only if you have an existing Aegis partner ID or pledge ID you intend to use.

Custom flags and custom data fields are sent only when Anedot creates a new partner. They aren't added to an existing partner.

## Payload Data

These are the request and response bodies shown in **Settings > Integrations > Integration Requests**. The stored request has one key per step. Lookup steps show only the endpoint, and the email value isn't stored. The password, Context key, URL and authorization header aren't stored. The stored response is the last step's status, body and headers.

### Request Body

This example is a $35 donation from a new donor on a page with a $10 product. The gift amount is $25.00 because Anedot subtracts the product price from the total.

```json
{
  "find_partner_by_name_and_address": {
    "get": "partner/Search"
  },
  "find_partner_by_email": {
    "get": "partner/Email"
  },
  "create_partner": {
    "firstName": "Annie",
    "lastName": "Dot",
    "email": "annie.dot@example.com",
    "partnerPhones": [
      {
        "number": "2255550123"
      }
    ],
    "originSource": "Web",
    "address1": "1340 Poydras St",
    "address2": null,
    "city": "New Orleans",
    "stateProv": "LA",
    "postalCode": "70112",
    "countryCode": "US",
    "customFlags": [],
    "customDataFields": []
  },
  "create_donation": {
    "partnerID": 104527,
    "transactionDate": "2026-11-11T15:03:03.287Z",
    "totalTransactionAmount": 35.0,
    "appealCode": "W2026WEB",
    "channel": "Internet",
    "payment": {
      "status": "Paid",
      "amount": 35.0,
      "paymentType": "CreditCard",
      "number": "4242"
    },
    "gifts": [
      {
        "giftAmount": 25.0,
        "fundCode": "GEN",
        "applyToPledge": false,
        "pledgeID": null
      }
    ],
    "productOrders": [
      {
        "discount": 0.0,
        "fundCode": "GEN",
        "price": 10.0,
        "productSKU": "MUG-1",
        "quantity": 1
      }
    ],
    "shipping": {
      "shipto": "Annie Dot",
      "shiptoAddress1": "1340 Poydras St",
      "shiptoAddress2": null,
      "shiptoCity": "New Orleans",
      "shiptoState": "LA",
      "shiptoPostalCode": "70112",
      "shiptoCountry": "US"
    },
    "referenceNumber": "7b2e9c41-3d5a-4f86-a1c0-9e8d7f6a5b43",
    "transactionNote": "Anedot UID: 7b2e9c41-3d5a-4f86-a1c0-9e8d7f6a5b43\nOnline Contribution (Source: Web)"
  }
}
```

### Response Body (Success)

```json
{
  "Gifts": [
    {
      "FundCode": "GEN",
      "PledgeID": null,
      "GiftAmount": 25.0,
      "ApplyToPledge": false
    }
  ],
  "Channel": "Internet",
  "Payment": {
    "Amount": 35.0,
    "Number": "4242",
    "Status": "Received",
    "PaymentType": "CreditCard"
  },
  "Shipping": {
    "Shipto": "Annie Dot",
    "ShiptoCity": "New Orleans",
    "ShiptoState": "LA",
    "ShiptoCountry": "US",
    "ShiptoAddress1": "1340 Poydras St",
    "ShiptoAddress2": null,
    "ShiptoPostalCode": "70112"
  },
  "PartnerID": "104527",
  "AppealCode": "W2026WEB",
  "InvoiceNumber": "2213291",
  "ProductOrders": [
    {
      "Price": 10.0,
      "Discount": 0.0,
      "FundCode": "GEN",
      "Quantity": 1,
      "ProductSKU": "MUG-1"
    }
  ],
  "ReferenceNumber": "7b2e9c41-3d5a-4f86-a1c0-9e8d7f6a5b43",
  "TransactionDate": "2026-11-11T15:03:03.287+00:00",
  "TransactionNote": "Anedot UID: 7b2e9c41-3d5a-4f86-a1c0-9e8d7f6a5b43\nOnline Contribution (Source: Web)",
  "TotalTransactionAmount": 35.0
}
```

### Response Status (Success)

```
201
```

### Response Body (Failure)

```json
{"Message":"The appeal could not be found in Aegis CRM. Appeal Code: 'W0000A0A'."}
```

### Response Status (Failure)

```
400
```

## Troubleshooting

### Rows Show Failure

Open the row in **Settings > Integrations > Integration Requests** and read Aegis's response.

* HTTP 401 means Aegis didn't accept the credentials. Check the username, password and Context key with Aegis, then delete the connection and connect again with the right values.
* HTTP 400 often means a required value is missing or doesn't exist in Aegis, such as an appeal code or fund code. Check the fund in **Funds > Locate Funds** and the appeal in **Appeals > Locate Appeal**.
* For other statuses, read the message in Aegis's response.

Fix the cause, then use [Push Unsent Records](https://docs.anedot.com/integrations/crm-donor-management/aegis.md#push-unsent-records).

### Rows Show Error

An **Error** row means Anedot couldn't complete the request, for example because of a connection problem.

### A Donor Doesn't Appear in Aegis

If there's no row in **Settings > Integrations > Integration Requests** for the submission, Anedot skipped it or hasn't sent it yet. Check that:

* The Action Page is in the connection's Action Page scope.
* The donation completed. Incomplete donations and failed recurring charges aren't sent.

If a row shows **Success**, search for the transaction in **Donors > Locate Transaction** using the date range of the gift. If the donor already existed in Aegis, the transaction is on that existing donor's record.

### Change Your Credentials or Fund Code

The Context key, username, password, URL and Fund code can't be changed in the Edit form. Delete the connection and connect again with the new values. See [Delete Your Connection](https://docs.anedot.com/integrations/crm-donor-management/aegis.md#delete-your-connection).

If the issue continues, contact our Support team at <help@anedot.com>.

## Related Articles

* [Integrations](https://docs.anedot.com/integrations.md)
* [CRM & Donor Management](https://docs.anedot.com/integrations/crm-donor-management.md)
* [Integration Requests](https://docs.anedot.com/integrations/relay-data-troubleshooting/integration-requests.md)
* [Push Unsent in Webhooks (API)](https://docs.anedot.com/integrations/integration-automation-tools/webhooks.md#push-unsent)
* [Notifications](https://docs.anedot.com/get-started/security/notifications.md)
* [Permission Sets](https://docs.anedot.com/settings/access/permission-sets.md)
* [Hidden Fields](https://docs.anedot.com/action-pages/page-builder/hidden-fields.md)
* [Commitments](https://docs.anedot.com/finance/management-and-reporting/commitments.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.anedot.com/integrations/crm-donor-management/aegis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
