Troubleshooting

If you receive an "invalid_client" error during OAuth2 authentication, it usually means there's an issue with your client credentials.

Possible causes:

• Incorrect client ID or client secret
• Client application not registered or deactivated
• Mismatched redirect URI

Solution:

1. Verify your client ID and secret are correct
2. Check that your application is active in the developer dashboard
3. Ensure the redirect URI matches exactly what you registered

If your API requests fail with a 401 Unauthorized error and a message about an expired token, your access token has expired.

Solution:

1. Use the refresh token to obtain a new access token
2. If the refresh token is also expired, initiate a new authentication flow

Example code:

// Example: Refreshing an expired token
async function refreshAccessToken(refreshToken) {
  const response = await fetch('https://www.iiniit.com/api/oauth2/authorize', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Basic ${btoa('YOUR_CLIENT_ID:YOUR_CLIENT_SECRET')}`
    },
    body: JSON.stringify({
      grant_type: 'refresh_token',
      refresh_token: refreshToken
    })
  });
  
  return await response.json();
}

If you receive a 429 Too Many Requests error, you've exceeded the rate limits for our API.

Solution:

1. Implement exponential backoff and retry logic
2. Check the response headers for rate limit information

If you receive a 400 Bad Request error, there might be an issue with your request parameters.

Possible causes:

• Missing required parameters
• Invalid parameter values
• Incorrect data format

Solution:

1. Check the API documentation for required parameters
2. Validate parameter values before sending the request
3. Ensure you're using the correct content type