How do I connect our CRM with the partner API and webhooks?

The partner API lets your CRM or another system read your organization's supporter data and advocacy activity. Webhooks send your system a message as soon as something happens, such as a supporter joining or taking action. Only an Owner can turn the API on, create keys and manage webhooks.

Open the menu under your name, choose Settings, then Partner API & webhooks.

Turn on access

Under Partner API access, use the switch to turn the API on. Turning it on shares nothing by itself. It only lets an Owner create keys. Turning it off stops every key and every webhook at once.

Create an API key

1. Under API keys, choose Create a key.
2. Give the key a name you will recognize, such as the system it is for.
3. Choose when it expires: Never, 1 year or 90 days.
4. Choose what else it may do:
   • Read your organization's tracked bills and positions, shared Issue Portfolios, campaigns and action pages. Private portfolios are never shared, and internal notes stay in the portal.
   • Register webhook endpoints, so the connected system can set up its own event receiver. It can only remove endpoints it created.
5. Check the box confirming you are authorizing the key to share supporter data with that system.
6. Choose Create key.

The key is shown only once, right after you create it. Copy it straight into your CRM. We store only a scrambled copy, so nobody can show it to you again. If you lose it, revoke it and create a new one.

Each key in the list shows when it was created and last used. Choose Revoke to stop a key immediately. Revoking a key also turns off any webhook endpoints that key registered.

What a key can read

For your organization only, a key can read:

• Supporters: identity, districts, engagement and consents.
• Their advocacy actions: bills, recipients and issue rollups.
• The position your campaigns asked them to take on each bill.

It cannot read the messages supporters wrote, and it cannot change or send anything.

Add a webhook endpoint

1. Under Webhooks, choose Add an endpoint.
2. Enter the web address of your receiver, starting with https://.
3. Choose the events to send, then choose Add endpoint.

The events are Supporter joined, Supporter updated, Supporter deleted their account, Action taken, Unsubscribed and Letter delivered or failed.

A signing secret is shown once after you add the endpoint. Add it to your receiver so it can confirm each message really came from us.

Each endpoint has these buttons:

• Send test sends a sample event so you can check your receiver.
• Deliveries shows recent deliveries and whether they succeeded. Choose Redeliver on a delivery to send it again.
• Rotate secret issues a new signing secret. Update your receiver with it.
• Disable pauses the endpoint, and Re-enable turns it back on.
• Delete removes the endpoint.

If your receiver is down, we keep retrying each event for about a day. An endpoint that keeps failing for many days in a row is turned off automatically. Webhooks are a quick way to hear about changes, but the API stays the full record, so your system can catch up from it.

Documentation for your developer

The Partner API & webhooks section links to the interactive API reference and a written guide. Together they cover every endpoint, authentication, sync patterns and how to check webhook signatures. Developers who use an AI coding assistant can also install our public skill. See the article on the developer skill.

If this does not solve it, email support@conservativestates.app and tell us your organization's name.