How to activate an API license in Secure Exchanges
Activating an API license allows you to use the advanced features of Secure Exchanges in your applications. Here are the steps to follow:
You can find the API and SDK help documentation here:
1. Log in to the online portal
Log in to your account via the Secure Exchanges online portal.
2. Assign the API license
In the user management interface:
To learn more about each of these options, we invite you to click on the corresponding hyperlinks (word in orange).
3. Generate API information
Once the license has been assigned:
An email containing the API information (email, serial, API ID, API password) will be sent to the assigned email address.
⏱ Important : The setup email is valid for 15 minutes only .
🔐 You will need to decrypt it with the password displayed on the screen at the time of sending.
Once you have retrieved the information, you can configure your API integration with the correct settings. If you need assistance with the integration, our team is here to help.
Related Articles
What is Secure Exchanges' Refund and Upgrade Policy?
At Secure Exchanges, we are committed to providing high-quality service to our customers. Please read our refund policy below: Free Trial Period We offer a free 30-day trial period so you can discover our services. During this period, you can explore ...
Microsoft Office error during Secure Exchanges update (ASR blockage)
1. Context Microsoft Defender includes a security rule called "Block executable content from email client and webmail" that blocks executable content from email clients. This rule blocks all content considered executable when it originates from an ...
Deploying Secure Exchanges via GPO/Intune on Outlook
If you plan to deploy Secure Exchanges using Group Policy Objects (GPO) or Microsoft Intune, the necessary PowerShell scripts are available at the bottom of this article. For any questions, please contact us at support@secure-exchanges.com
Error adding a signature file or document with Secure Exchanges
If an error occurs when you try to attach a file or document for signature in an email protected by Secure Exchanges, it usually means that the file is already being used by another application or is temporarily blocked by your antivirus software. In ...