NMI is making a change to their API authentication method. By the end of 2026, all merchants will be required to migrate from username and password authentication to API key authentication. No code changes will be required for this migration, however if you are currently using a Username/Password combination for API authentication in your Sticky.io NMI Profile, you will need to generate a new API key in the NMI portal and then update your Sticky.io gateway profile configuration with the new API key.
NOTE: If you are not sure if you are using a Username/Password in your Sticky.io NMI configuration, check your gateway configuration first. If your configuration only shows a value for API Key, you are already in compliance and do not need to do anything further. If your NMI gateway configuration shows values for Username and Password, follow these steps to update your configuration.
Step 1: Create a New API Key in the NMI portal
Generate a Private Security Key
Log into the merchant portal as an admin user.
Navigate to Options → Settings → Security Keys.
Click Add a New Private Key.
Assign the key API permissions when prompted.
Step 2: Update your Sticky.io profile
NOTE: If your Sticky.io NMI configuration shows only the option for an API key, you are already in compliance with the new NMI API key mandate. No further update is necessary.
If your Sticky.io NMI configuration shows values for Username and Password you MUST update the Username field to be “api_key” and add the newly created API key in the Password field.
Step 3: Test your NMI integration
Use the Sticky.io API to retrieve or create a transaction to test that API authentication is working as expected.