Update a LinkedIn Marketing API version in your project

Find the version your requests explicitly select

LinkedIn Marketing API versions use a monthly YYYYMM value in the LinkedIn-Version request header. Versioned endpoints use the /rest/ path. Removing the header does not automatically select the newest version. Check the official versioning documentation for the API product your integration uses.

WATA scans supported local source patterns for explicit headers. In Desktop 0.2.0, literal values 202509 or older are flagged for attention, and supported replacements target 202608.

Check the sunset date before choosing a target

As reviewed on September 12, 2026, the official migration table lists version 202509 as active until September 15, 2026. It lists 202608 as active, with an August 17, 2027 sunset. A version detected by WATA can therefore be nearing retirement rather than already unavailable. Verify the current LinkedIn migration status before making a production change.

Apply a supported header replacement locally

1. Open the local project in WATA and connect your account.
2. Scan the project and inspect the exact file and header declaration reported.
3. Review the proposed replacement. For supported literal declarations, WATA 0.2.0 can make the following change.

// Before
export const headers = { "LinkedIn-Version": "202509" };

// After WATA's supported edit
export const headers = { "LinkedIn-Version": "202608" };

4. Let WATA create and verify a backup before applying the edit.
5. Review the diff and the follow-up scan. Confirm that your actual HTTP client uses this declaration.
6. Review the detected project checks and run the relevant integration tests before deploying.

Test the behavior selected by the new version

A request header is a small edit that can select a different API contract. Review the release and migration notes for the versions between your old selection and the target. A successful local scan cannot establish that the remote API still accepts every operation.

• Exercise the reporting queries and write operations your integration actually uses.
• Check response fields, enum values, validation errors and permission requirements.
• Update fixtures or application code when the provider’s contract has changed.
• Review changes before deployment. WATA’s backup can restore its local repair if needed.

Common questions

Does changing LinkedIn-Version complete the migration?

Only when the rest of your integration is already compatible. WATA handles supported declarations; your tests and a review of the affected API contract determine what else must change.

Does WATA need access to my LinkedIn account?

The local scan and supported text repair do not require your LinkedIn credentials. Your own integration tests may need authorized credentials and can make network requests. Review project scripts before running them.

Can I use it offline?

Scanning and repairs require an authorized WATA account and internet access. Source files stay local, and opening the project folder or restoring a backup remains available without a server authorization.