CRM APIs

Helpful Note

Each CRM system will have their own request payload requirements. Propexo will unify the request payload shape, but you will need to understand the CRM system requirements for how to properly populate the request payload. Leverage these API docs to understand the request payload requirements for each system.

With the Propexo API, you can choose to leverage our generic write endpoints or the system-specific write endpoints. The benefit to using generic write endpoints is that you do not have to manage many different endpoints that perform the same operation.

note

Below is an example of what it might look like to write to the generic endpoint creating a prospect.

Generic endpoint

// Propexo will route the request to the
// appropriate system-specific endpoint
// under the hood.
await app.post('crm/v1/prospects',
    {
        ...prospectPayload,
        integration_id: 'foo'
    })

note

Below is an example of what it might look like to write to a system-specific endpoint. Note that you would need to understand the system context and define the Knock specific endpoint.

System-specific endpoint (Entrata)

// You would need to understand the system context
// and define the Knock specific endpoint.
await app.post('crm/v1/prospects/knock',
    {
        ...prospectPayload,
        integration_id: 'bar'
    })

The end result will be the same. You are just given the option to choose how much control you would like.