make sure you create as little code as possible keep it DRY
think very hard how to name the fields/methods/variables
think of a generic solution, i.e. so that we can support other backends with the same serialiser without changing the API (this is related to proper fields naming)
Problem: twitter (and some other providers) requires frontend to pass two fields, existing serialiser supports only
access_token
access_token
Also please see my comment below.