Back to all

Keys and LeadV2 - Six (6) quick questions

Greetings Team,

Creating LeadsV2 using the API. Notice a "Key" property is returned upon creation. I need to store a key in my local MS SQL DB so I can access the specific Lead object later. Some "Key" property values within the Maximizer API are subject to "change" and not guaranteed to be persistent over time. Question: 1) Are the "Key" property values returned on LeadV2 creation persistent? If not, 2) can I utilize the "Key" object somehow (as in AbEntry objects)? If I need to, 3) how to I instruct the API to return the whole "Key" object upon creation for LeadsV2 or obtain a persistent key for LeadV2?

Generally not best practice, in my opinion, to allow "Key" values to change within a DB that reference saved objects. 4) Why within the API for some objects? 5) When do these "Key" values change? 6) What is the rationale with some "Key" values "returned" within the API upon creation not being guaranteed persistent?

Thanks, Joe