Security Center
Your Source For Our Latest Security & System Information
Customer Security Responsibilities
SAFEGUARD PASSWORDS
Keep your user passwords safe by following these tips.
- Use a strong password that is difficult for others to guess and avoid birthdays, names, and pet’s names. Be creative: think of a special phrase and use the first letter of each word as your password. Substitute numbers for some words or letters. For example, “I want to see the Pacific Ocean” could become 1W2CtPo
- Use more symbols and numbers in passwords. The reality is that longer, more complex logins are harder to breach.
- Never write down your password or share it with others.
- Never provide your Botdoc account login or password, credit card number, or other personal information via email or to unknown parties.
Note: Botdoc will never ask you for your password.
Exercise caution using public computers (coffee shops, library, airport, hotel): Public web browsers can cache personal data and store login details. Always log off of web sites and clear the browser cache to protect your personal information, passwords, and accounts.
SAFELY DISPOSE OF PERSONAL INFORMATION
Before you dispose of a computer, get rid of all the personal information it stores. Use a wipe utility program to overwrite the entire hard drive.
Before you dispose of a mobile device, check your owner’s manual, the service provider’s website, or the device manufacturer’s website for information on how to delete information permanently, and how to save or transfer information to a new device. Remove the memory or subscriber identity module (SIM) card from a mobile device. Remove the phone book, lists of calls made and received, voicemails, messages sent and received, organizer folders, web search history, and photos.
AVOID PHISHING EMAILS
Don’t open files, click on links, or download programs sent by strangers. Opening a file from someone you don’t know could expose your system to a computer virus or spyware that captures your passwords or other information you type.
READ PRIVACY POLICIES
Yes, they can be long and complex, but they tell you how the site maintains accuracy, access, security, and control of the personal information it collects; how it uses the information, and whether it provides information to third parties.
REPORT ISSUES
System failures, suspected breach, or general incident
If you are experiencing a system failure, suspect some type of technical incident or breach, or have a general issue, please contact us at support@botdoc.io
Suspicious Emails
If you believe you may have received a fake email, forward the entire email – including the header information – to us at: support@botdoc.io, then delete it from your mailbox.
Security Incidents/Breach
If you find or suspect a security incident, please report this to us at: support@botdoc.io
Unethical Behaviors
Please report this to us at: anonymous@botdoc.io
SECURITY ASSURANCE
Key Security Features
Security is part us, and part you. That’s why we’ve developed best practices for securing your Botdoc-powered applications.
Data Encryption
Files are encrypted in transit (only strong cipher suites) and at rest (AES-256).
Authentication
Two-factor authentication with RSA, SecurID or a digital certificate as well as Active Directory integration.
Network Security
Auto Scaling Firewalls, DDoS Protection, traffic filtering and penetration tests.
Access Controls
Access rights, permissions, and ethical walls based on users and groups.
ISO 27002:2013 & ISO/IEC 27017:2015
Botdoc is ISO27002:2013 certified through MS Azure. This is the highest level of global information security assurance available today, and provides customers assurance that Botdoc meets stringent international standards on security. ISO/IEC 27017:2015 certification, an international standard that aligns with and complements the ISO/IEC 27002:2013 with an emphasis on cloud-specific threats and risks.
Application Security
Static and dynamic application scans, comprehensive logging, and adherence to programming best practices (OWASP Top Ten, etc).
Service Organization Controls (SOC)
Annual Type 2 SOC 2 and SOC 2+ audits based on standards set by the AICPA.
PCI DSS
Botdoc maintains compliance with the current version of the PCI Data Security Standard (DSS) to ensure safe and secure handling of credit card holder information. As overseen by the Payment Card Industry Security Standards Council (PCI SSC), Botdoc places stringent controls around cardholder data as both a service provider and merchant.
HIPAA Compliant
Full compliance with the Health Insurance Portability and Accountability Act of 1996 for privacy, security, and breach notification rules for data storage.
Privacy Shield Certified
Botdoc complies with the EU-U.S. Privacy Shield Framework and Swiss-U.S. Privacy Shield Framework as set forth by the U.S. Department of Commerce regarding the collection, use, and retention of personal information transferred from the European Union and Switzerland to the United States.
FERPA Compliant
Compliant with the US Department of Education regarding data privacy, confidentiality, and security practices related to student-level longitudinal data systems and other uses of student data.
GDPR Compliant
Compliant with processing and holding the personal data of subjects residing in the EU.
GLBA
The Gramm-Leach-Bliley Act (GLB Act or GLBA) is the United States federal law that makes it mandatory for the financial institutions to share their methodology to protect the customers’ financial information. Botdoc follows all safeguard rule requirements and practices to ensure functioning in compliance with standards at all times.
Updates and Alerts
Routine maintenance, new features, fixes, updates and other important announcements!
(For best results please clear your browser history/cache after updates)
Botdoc API SANDBOX Planned Maintenance
Botdoc API SANDBOX Planned Maintenance
Hello Botdoc Developers,
Botdoc will have a new update running in our SANDBOX environment SUNDAY May 28, 2023 @ 3am MST!
This update will hit our production servers estimated Sunday June 11 2023 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
- Updated notifications flows. As of this deployment, all communications with a given Servicer Provider for Email, Sms and Voice will be performed asynchronously.
- Add a new endpoint to retrieve Sms and Email events directly from the Servicer. From this endpoint, communication may be performed with the Email/Sms Servicer to retrieve the most recent data on a message which may result in higher response times according to the Servicer availability.
- Ability to import and export Automation steps.
- Updated Transport Method integration with Google Gmail and Microsoft Office 365.
- Added endpoint to paginate entities Message and MessageReply from a single call.
- Added integration with new Vendor to send emails, Sendinblue
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/
Thanks,
Botdoc API Team
Services Back to Normal
Services Back to Normal
Dear Botdoc Users,
Botdoc had to make some emergency (hot-fixes) updates that may have effected some user’s experience while using Botdoc NOW product.
Botdoc is 100% back to normal and there are no current disruptions.
Sorry for this inconvenience.
Botdoc Team
Disruption of Botdoc NOW product and API Service
Disruption of Botdoc NOW product and API Service
Botdoc Status: 100%
At roughly 6PM Mountain time today (Friday 7 April 2023), Botdoc experienced what we believe to be a DDoS attack. Our services were down from roughly 6:10PM MT to 6:25PM MT due to our own efforts to appropriately address the issue and solve it quickly.
Our environment scaled appropriately and we were notified. Internal network measures were taken per our incident response plan.
At roughly 6:35PM MT everything was brought back online 100%. Based one the sequencing of geographic servers some of our customers may have experienced downtime, others may not have.
As of this update, since 6:35PM MT there have been no anomalies, no degradation of service nor any other attempts of attacks. This event has passed and we do not expect any more issues.
Our team is watching this and our services closely and will continue to do so over the coming weeks.
Thanks,
Botdoc Team
Botdoc NOW Product – Planned Maintenance Updates for April 2, 2023
Botdoc Now Product Planned Maintenance
On Sunday April 2, 2023 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- P2 automation page custom URL fixes (for dealerships)
- P2 – downloading pull files fixed on the automation pages (for dealerships)
- P2 – Automation duplicates messages removed on customer side/UX (for dealerships)
- P2 Page scrolling fixes (UX) via mobile
- P1 – ability for Team owners to set Two factor login for all users on team (global feature) bug fixes
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
EMAIL SERVICES BACK TO NORMAL – Disruptions of Botdoc NOW product and API Service
SERVICES BACK TO NORMAL
Dear Botdoc Users,
We have confirmed with Mailgun that all is functioning correctly and services are responsive therefore ALL Botdoc EMAIL services are back to normal.
Even though this was out of our hands, we are sorry for this inconvenience.
Botdoc Team
Disruptions of Botdoc NOW product and API Services (EMAIL service)
Disruptions of Botdoc NOW product and API Services
Hello Botdoc Users
Our email service (Mailgun) is having intermittent connection issues which is causing some of our clients, who do not have their own SMTP, to experience connection issues.
Mailgun continues to work on the issues and we will have more information to you ASAP. We appreciate your patience and understanding.
Sorry for this inconvenience.
Botdoc Team
Botdoc API – IMPORTANT NOTICE “New IP’s to add”
Botdoc API Important NOTICE
IMPORTANT NOTICE:
*Please implement by 1/18/2023 for Sandbox deploy and 1/22/2023 for Live production deploy!
Hello Botdoc developers,
Botdoc will be adding a few new Public IPs to it’s pool in the API product.
Customers that have strict firewall rules will be required to add the new IPs to the whitelist accordingly.
If you strict the outbound of your network, you will be required to add our additional inbound to your whitelist.
If you do restrict the traffic received from the internet (This would be the Botdoc API Webhooks), you will be required to add our additional outbound IP to your whitelist.
The new IPs are:
– Inbound: 20.62.143.104
– Outbound: 20.246.242.252
If you have any questions regarding this addition, you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io.
Thanks,
Botdoc API Team
Botdoc API Planned Maintenance (LIVE/PRODUCTION) – Sunday January 22, 2023
Botdoc API LIVE/PRODUCTION Planned Maintenance
Hello API Developers,
On Sunday January 22 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
-
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times.
Automotive Industry developers: Allow your customers to set a time to test drive or service maintenance.
Financial Industry developers: Allow your customers to set a time to discuss investments, tax preparations or any financial related meeting.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of December 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API – IMPORTANT NOTICE “New IP’s to add”
IMPORTANT NOTICE:
*Please implement by 1/18/2023 for Sandbox deploy and 1/22/2023 for Live production deploy!
Hello Botdoc developers,
Botdoc will be adding a few new Public IPs to it’s pool in the API product.
Customers that have strict firewall rules will be required to add the new IPs to the whitelist accordingly.
If you strict the outbound of your network, you will be required to add our additional inbound to your whitelist.
If you do restrict the traffic received from the internet (This would be the Botdoc API Webhooks), you will be required to add our additional outbound IP to your whitelist.
The new IPs are:
– Inbound: 20.62.143.104
– Outbound: 20.246.242.252
If you have any questions regarding this addition, you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io.
Thanks,
Botdoc API Team
POSTPONEMENT – Botdoc API Planned Maintenance (LIVE/PRODUCTION) – Sunday January 8, 2023
Hello API Developers,
POSTPONEMENT MESSAGE:
The turn of the new year requires a few more technical aspects to be in place before we deploy to production.
We will be sending out a follow up email with more details as of when this patch will hit our production servers. Thanks for the understanding, and Botdoc wishes a great 2023 to everyone!
On Sunday January 8 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
-
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times.
Automotive Industry developers: Allow your customers to set a time to test drive or service maintenance.
Financial Industry developers: Allow your customers to set a time to discuss investments, tax preparations or any financial related meeting.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of December 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API Planned Maintenance (LIVE/PRODUCTION) – Sunday January 8, 2023
Hello API Developers,
On Sunday January 8 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
-
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times.
Automotive Industry developers: Allow your customers to set a time to test drive or service maintenance.
Financial Industry developers: Allow your customers to set a time to discuss investments, tax preparations or any financial related meeting.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of December 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API SANDBOX update December 21, 2022
Hello Botdoc Developers,
Botdoc will have a new update running in our SANDBOX environment TOMORROW December 21, 2022 @ 7am MST!
This update will hit our production servers estimated Sunday January 8 2023 at 2am MST. We will send another email next week confirming.
Here is the NEW feature to Botdoc’s API Developers SANDBOX platform:
-
Scheduler – With this scheduler feature, you are now able to book and schedule meetings/appointments during business hours via the P2 container with the added ability to customize dates and times.
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API Planned Maintenance (LIVE/PRODUCTION) – Sunday November 20, 2022
Hello API Developers,
On Sunday November 20, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
- Sending email out when certificates are about to expire.
- Added the ability to set a redirect to after a P2 Container completes.
- Add SMS templates ability
- Minor visual bug fixes on Secure Session page
- Update Acuant, customer can now click to send ID vs automatically sending after customer takes second photo of their Id.
- Moving user to the Complete page after a Container is killed.
- Added a new entity, LiketimeMeta. This entity holds Container EVent Values that happen during the lifetime of a Container. Check our documentation to read more on the events that are stored currently
- Allowing the P2 session to be embeded into iframes
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of November 13, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API SANDBOX update November 13, 2022
Hello Botdoc Developers,
Botdoc will have some new updates running in our SANDBOX environment on November 13, 2022 @ 2am MST!
These updates will hit our production servers estimated Sunday November 20, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
-
Sending email out when certificates are about to expire.
-
Added the ability to set a redirect to after a P2 Container completes.
-
Add SMS templates ability
-
Minor visual bug fixes on Secure Session page
-
Update Acuant, customer can now click to send ID vs automatically sending after customer takes second photo of their Id.
-
Moving user to the Complete page after a Container is killed.
-
Added a new entity, LiketimeMeta. This entity holds Container EVent Values that happen during the lifetime of a Container. Check our documentation to read more on the events that are stored currently (https://sandboxapi.botdoc.io/documentation/#section/Objects/LifetimeMeta). (documention will show on this URL AFTER the sandbox deploy)
-
Allowing the P2 session to be embeded into iframes
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API Planned Maintenance (LIVE/PRODUCTION) – New Version Sunday August 28, 2022
Hello API Developers,
On Sunday August 28, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
- Added assets manager. Allow users to send images in order to use them as assets on their Custom CSS
- Added a new Configuration where users can change the behavior of the Features when a Container completes. Currently, any Feature on a pending state is moved to a completed state once the Container itself completes. This configuration allows users to control the state change of the Feature(s) of all Containers in that Apikey, controlling if the Features should transition to a “complete” state or “expired” state.
- Added a new Configuration where users can enable or disable HTML tag stripping from the Webhooks Payload data.
- Added a “Download All” functionality to P2 Pushes and, PushPull Pushes. When enabled, a “download all” button will appear as the first item in the file list received by an user. This functionality will be disabled on the Push if the size of all files exceeds 30 Megabytes. In this case, the files on that Push must be downloaded individually.
- Updated typos in Documentation
- Updated Two Factor Authentication page on the Secure Session. We will now display to the user all of its TFA receiving methods on the same page. This will allow users to request the code again through the same page.
- Added new CSS classes to Secure Session HTML elements, so users can select different buttons using CSS selectors according to the Feature(s) states of that Container.
- Updated the file removal behavior on a Pull. Users were able to remove files only after its upload was complete. Now, users can cancel the upload of the files both on a P2 Pull and PushPull Pull.
- Increased valid window of the TFA codes to 600 seconds. Each code sent on the TFA had a valid window of 180 seconds. This means, the user had to input the code in a maximum of 3 minutes, otherwise he/she would get a “wrong code” error. However, emails may delay according to different providers, this window was not large enough in a few scenarios. Now the TFA codes will be valid for approximately 10 minutes. After the first valid code is used, all previous codes sent (if the user sent more than one) are invalidated.
- Updated accessibility elements on the Secure Session page
- Adde new attributes to Acuant Feature to control the process mode of the IDs and, the authentication sensitivity of the validation
- Create a new entity called “LifetimeMeta”. This entity relates directly with the Container and, it will hold custom metadata about the Container and its related Entities during its lifecycle. Check our API docs in order to see all data stored as LifetimeMeta.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of August 21, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc NOW Product – Planned Maintenance Updates for August 21, 2022
On Sunday August 21, 2022 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- Adding a searchable subject line column to the Push and Pull details page
- Updated the file removal behavior on a Pull. Users were able to remove files only after the upload was complete. Now, users can cancel the upload of the files during upload if needed.
- Updates on white-label syncing on the P2
- Bug fixes
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
Botdoc API SANDBOX update August 21, 2022
Hello Botdoc Developers,
Botdoc will have some new updates running in our SANDBOX environment on August 21, 2022 @ 2am MST!
These updates will hit our production servers estimated Sunday August 28, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
- Added assets manager. Allow users to send images in order to use them as assets on their Custom CSS
- Added a new Configuration where users can change the behavior of the Features when a Container completes. Currently, any Feature on a pending state is moved to a completed state once the Container itself completes. This configuration allows users to control the state change of the Feature(s) of all Containers in that Apikey, controlling if the Features should transition to a “complete” state or “expired” state.
- Added a new Configuration where users can enable or disable HTML tag stripping from the Webhooks Payload data.
- Added a “Download All” functionality to P2 Pushes and, PushPull Pushes. When enabled, a “download all” button will appear as the first item in the file list received by an user. This functionality will be disabled on the Push if the size of all files exceeds 30 Megabytes. In this case, the files on that Push must be downloaded individually.
- Updated typos in Documentation
- Updated Two Factor Authentication page on the Secure Session. We will now display to the user all of its TFA receiving methods on the same page. This will allow users to request the code again through the same page.
- Added new CSS classes to Secure Session HTML elements, so users can select different buttons using CSS selectors according to the Feature(s) states of that Container.
- Updated the file removal behavior on a Pull. Users were able to remove files only after its upload was complete. Now, users can cancel the upload of the files both on a P2 Pull and PushPull Pull.
- Increased valid window of the TFA codes to 600 seconds. Each code sent on the TFA had a valid window of 180 seconds. This means, the user had to input the code in a maximum of 3 minutes, otherwise he/she would get a “wrong code” error. However, emails may delay according to different providers, this window was not large enough in a few scenarios. Now the TFA codes will be valid for approximately 10 minutes. After the first valid code is used, all previous codes sent (if the user sent more than one) are invalidated.
- Updated accessibility elements on the Secure Session page
- Adde new attributes to Acuant Feature to control the process mode of the IDs and, the authentication sensitivity of the validation
- Create a new entity called “LifetimeMeta”. This entity relates directly with the Container and, it will hold custom metadata about the Container and its related Entities during its lifecycle. Check our API docs in order to see all data stored as LifetimeMeta.
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc NOW Product – Planned Maintenance Updates for June 26, 2022
On Sunday June 26, 2022 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- P2 – Improving Synchronization between NOW prodcut and API (SMTP, CSS and others)
- Bug fixes on expired files
- Improvement on UX on PULL request pages. Send/Finish button now has animation.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
Botdoc API Planned Maintenance (LIVE/PRODUCTION) – New Version Sunday June 12, 2022
Hello API Developers,
On Sunday June 12, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
- Changed the text “uploading” to “encrypting” on a P2 Pull file status upload
- Added ability to define a custom favicon to be used on the Secure Session page
- Added ability to define the Page Title on the Secure Session
- Added a new attribute to the Recipient entity which tells if that Recipient is online (has the Secure Session page open). Note: It may take up to 5 minutes to have a Recipient transition back to an “offline” state after being marked as online. The online status does not have any delays, as soon the Secure Session is open, the status is updated to online.
- When removing Recipient(s) from a P2 session, they will be redirect to a page that says “This session is no longer available”
- Added a few new endpoints to the API in order to retrieve data in bulk.
- Navbar on a P2 Session updated
- Added a NEW Feature, Acuant. With Acuant you will be able to securely collect IDs and, validate them with Acuant. Acuant will ensure its authenticity and, extract all the data via OCR.
- Allowance of HTML tags on the Feature Title and Description attributes.
- Added ability to enter custom initials for Requesters
- Removed previous code related to the previous Secure session version.
- Updated the HTTP Status a QR code returns
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of June 3, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API SANDBOX update June 3, 2022
Hello Botdoc Developers,
Botdoc will have some new updates running in our SANDBOX environment on June 3, 2022 @ 2am MST!
These updates will hit our production servers estimated Sunday June 12, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
- Changed the text “uploading” to “encrypting” on a P2 Pull file status upload
- Added ability to define a custom favicon to be used on the Secure Session page
- Added ability to define the Page Title on the Secure Session
- Added a new attribute to the Recipient entity which tells if that Recipient is online (has the Secure Session page open). Note: It may take up to 5 minutes to have a Recipient transition back to an “offline” state after being marked as online. The online status does not have any delays, as soon the Secure Session is open, the status is updated to online.
- When removing Recipient(s) from a P2 session, they will be redirect to a page that says “This session is no longer available”
- Added a few new endpoints to the API in order to retrieve data in bulk.
- Navbar on a P2 Session updated
- Added a NEW Feature, Acuant. With Acuant you will be able to securely collect IDs and, validate them with Acuant. Acuant will ensure its authenticity and, extract all the data via OCR.
- Allowance of HTML tags on the Feature Title and Description attributes.
- Added ability to enter custom initials for Requesters
- Removed previous code related to the previous Secure session version.
- Updated the HTTP Status a QR code returns
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc NOW Product – Planned Maintenance Updates April 17, 2022
On Sunday April 17, 2022 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 30 minutes to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- P2 updates: Botdoc can now sync your P1 white-label configurations to your P2 containers. This includes:
- Logo
- background color
- profile photos
- email templates including custom email templates
- Disclaimer message
- SMTP configurations (SPF configurations not included)
- Queue – UPDATE: Email notification, will include visibility into some details of the request. Notify selected users or all users of incoming requests into your Teams Queue. Owners and Admins of the Team can select any user or all users in a Queue to receive an email notification when incoming requests arrive. This feature is defaulted as disabled until the Owner/Admin checks the box/users. Once this notification box is checked, those users will receive an email notification of all incoming requests to this Queue where the user can then assign to themselves or to another user.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
Botdoc API Planned Maintenance (LIVE/PRODUCTION) – New Version Sunday April 3, 2022
Hello API Developers,
On Sunday April 3, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hr to perform.
Service updates to Botdoc’s API Developers platform, which include:
- NEW – Automations (Enterprise Level) – Configure custom Automated API calls based on set triggers.
- Added ContainerMetadata entity. This feature will allow you to send custom key => values entries and have them associated with a Container in order store custom values for your Containers.
- Secure session UI update. When a Feature is expired in a P2 Session, the go to action button won’t be shown on that Feature card.
- Secure Session UI update. The TFA “request a new code” message has been replaced. The Request a new code message will now say “request a new email”, “request a new text” and “request a new call” according to the TFA method chosen.
- Increased interval between TFA code requests on Secure Session page from 60 seconds to 120 seconds.
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of March 23, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
SMS SERVICES BACK TO NORMAL – Disruptions of Botdoc NOW product and API Service
Dear Botdoc Users,
We have confirmed with Twilio that all is functioning correctly and services are responsive therefore ALL Botdoc SMS services are back to normal.
Even though this was out of our hands, we are sorry for this inconvenience.
Botdoc Team
UPDATE – Disruptions of Botdoc NOW product and API Services (SMS service)
Hello Botdoc Users
Our SMS servicer (Twilio) is STILL currently experiencing issues with their infrastructure. This is causing SMS delays from our platform but specifically with US T-Mobile:
- SMS and MMS Delivery and Report Delays and Failures to US T-Mobile
- SMS Delivery Delays to Safaricom Network In Kenya
- Devices using Super SIM may experience degraded service
Twilio continues to work on the issues and we will have more information to you ASAP. We appreciate your patience and understanding.
Sorry for this inconvenience.
Botdoc Team
Botdoc API SANDBOX update March 23, 2022
Hello Botdoc Developers,
Botdoc will have some new updates running in our SANDBOX environment on March 23, 2022 @ 4am MST!
These updates will hit our production servers estimated Sunday April 3, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
- NEW – Automations (Enterprise Level) – Configure custom Automated API calls based on set triggers.
- Added ContainerMetadata entity. This feature will allow you to send custom key => values entries and have them associated with a Container in order store custom values for your Containers.
- Secure session UI update. When a Feature is expired in a P2 Session, the go to action button won’t be shown on that Feature card.
- Secure Session UI update. The TFA “request a new code” message has been replaced. The Request a new code message will now say “request a new email”, “request a new text” and “request a new call” according to the TFA method chosen.
- Increased interval between TFA code requests on Secure Session page from 60 seconds to 120 seconds.
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API LIVE/PRODUCTION Planned Maintenance
Hello API Developers,
On Sunday February 20, 2022 at 2:00am MST there will be a scheduled service update to Botdoc API.
Service updates to Botdoc’s API Developers platform, which include:
- Added voice/audio TFA
- Requests can now have multiple TFA methods
- Migrated White Label to Custom CSS
- Frontend application version update (Drop support for I.E)
- DocuSign is LIVE
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of February 11, 2022)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications.
Why we’re doing this:
Botdoc is expanding NEW features to our developers.
We appreciate your patience and understanding.
Thanks,
Botdoc API Team
Botdoc API SANDBOX Planned Maintenance
Hello API Developers,
Botdoc will have some new updates running in our SANDBOX environment on Friday February 11th, 2022 @ 3am MST!
These updates will hit our production servers estimated Sunday February 20, 2022 at 2am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
- Added voice/audio TFA
- Requests can now have multiple TFA methods
- Migrated White Label to Custom CSS
- Frontend application version update (Drop support for I.E)
- DocuSign is LIVE
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc Now Product Planned Maintenance
On Sunday January 30, 2022 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 30 minutes to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- PUSH 2 step authentication (code expires in 3 minutes vs 60 seconds)
- PUSH 2 step authentication – Pin code and Delivery ID# were listed on the email and mobile notifications. Delivery ID# has been removed to stop any confusion of what the pin code is.
- Queue – Notify selected users or all users of incoming requests into your Teams Queue. Owners and Admins of the Team can select any user or all users in a Queue to receive an email notification when incoming requests arrive. This feature is defaulted as disabled until the Owner/Admin checks the box/users. Once this notification box is checked, those users will receive an email notification of all incoming requests to this Queue where the user can then assign to themselves or to another user.
- DocuSign updates
- Personal URL page/Customer view – Added a more defined “send me files securely” button.
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
Terms of Service Update
Important Notice
Hello Botdoc Users
At Botdoc, we’re constantly working to improve our products and services for you. As our offerings evolve, our Terms of Service (“Terms”) will also evolve accordingly. To that end, we wanted to let you know we recently updated our Terms of Service to reflect changes we have made.
The updated Terms include further information about the rights granted to you through Botdoc’s services, including what you are and are not allowed to do on our platform.
We encourage you to read through the fully updated Terms to make sure you understand the changes and how they affect you. Other than that, you don’t need to do anything else.
If you have any questions or concerns you can reach us at support@botdoc.io.
Thanks,
Botdoc Team
Botdoc Now Product Planned Maintenance
On Wednesday December 29, 2021 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- NEW – Email Subject Line– Replace Botdoc’s Push and Pull default email subject line to recipients by setting a custom Team default subject line or allow users to send their own subject line.
- NEW – Personal URL Subject Line – When using the personal URL link in your email signature block allow your recipients to enter their own subject line when uploading documents. This subject line will be included in all email notifications to team users.
- Bug fixes on IP address metadata
- Security updates on TFA login process (code now expires in 60 seconds)
- Security updates on Password Reset
- Security updates
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
Announcing Our Newest Product Launch “The QUEUE”!
Botdoc NOW Product Planned Maintenance
On Sunday, October 24, 2021 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
Botdoc’s newest product launch “the QUEUE”! Its finally here!
* This removes the need for Teams to have multiple users logging into one account with the same passwordThe Queue feature is where Teams: Create a Queue (Loan Department) or multiple Queues (Loan Department; Pre-Approvals; Applications), Owner/Admin can add/invite any or all users on the Team to a Queue or multiple Queues to access Requests, Users can send Requests via the Queue and Users can assign themselves Requests inside the Queue or assign Requests to others in the Queue.Features include:
- An Enterprise Level Functionality
- Each Queue created will be a license (count as a user) however a Queue CANNOT log in
- Only Owners and/or Admins of the team can create and invite users to the Queue
- Depending on how many licenses you have for your team, there is no limit to how many users you can invite to a Queue
- A Team public URL link (just like the personal URL link in email signature blocks) with its own personal page tab to make changes
- Users can send a Pull via the Queue or send a Push via the Queue vs your own user name
- Assign a Pull to yourself or assign to a another user in the Queue
- Queue Pull timeline details – “Tori Mills assigned this request to Melinda Price” (assigned to a user) or “Tori Mills assigned this request to Tori Mills” (assigned to myself) or email@yahoodotcom initiated a Pull from the PRE Loan Apps Queue Public URL
- Assign a Push to yourself or assign to another user in the Queue
- Queue Push timeline details – “Tori Mills assigned this send to Melinda Price” (assigned to a user) or “Tori Mills assigned this send to Tori Mills” (assigned to myself)
- All movement/assigning within the Queue Push or the Queue Pull are saved on the audit logs
Note: Internet Explorer is no longer supported
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
Important Message – New Inbound IP address for the Botdoc NOW product
Important Notice
Hello Botdoc Users,
Starting November 8, 2021, Botdoc will have a NEW inbound IP address related to app.botdoc.io (The NOW product)
Many of our Users will notice no change however, if you control the IPs in your firewall you will need to allow/add the following NEW IP: 52.154.218.78
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io.
Thanks,
Botdoc Team
Botdoc NOW Product – Planned Maintenance Outage/Security Updates September 19, 2021
On Sunday September 19, 2021 at 2am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- NEW – Adobe Sign Integration – Added to the P2 for E-Sign capability
- Bug fixes on monthly Automatic request refills
Note: Features and updates are no longer supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
Botdoc API LIVE/PRODUCTION Planned Maintenance Sept 11 2021
Hello API Developers,
On Saturday September 11th at 2:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 30 minutes to perform.
Service updates to Botdoc’s API Developers platform, which include:
- Adobe Sign updates
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of Sept 4, 2021)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Important Notice Regarding IE Browser
Hello Botdoc Users
Botdoc is saying Farewell to Internet Explorer and we will no longer support bugs or fixes as of Aug 17, 2021 within our NOW product and here is why…
As of August 17, 2021, Microsoft will no longer provide security updates or technical support for versions of Internet Explorer and will fully retire IE on June 15, 2022.
Statement from Microsoft: After the above dates, customers will have a degraded experience or will be unable to connect to Microsoft 365 apps and services on IE 11. For degraded experiences, new Microsoft 365 features will not be available or certain features may cease to work when accessing the app or service via IE 11. While we know this change will be difficult for some customers, we believe that customers will get the most out of Microsoft 365 when using the new Microsoft Edge.
We appreciate your patience and understanding. If you have any questions or concerns you can reach at support@botdoc.io
Thanks,
Botdoc Team
DELAY Botdoc API LIVE/PRODUCTION Planned Maintenance July 25, 2021
LIVE PRODUCTION DELAY
Botdoc apologizes for this delay. Due to an unexpected callback queue discovery, this deploy has been delayed by one week and will be LIVE July 25, 2021 @2am MST.
Hello API Developers,
On Sunday July 18th at 1:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s API Developers platform, which include:
- Adobe Sign integration
- Added Callback Filters. This Feature allows you to filter only the Callbacks/Webhooks you would like to receive
- Added an attribute to the Iframe Feature where it won’t complete once it detects the first redirect inside the Iframe
- Add more Callback samples to documentation for each Feature
- Created a new Callback, “session_opened”. This Callback/Webhook is triggered once the recipient of a Container opens the session page
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of July 11th)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API LIVE/PRODUCTION Planned Maintenance July 18, 2021
Hello API Developers,
On Sunday July 18th at 1:00am MST there will be a scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s API Developers platform, which include:
- Adobe Sign integration
- Added Callback Filters. This Feature allows you to filter only the Callbacks/Webhooks you would like to receive
- Added an attribute to the Iframe Feature where it won’t complete once it detects the first redirect inside the Iframe
- Add more Callback samples to documentation for each Feature
- Created a new Callback, “session_opened”. This Callback/Webhook is triggered once the recipient of a Container opens the session page
Affected Product/Service: API Production Interface ONLY (Sandbox had this version as of July 11th)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API Important Notice
IMPORTANT NOTICE:
Starting August 4, 2021 forward, Botdoc API will start to employ Throttling to its API endpoints.
This behavior will be based on your current Authenticated Apikey set on the HTTP Request sent. This means, the number of HTTP Calls that can be performed to our API endpoints will be limited to:
– Maximum Requests per second: 40 HTTP Calls per Apikey
– Maximum Request per minute: 1000 HTTP Calls per Apikey
Any additional HTTP Call greater than those limits will return a 429 HTTP_STATUS for exceeding the numbers described above.
We advise our customers to employ a re-execution logic into their integrations. This means, when your integration reads a response HTTP_STATUS 429 for a given Apikey, it will re-execute that HTTP Call and any new HTTP Call it would perform only on the subsequent second.
If you have any questions regarding this behavior or would like know how your integration HTTP call/rate would look like, you can send an email to api@botdoc.io with your account email address and the list of Public IPs your integration uses.
Thanks,
Botdoc API Team
Botdoc API SANDBOX Update/New Version July 11, 2021
Hello API Developers,
Botdoc will have some new updates running in our SANDBOX environment on July 11, 2021 @ 8pm MST!
These updates will hit our production servers estimated Sunday July 18, 2021 at 1am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
- Adobe Sign integration
- Added Callback Filters. This Feature allows you to filter only the Callbacks/Webhooks you would like to receive
- Added an attribute to the Iframe Feature where it won’t complete once it detects the first redirect inside the Iframe
- Add more Callback samples to documentation for each Feature
- Created a new Callback, “session_opened”. This Callback/Webhook is triggered once the recipient of a Container opens the session page
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc NOW Product – Planned Maintenance Outage/Security Updates June 13, 2021
On Sunday June 13, 2021 at 1am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- NEW – Manage Multiple Teams via Organization tab
- NEW – Inactivity Session Timeout is now a global setting for Team Owners
- NEW – “Reply to” feature: Enable your recipients to “reply to” directly to your users requests via email. This means that if this feature is enabled, your users can send out requests, and the recipients can then “reply-to” directly to you as the user who sent the request vs the recipient getting the no-reply@bank.com
- Upgrade the core framework
- P2 – Remove and/or Add recipient(s) from a live session
- Security updates
- Last 10 files Received/Sent – shortcut on Dashboard has improvements
Note: Not all features and updates are supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team
SERVICES BACK TO NORMAL – Disruptions Of Botdoc NOW Product And API Service
Hello Botdoc Users
We have confirmed with Mailgun that all is functioning correctly and services are responsive therefore ALL Botdoc services are back to normal.
Even though this was out of our hands, we are sorry for this inconvenience.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io or support@botdoc.io
Thanks,
Botdoc Team
Disruptions of Botdoc NOW product and API Services
Hello Botdoc Users
Our email servicer (Mailgun) is currently experiencing issues with their infrastructure. This is causing some emails sent from our platform to not get delivered. Mailgun is already working on the issue. If you use a custom SMTP configuration or a different email servicer other than the default Botdoc offers, the emails sent from your account should work as expected.
Sorry for this inconvenience.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io or support@botdoc.io
Thanks,
Botdoc Team
Botdoc API LIVE/PRODUCTION Planned Maintenance
Hello API Developers,
On Sunday May 30th at 1:00am MST there will be scheduled service update to Botdoc API. We anticipate this planned update will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s API Developers platform, which include:
- Updated the Audit Log codes ABA-0010, ABA-0020 and ABA-0030 that refers to the models CRUD operations to save the current state of the object when the Create/Edit/Delete event happens on watched objects.
- Updated List of models watched by the Audit Logs (Refers to Audit Log codes ABA-0010, ABA-0020 and ABA-0030):Container, Feature, Recipient, RecipientItem, ContactNotificationSend, Message, Requester, RequesterContainer, AuthCode, RecipientAuthCode, DocuSign, DocuSignDocument, DocuSignDocumentDownload, Iframe, Pull, PullFile, Push, PushFile, PushFileDownload, Media, MediaDownload, MediaTag, Request
- Updated List of endpoints that are watched by the Audit Logs (Refers to Audit Log code AAA-0010): https://api.botdoc.io/documentation/
- Added a “Scroll down” button on the session pages for P2 Sessions. If there are any contents below the coverage of the screen the “scroll down bottom” arrow will automatically appear.
- Added the ability to define Session TFA codes based on each Recipient on a Container. All previous functionality remains the same, where when defining an AuthCode to a Container, that is a general TFA. If there are more than one Recipient and you need to define different TFA codes to each Recipient, the object RecipientAuthCode should be used as it provides the TFA information separately per Recipient.
- When the Flat Callback functionality was enabled, the payload of a Callback did not included the relation primary key of the related objects. Changed behavior where if Flat Callbacks are enabled, we will not include the actual data of the related object but we will include the primary key of the related objects.
- Updated P2/PushPull TFA backspace behavior entering the guard code.
- Feature(s) are not user-session dependent anymore. This means, P2 Feature(s) will have their state transitions happening on the background of the service for Feature(s) that needs to be moved to an “expired” state.
Affected Product/Service: API Production Interface ONLY (Sandbox has this version as of May 24th)
Expected Behavior:
Service updates/maintenance are normal deployments which won’t cause any impact to production or to the development tools. They happen with no impact to the functionality of the platform or customer applications. However, although this is very rare, if for any reason there may be an interruption of the functionality of deployment workflows and tools, it will be resolved within our expected maintenance window.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc API SANDBOX update/new version May 24, 2021
Hello Botdoc Developers,
Botdoc will have some new updates running in our SANDBOX environment on May 24th 2021 @ 5am MST!
These updates will hit our production servers estimated Sunday May 30, 2021 at 1am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
- Updated the Audit Log codes ABA-0010, ABA-0020 and ABA-0030 that refers to the models CRUD operations to save the current state of the object when the Create/Edit/Delete event happens on watched objects.
- Updated List of models watched by the Audit Logs (Refers to Audit Log codes ABA-0010, ABA-0020 and ABA-0030):Container, Feature, Recipient, RecipientItem, ContactNotificationSend, Message, Requester, RequesterContainer, AuthCode, RecipientAuthCode, DocuSign, DocuSignDocument, DocuSignDocumentDownload, Iframe, Pull, PullFile, Push, PushFile, PushFileDownload, Media, MediaDownload, MediaTag, Request
- Updated List of endpoints that are watched by the Audit Logs (Refers to Audit Log code AAA-0010): https://testapi.botdoc.io/documentation/#section/Log-Codes/Tracked-Endpoints
- Added a “Scroll down” button on the session pages for P2 Sessions. If there are any contents below the coverage of the screen the “scroll down bottom” arrow will automatically appear.
- Added the ability to define Session TFA codes based on each Recipient on a Container. All previous functionality remains the same, where when defining an AuthCode to a Container, that is a general TFA. If there are more than one Recipient and you need to define different TFA codes to each Recipient, the object RecipientAuthCode should be used as it provides the TFA information separately per Recipient.
- When the Flat Callback functionality was enabled, the payload of a Callback did not included the relation primary key of the related objects. Changed behavior where if Flat Callbacks are enabled, we will not include the actual data of the related object but we will include the primary key of the related objects.
- Updated P2/PushPull TFA backspace behavior entering the guard code.
- Feature(s) are not user-session dependent anymore. This means, P2 Feature(s) will have their state transitions happening on the background of the service for Feature(s) that needs to be moved to an “expired” state.
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Exciting Botdoc NOW Changes
Dear Customer,
Just a kind reminder of the excitement of Botdoc’s rapid growth, expanded capabilities and recent release of the new version of Botdoc (Botdoc NOW)!
With these changes, Botdoc has some pricing updates that will effect current users when upgrading or adding additional licenses or you take advantage of our new P2 feature (Remotely and digitally transact ALL phases of business within ONE encrypted session; Push, Pull, Chat – real time with your customers and E-Sign). If you don’t want to add any users/license, that’s ok too as your pricing will not change. This increase helps us ensure our commitment to providing the very best products and services to you, our customer.
Someone from our sales team will be reaching out to you in the coming weeks, to arrange a quick call with you and your team so you know what is available to you and work with you for the best solution that fits your needs.
As always, we are committed to providing quality products and service to you and appreciate your business and continued support.
Botdoc Team
Botdoc API Planned Maintenance – New Version Sunday April 11, 2021
Hello API Developers,
On Sunday April 11th at 1:00am MST there will be scheduled down time to perform upgrades to Botdoc API. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s API Developers platform, which include:
- Added ability to remove Recipient(s) from existing P2 Container(s).
- Added ability to send Feature(s) to specific Recipient(s) of a Container, so only the recipient can see and perform actions on a given Feature(s).
- Added code samples for adding/removing Recipient(s) from a P2 Container as sending Feature(s) to specific Recipient(s) of a Container.
- Added one additional state to the Feature object, “created”. When creating Feature(s) on the fly for a Container that was already sent, there are a few scenarios where it may be necessary to create a given Feature in a hidden state (it won’t be visible to the user once created). Any Feature in a “pending” state is shown to the user receiving and that is the default state when creating any Feature(s). The new state “created” gives the ability to users to create Feature(s) that won’t be shown to the receiving users right after its creation considering the Container has already been sent. This allows you to perform any checks or changes to a Feature(s) before actually displaying to the receiving user. If you do create Feature(s) in this state, you will need to perform an additional call informing Botdoc your new Feature is ready to be displayed.
- Improved email validators on Developer Portal – Dashboard Wizard
- Added French translation to a P2 Container
- Added “expires_at” attribute to a Container or Request View on Developer portal
Affected Product/Service: API Production Interface ONLY (Sandbox has this version as of Mar 26th)
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc is expanding NEW features to our developers. These new updates and features expand capabilities providing more advancements to our developers regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
SERVICES BACK TO NORMAL – Disruptions of Botdoc NOW product and API Service
Dear Customers,
We have confirmed with Microsoft Azure that all is functioning correctly and services are responsive therefore ALL Botdoc services are back to normal.
Even though this was out of our hands, we are sorry for this inconvenience.
Botdoc Team
Disruptions Of Botdoc NOW Product And API Services
Dear Customers,
We have an issue effecting services on Microsoft Azure, Azure DNS service is down globally and is affecting ALL Botdoc services. We are investigating it and troubleshooting and will have more information to you ASAP.
Sorry for this inconvenience.
Botdoc Team
Botdoc API SANDBOX Update/New Version March 26th, 2021
Hello API Developers,
Botdoc will have some new updates running in our SANDBOX environment on March 26th 2021 @ 8pm MST!
These updates will hit our production servers estimated Sunday April 11, 2021 at 1am MST. We will send another email next week confirming.
Remember, we are changing our LIVE deployment process.
A week or two before a Production deployment, we will make the new version available in our Sandbox environment. This will give developers/clients the opportunity to perform tests with a new version if they feel they need based on the changelog of the new version. Any tweaks and changes found by developers will take place during this testing phase in Sandbox if needed before rolling to Production.
Here are the features to Botdoc’s API Developers SANDBOX platform:
- Added ability to remove Recipient(s) from existing P2 Container(s).
- Added ability to send Feature(s) to specific Recipient(s) of a Container, so only the recipient can see and perform actions on a given Feature(s).
- Added code samples for adding/removing Recipient(s) from a P2 Container as sending Feature(s) to specific Recipient(s) of a Container.
- Added one additional state to the Feature object, “created”. When creating Feature(s) on the fly for a Container that was already sent, there are a few scenarios where it may be necessary to create a given Feature in a hidden state (it won’t be visible to the user once created). Any Feature in a “pending” state is shown to the user receiving and that is the default state when creating any Feature(s). The new state “created” gives the ability to users to create Feature(s) that won’t be shown to the receiving users right after its creation considering the Container has already been sent. This allows you to perform any checks or changes to a Feature(s) before actually displaying to the receiving user. If you do create Feature(s) in this state, you will need to perform an additional call informing Botdoc your new Feature is ready to be displayed.
- Improved email validators on Developer Portal – Dashboard Wizard
- Added French translation to a P2 Container
- Added “expires_at” attribute to a Container or Request View on Developer portal
Affected Product/Service: Botdoc API Sandbox only
Why we’re doing this:
This will give developers/clients the opportunity to perform tests in the SANDBOX with a new version if they feel they need based on the changelog of the new version.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us on Slack at https://botdoc.io/slack/ or api@botdoc.io
Thanks,
Botdoc API Team
Botdoc NOW Planned Maintenance March 21, 2021
On Sunday, March 21, 2021 at 1am MST there will be scheduled down time to perform upgrades to Botdoc. We anticipate this planned outage will take approximately 1 hour to perform.
We’re adding some BIG features to Botdoc’s platform, which include:
- Security updates
- Instagram link added to Personal profile/URL pages
- Owners can now create custom fields/Icons to Personal profile/URL pages
- Billing and Pricing updates
- New Website design – check us out https://botdoc.io/
Note: Not all features and updates are supported by Internet Explorer
Affected Product/Service: Botdoc Interface
Expected Behavior:
Botdoc’s interface will be inaccessible during this scheduled maintenance. Users Requests and Sends (inbound and outbound data/communications) will NOT be processed during this period.
Why we’re doing this:
Botdoc has received great feedback from its USERS therefore our team is expanding NEW features to our clients. These new updates and features expand capabilities providing more advancements to our users regarding secure transport of data between two points.
We appreciate your patience and understanding. If you have any questions or concerns you can reach us at support@botdoc.io
Thanks,
Botdoc Team