> ## Content Index
> Fetch the complete content index at: https://blog.businessleague.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# API token modifications
- URL: https://blog.businessleague.com/api-token-modifications/
- Published: 2020-02-18T08:43:41.000Z
- Updated: 2026-10-15T21:29:02.000Z
- Author: Tiberiu Anghelina
- Tags: Anunturi 2Performant, Important, Pentru Advertiseri, Pentru Afiliati, Product Updates, #Migrated-1749251779576, #wp, #wp-post, #Import 2025-06-06 23:18, en

In order to improve security for all user accounts in 2Performant, starting at the from 1st of March 2020, we will modify the way sessions are maintained in our network.

If:

- you use 2Performant through [network.2performant.com/](https://network.2performant.com/?ref=blog.businessleague.com) \- you just log in the platform and use it from the 2Performant interface;
- or through our official PHP library: [https://github.com/2Parale/2Performant-php](https://github.com/2Parale/2Performant-php?ref=blog.businessleague.com)

t**hen everything will work as usual and there is no need for a change.**

If you've developed API integrations on your own, please make sure of the following:

- you do "sign-in" once, at the beginning of each data process session;
- you make requests to 2Performant's API sequentially (the code waits for a response to a request before it sends a new request)
- when you receive a response to a request via API, you take the access token delivered by the server and you use it for your next request and so on.

**If this doesn't happen or you don't make changes for this to happen, after our security update from 1st of March 2020, API calls more then 10 seconds away from the log-in will respond with HTTP 401 (unauthorized).**