When using the Jetpack CRM API connector you need to first have the API enabled on your Jetpack CRM install and have available your API endpoint, API key and API secret.
This guide covers what the API connector is useful for, and the plugins supported out of the box.
API connector basic usage
The API connector is intended for you to capture data into the CRM via the API. It requires no coding (vs using the API documentation and writing your own solution).
You can also install it on as many websites are you own, and use it to send data to a central CRM.
To do this, it needs your API details from your CRM install. Here’s how it may look in practice, with a central CRM, accepting data from a network of sites.
If you just have a single site, you don’t need to use the API connector, since your CRM extensions will take care of any integrations on the CRM site.
The API Connector is written to help you get contacts from external sites into your CRM. It currently supports the following:
You can use API connector for an “external” site on a multisite network.
When you install API connector and other Jetpack CRM extensions on the main Multisite Network Admin page, make sure that you do not network activate installed plugins.