Create a Partner

To recruit new partners from your website, you can connect your "Partner Program Application Form" by calling the following method on each submission:

kiflo('partner', {
        // partnerObject,
    },
    function(response) {
        // handle success
    },
    function(error) {
        // handle error
    }
);

Example:

kiflo('partner', {
    name: 'Microsoft',
    status: 'Prospect',
    programLevelId: 14,
    mainContact: {
        firstName: "John",
        lastName: "Doe",
        email: "john.doe@inc.com",
	jobTitle: "CEO",
	phoneNumber: "+1 555 666 777",
	createAccount: false
    },
    properties: {
        country: 'US',
        ... // other custom partner properties
    }
})

PartnerObject:

Name Type Description
name (required) string The name of the partner
status (optional) enum The status of the partner. Could be Applicant, Prospect, Active, Declined
programLevelId (optional) enum The program level identifier where the partner applies to. This Id can be found in the browser address bar when you select a level in a program. For this URL "https://app.kiflo.com/account/65758263/programs/93/levels/155", the programLevelId is 155
mainContact (required) object The main contact of the partner. A firstName, lastName, email is required.
properties (optional) object The properties of the partner visible on your Kiflo account

MainContact Object:

Name Type Description
firstName (required) string The main contact's firstname
lastName (required) string The main contact's lastname
email (required) string The main contact's email
jobTitle (optional) string The main contact's jobTitle
phoneNumber (optional) string The main contact's phoneNumber
createAccount (optional) boolean True to create the account on Kiflo for the new partner, otherwise False (default is False)

In which case should I create a partner?

If your partners can apply to your partner program from your website for example.
Have a look at how to connect your partner application form to Kilfo.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.