LinkedIn UGC Posts API: Missing Timezone Parameter for Scheduled Shares

Feature Context

The UGC posts endpoint allows scheduling by supplying a UTC scheduledAt timestamp. The request body contains no field for a timezone offset or region.

Current Constraint

When a client constructs a local‑time datetime without timezone information, the API interprets it as UTC. This can cause unintended delays for users in regions that observe daylight‑saving time or have a non‑UTC offset.

Uncertainty

Documentation does not clarify how LinkedIn handles DST transitions or whether the user’s profile timezone influences the scheduled publish time. Developers must manually convert local times to UTC, but the correctness of that conversion depends on the client’s library and its DST rules.

Specific Questions

• Should the API expose a timezone or offset parameter to allow explicit scheduling in a user’s local time?
• How does LinkedIn process scheduled timestamps that cross a DST boundary?
• What is the recommended workflow for developers to ensure accurate scheduling across time zones?