Common API credential mistakes for Facebook, Instagram, and LinkedIn.
A lot of publishing issues are not content issues at all. They are setup issues caused by mismatched identifiers, tokens from the wrong stack, or assumptions that one valid-looking string is enough.
Mistake 1: using the wrong kind of identifier
The publishing account field should identify the real publisher. That means Page ID for Facebook, Business Account ID for Instagram, and author URN for LinkedIn. Public URLs and usernames are often the wrong input.
Mistake 2: mixing identifiers and tokens from different stacks
A token may look valid while still belonging to a different business setup, app flow, or author context than the identifier stored in the dashboard. The closer your identifier and token are to the same real publishing flow, the more stable the workflow becomes.
Mistake 3: assuming valid means usable
A token can be syntactically valid and still be useless because permissions are missing, access is scoped incorrectly, or the target account is not actually connected the way you think it is.
Mistake 4: changing a working setup without documenting the change
If a legacy setup already works, replacing it without tracking what changed makes future debugging much harder. Change credentials deliberately, not casually.