@OmarAlmonte - Another issue to add.
In the XML-RPC you can get a list of the Referrals via this endpoint below.
https://developer.infusionsoft.com/docs/table-schema/#Referral
The only thing you can do in REST v2 is to Create a Referral.
Hi @Pav, we do have an endpoint in REST v2 to get referrals by affiliate ID: Get Referrals by Affiliate ID.
If you also want to see which affiliate(s) referred a specific contact, you can use the GET /affiliates endpoint and filter by referral_contact_id.
Let me know if you have any questions!
No good just by Affiliate ID, it would be better to get a list of records similar to the other List endpoints.
Can you explain your specific use case? Understanding how you plan to use the data will help me suggest the most effective solution.
I have used the XML-RPC Referral table to look at the Info and Source fields to determine where the contact has been referred from, or filter on them to match them to a particular source.
Currently in an integration that I have developed it stores the referrals in a database table and looks them up by Contact ID. This is so that when transferring data from a merchant gateway to Keap I can set the Affiliate ID for the Order.
The endpoint you mentioned only works by the Affiliate ID, I would need to query it by Contact ID to determine the latest Affiliate being used for that Contact.
Generally all the main areas of Keap should have equivalent List Endpoints. Other integrations could be doing a variety of things to retrieve particular data.
That makes sense. With the current options available, filtering by source is not supported. I will raise this internally for further review and consideration.
@OmarAlmonte This is a must have. Querying by affiliate id to get refferal ids isnt scalable vs getting all refferals.
@Pav @Rick_Nielsen We will look into this. I have added the item to the tracker.