CB Connect update LinkedIn changes after regist

We have CB Connect working for authentication and to initially fill CB profile fields during registration. When someone updates their Linkedin Profile, how do we get CB to resync with LinkedIn (automagically :huh: once a month)?

Is there a way to make a button so the user can "re-register" when they see something change?

how do we get CB to resync with LinkedIn (automagically once a month)?

You can't, it's not designed to do that. You'd hit API limits within days or hours doing this if you have an active site as it'd have to check their LinkedIn profile on every login.

Is there a way to make a button so the user can "re-register" when they see something change?

Anything is possible, but you'll have to program it your self as it has no such feature. This could easily be abused to result in your hitting API limits. All the social sites limit how many times per hour, day, etc.. API can be called. If you allow users to click a button to re-sync you'll hit that limit from a single user abusing it for example.

My thought was to built-in some throttles/limits. Maybe something like:

1. an individual user could only request a manual update once per week; and/or
2. the whole site would automatically update once a quarter (in chunks spread-out somewhat evenly)

I recognize that you don't work for LinkedIn, and this is something custom I would support myself. With that said, does my throttle/limits concept seem plausible or am I grossly underestimating the API usage?

Thanks.

an individual user could only request a manual update once per week; and/or

You'd have to implement such a feature then as it doesn't have one.

the whole site would automatically update once a quarter (in chunks spread-out somewhat evenly)

Then you'd once a quarter guarantee to hit API limits. Do this enough and they'll lock your application, indefinitely.

does my throttle/limits concept seem plausible or am I grossly underestimating the API usage?

LinkedIn API limits are pretty generous, but that still is open for abuse depending on the usage. You can find their limits at the below link.

developer.linkedin.com/documents/throttle-limits

What you want is certainly doable, but not very practical. Especially if you end up with 50k active users for example.