How to build a social account picker with stable avatars and usernames

Fetch /api/v1/accounts on your server, render the returned platform, display name, unique username and avatarImageUrl, and store the selected platform-plus-handle pair as the publish target. MultiPost returns public account metadata only; provider tokens never enter the picker response.

Show both display name and unique username when they differ. A display name can change or collide, while the returned handle is the value the Partner API uses to resolve one of several accounts on the same network.

The fast way is to authenticate server-side with the customer's personal token, call the accounts endpoint and send only the display fields your UI needs. If the list is empty, use the connectUrl from/api/v1/me to send the customer to MultiPost account connection.

Publishing from the selected account requires Pro or Agency. Link to plans and billing whencanPublish is false, but allow users to understand their connection state before asking them to choose a destination.

Display platform name, avatar, display name and unique username; persist platform and handle for the target. Treat username as optional because a network may not expose one or an older connection may need reconnection before MultiPost can populate it.

Use avatarImageUrl in the UI rather than rebuilding provider CDN URLs. MultiPost normalizes expiring network avatars through its own media path. The guide to managing multiple accounts without sharing passwords provides the matching OAuth model.

Refresh the account list before a publish session and invalidate any selection whose platform-and-handle pair is no longer returned. Do not keep a deleted account selectable merely because its avatar remains in a client cache.

If username is missing for an older TikTok grant, explain that reconnecting can populate the newer profile scope. Keep the returned handle as the API target and never substitute an edited label from your own interface.

MultiPost scopes the accounts response to the bearer token's owner and returns no provider credentials. Your SaaS completes the boundary by storing one token per tenant, keeping calls on the server and never mixing cached account lists between customers.