> 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/political-campaign-tools/partyline.md).
# Partyline
Connect Anedot to Partyline to relay donation data for political compliance and campaign reporting from Settings → Integrations → Directory.
Set up the Anedot and Partyline CRM integration to automatically sync financial donation data. Step-by-step guide to connecting Action Pages, configuring API credentials, and using data relays.
**Partyline** is a CRM platform widely used by political organizations to manage supporter and donor data.
Anedot supports direct integration with Partyline by sending **financial page data** through `donation_completed` webhook events. Please note that **non-financial page data** and **custom field data** are **not supported** at this time.
## Connecting Anedot to Partyline
1. Go to **Settings → Integrations → Directory** in your Anedot account.
2. Click **+ New Connection** in the top right.
3. Choose **Partyline** from the Directory.
4. Select the Action Pages to sync *(default is all pages)*.
* To exclude pages, enter their IDs *(comma-separated)*.
* *Optionally*, limit the sync to a specific Team
5. **Enter your Partyline API Key and Client Secret.**
6. Click **Save** to complete the setup.
*You can update pages, Teams, or credentials anytime.*
## Data Relays
* **Supported Relays**: Only **financial Action Pages** are supported, and data is sent via the `donation_completed` webhook.
* **Data:** The integration delivers data to Partyline’s Anedot API endpoint: `https://platform.gulfpartyline.com/api/anedot`
* **Limitations**:
* **Custom field data is not relayed**.
* **Non-financial pages are not supported**.
* **Conduit Transactions are not relayed.**
* **Relay Tools**: Use the **Push Unsent** feature to resend failed or unsent donations by specifying a **date range**. This applies to all financial Action Pages.
## Field Mapping
### Relay Fields
The Anedot Fields match the Submission's Raw Data and the Partyline Fields match the Request Body relay.
| Anedot Field | Partyline Field |
| ----------------------------------------------------------------------- | ----------------------------------------------------------- |
| “donation\_completed” | event |
| (Donation) id | uid |
| createdAt | date |
| (Donation object: includes anedot & vendor fee amounts) | fees (multiple fields) |
| “\[firstName] \[lastName]” | name |
| email | email |
| phone | phone |
| title | title |
| amount (x100) | amount |
| origin (Donation) | origin |
| status (Donation) | status |
| suffix | suffix |
| address (postalCode) (city) (region) (line1) (country) (line2) | address (zip) (city) (state) (street) (country) (street\_2) |
| comments (Donation) | comments |
| employerName | employer |
| lastName | last\_name |
| “true” or “false” | recurring |
| createdAt | created\_at |
| “individual” or “organization” | donor\_type |
| firstName | first\_name |
| occupation | occupation |
| \* (optional field) | referred\_by |
| actionPageId | campaign\_uid |
| totalAmount (x100) | event\_amount |
| phone | mobile\_phone |
| organization | organization |
| actionPageName | campaign\_name |
| middleName (first letter only) | middle\_initial |
| id of the first (originating) donation on the commitment (if recurring) | originating\_uid |
| actionPageName | campaign\_identifier |
| “di” | api\_method |
\*referred\_by is a numeric value that maps as follows:
| Numeric value | Partyline referred\_by Value |
| ------------- | ---------------------------- |
| 0 | "Magazine" |
| 1 | "TV" |
| 2 | "Newspaper" |
| 3 | "Radio" |
| 4 | "Facebook" |
| 5 | "Twitter" |
| 6 | "Online Ad" |
| 7 | "Word of mouth" |
| 8 | "Other" |
## Payload Data
### Request Headers
```
{}
```
### Request Body
```json
{"event":"donation_completed","payload":{"uid":"dbd0ce1bb5544cd767ddd","date":"2023-05-11T14:37:13.580Z","fees":{"anedot_fees":{"amount":"2.30"},"vendor_fees":[]},"name":"Annie Dot","email":"admin@anedot.com","phone":"2255011234","title":null,"amount":"$50.00","origin":"hosted","status":"completed","suffix":null,"address":{"zip":"70503","city":"Lafayette","state":"LA","street":"123 Test Road","country":"US","street_2":null},"comments":null,"employer":null,"last_name":"Dot","recurring":false,"created_at":"2023-05-11T14:37:13.548Z","donor_type":"individual","first_name":"Annie","occupation":null,"referred_by":null,"campaign_uid":"00c7b970-c269-4062-979e-b7aa939995fe","event_amount":"$50.00","mobile_phone":null,"organization":null,"campaign_name":"Feed the Children - March Gala","middle_initial":null,"originating_uid":null,"campaign_identifier":"Feed the Children - March Gala"},"api_method":"di"}
```
### Response Body *(Success)*
```
"Anedot Transaction Imported Successfully"
```
### Response Body *(Failure)*
```
" \n \n \nIIS 10.0 Detailed Error - 404.0 - Not Found \n \n \n \n \n
\n
\n
HTTP Error 404.0 - Not Found
\n
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
\n
\n
\n \n
\n
\n \n
\n \n
\n \n
\n \n
\n \n
\n
\n \n \n"
```
### Response Status *(Success)*
```
200
```
### Response Status *(Failure)*
```
404
```
---
# 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/political-campaign-tools/partyline.md?ask=&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.