As the field was no longer useful for advertisers, it was removed.

Whenever you need to pass the 2FA, the input field is already selected, and you can enter the code right away without selecting the field.

Now that API Tokens table is optmized, it provides contents rapidly.

With the help of these filters, you can find only expired, active tokens, or even those tokens that will be active until a selected date.

Now the support button in the sidebar has the same icon as the general support button in the bottom right corner.

It overloaded the page with additional information that wasn’t that popular and useful. Now the header is much more compact and readable.

Previously, some validation notifications emerged even when modal windows were just opened. The issue is fixed.

The second step of localization covers important and thorough sections of the Partner Platform.

Previously, unique user settings for the dashboard widgets were overwritten each time they logged in from a different device. Now the settings are independent of the device.

Filter the Affiliates table by the data in the protected fields, but pass the 2FA first.

Now, setting an earning to the Paid status doesn’t return an error.

Previously, there were outdated links that returned the 403 response code, now they are removed.

For some conversions, IDs were missing. Now it’s fixed.

Previoulsy, zeros in fields were depicted as emty fields. Now the issue is fixed.

As it’s designed to be created with either an invoice or an earning as a source, validation behaves accordingly.

Now, when passing a 2FA, the message clearly states what went wrong, and an old message with a vague meaning was removed.

Previously, it was possible to pass invalid data through the parameters of offer-related endpoints. Now, the validation excludes cases where a correctly edited or created offer malfunctions due to incorrect contents. The changes are applied to these two endpoints:

PUT backend/user-api/v1/offers/{offer_id}

POST backend/open-api/v1/users/offers/