Notion error: Access code already utilized

Other Questions Notion
1

I encounter an error while integrating Notion into my web app; the access token returns a ‘code already used’ message. Below is my updated backend snippet:

appRouter.get('/authenticate/:authParam', async (req, res) => {
  const { authParam } = req.params;
  try {
    const tokenResult = await axios({
      method: 'POST',
      url: 'https://api.notion.com/v1/oauth/token',
      auth: { username: apiKey, password: apiSecret },
      headers: { 'Content-Type': 'application/json' },
      data: { code: authParam, grant_type: 'authorization_code' }
    });
    if (!tokenResult.data.access_token) throw new Error('Token not received');

    const searchResult = await axios({
      method: 'POST',
      url: 'https://api.notion.com/v1/search',
      headers: {
        'Content-Type': 'application/json',
        Authorization: `Bearer ${tokenResult.data.access_token}`,
        'Notion-Version': '2022-02-22'
      },
      data: { filter: { property: 'object', value: 'database' } }
    });
    res.json({ results: searchResult.data.results });
  } catch (error) {
    console.error('Notion API error:', error);
    res.status(500).send('Authentication error.');
  }
});
2

hey, seems ur token is being reused - notion codes are one time use. check if ur code isnt fired more than once, might solve the issuse

3

I encountered a similar obstacle while integrating Notion into an application. The error resulted from the repeated use of the authorization code because the endpoint was triggering more than once. In my case, ensuring that the token exchange request was sent only once resolved the issue. I recognized the problem by adding detailed logging to track the request flow, revealing that the front-end inadvertently fired duplicate device authentication calls. A single-call approach, along with proper state management on the client side, proved effective, eliminating the error.

4

I experienced a similar recurring issue where my Notion integration kept failing because of duplicate token exchanges. The root cause lay in the asynchronous handling of requests, which inadvertently sent multiple token requests. In my case, establishing strict control flow with proper state verification ensured that the token exchange process was executed only once per authorization attempt. Logging the complete request flow helped to pinpoint the issue, and eventually, adding appropriate middleware to block duplicate calls resolved the error completely.

5

hey, i had similar issue - turned out its a double-request problem. fixed it by ensuring a single token call on server side. prob a race cond mess. check you client too, might be triggering twice. hope it helps