Updated February 12, 2018
These Validic Application Programming Interface (“API”) Support Policies apply to the support provided by Validic, Inc. (“Validic”), as part of a Validic API license.
These API Support Policies are subject to change at Validic’s discretion.
“API Update” means a subsequent release of the API product, which Validic generally makes available for its API customers with an active API license and support contract at no additional fee. API Updates may contain, but are not limited to security fixes, critical patch updates, general maintenance releases, selected functionality, and documentation updates.
Validic will provide API Updates when available and at its discretion. Validic is under no obligation to develop any future functionality or enhancements. If an update for an API product is made available to you pursuant to these API Support Policies, it shall automatically replace the previous version of the applicable API product. Validic will continue to support previous major versions of the API for a period of 12 months from the time an updated version is made available.
Where practical, Validic will schedule such API Updates during non-business hours and will provide customers with advance notice via email or the Validic API Status Page.
DEDICATED INTERNAL HELP DESK
You are expected to establish and maintain an internal help desk for your customers and act as first-line support for your product within which the Validic API product is incorporated. First-line support shall include, but not be limited to: (i) a direct response to users with respect to inquiries concerning the performance, functionality or operation of the API product, (ii) a direct response to users with respect to problems or issues with the API product, (iii) a diagnosis of problems or issues of the API product, and (iv) a resolution of known problems or issues with the API product with the help of technical knowledge base articles, repositories and experience.
If after reasonable efforts you are unable to diagnose or resolve the API product problems or issues, you may contact Validic for technical support by emailing us at email@example.com.
Validic Technical Support consists of (i) a diagnosis of problems or issues with the API product, and (ii) reasonable efforts to resolve verifiable reported errors in the API product so that it performs materially as described in the online API product documentation.
Validic may review Support Requests logged by your technical contacts, and may recommend specific organization and process changes to assist you with the practices described in these API Support Policies.
Your Technical and/or Project Leads are the liaisons between you and Validic for API Technical Support. These persons must be knowledgeable about the Validic API product you have licensed and your technical environment in order to work with Validic to analyze and resolve Support Requests. They are responsible for engaging Validic technical support and monitoring the resolution of all Support Requests and escalated support issues.
Your Technical Leads assigned to monitor and administer your Validic API product should have experience in network troubleshooting as well as browser knowledge & debugging skills. In addition, they should have experience troubleshooting third-party web application integration.
Technical Leads are responsible for checking Validic’s online resources (e.g. website technical documentation and knowledge base solutions) and the Validic API Status Page, if available before submitting a Support Request as the issue or problem may have already been reported. Status of service outages and API product maintenance scheduling is updated on the Validic API Status Page.
Validic is committed to rapid response of all Support Requests. All severities can be logged with Validic on a 24 hours-per-day, 7 days-per-week, 365 days-per-year basis via email at firstname.lastname@example.org.
Validic will use commercially reasonable efforts to promptly respond to each Support Request. Validic does not guarantee resolution time as that may vary on the nature of the problem. A resolution may consist of a fix, workaround or other solution Validic deems reasonable.
Validic will use reasonable efforts to meet the Service Level Objectives stated in the table below. Validic will provide continuous efforts (24x7x365) to resolve Severity 1 API service availability issues until a workaround or resolution can be provided or until the incident can be downgraded to a lower severity.
API Support Service Level Objectives
|Target Response Times
|Critical (API Severity 1)
|30 minutes or less: 24×7
|Major (API Severity 2)
|4 business hours
|Minor (API Severity 3)
|8 business hours
|Cosmetic (API Severity 4)
|12 business hours
Please refer to your API Product Terms of Service for any additional API product specific details.
Critical (Severity 1)
Critical production issue affecting all users, including system unavailability and data integrity issues with no workaround available. This may include one or more of the following:
- Service is down or unavailable.
- A critical part of the API infrastructure is unavailable or inaccessible, resulting in total disruption of work or critical business impact.
- Service crashes or hangs indefinitely causing unacceptable or indefinite delays for resources or response.
- Data corrupted or lost and must restore from backup.
- A critical documented feature / function is not available.
Severity 1 issues identified by the customer but not related to a service interruption/outage require the customer to have dedicated resources available to work on the issue on an ongoing basis.
Major (Severity 2)
Major functionality is impacted or significant performance degradation is experienced. Issue is persistent and affects many users and/or major functionality. No reasonable workaround is available. This may include one or more of the following:
- Service is operational but highly degraded performance to the point of major impact on usage.
- Important features of the API offering are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion.
- Access to a particular third-party application or service provider deemed noncritical is impacted
Minor (Severity 3)
System performance issue or bug affecting some but not all users. Short-term workaround is available, but not scalable. This may include one or more of the following:
- Service is operational but partially degraded for some or all customers, and an acceptable workaround or solution exists.
- Problem with non-critical feature or functionality
Cosmetic (Severity 4)
An inquiry regarding a routine technical issue; information requested on application capabilities, navigation, installation or configuration; bug affecting a small number of users. An acceptable workaround is available. This may include one or more of the following:
- Minor problem not impacting service functionality.
- Enhancement requests, missing or erroneous documentation.
- Minor problem or question that does not affect delivery of service.
SUPPORT REQUEST SEVERITY LIFE CYCLE
Support Requests are assigned a severity level based on the nature of your request. We highly recommend you familiarize yourself with the Severity definitions and response times defined above.
Severity 1 Problem Reporting — Please first check the Validic API Status Page to see if the outage has already been reported or if your issue is due to a scheduled API product maintenance. If you do not see your issues reported, please report service outages/severity 1 problems via email.
Downgrade of Severity Level — If, during the Support Request process, the issue no longer warrants the severity level currently assigned based on its current impact on the production operation of the API product, then the severity level will be downgraded to the severity level that most appropriately reflects its current impact.
Upgrade of Severity Levels — If, during the Support Request process, the issue warrants the assignment of a higher severity level than that currently assigned based on the current impact on the production operation of the API product, then the severity level will be upgraded to the severity level that most appropriately reflects its current impact. In requesting any assignment of a higher severity level, you must provide Validic with sufficient information that demonstrates the increased impact of the issue on the production operation of the service.
Adherence to Severity Level Definitions — You shall ensure that the assignment and adjustment of any severity level designation is accurate based on the current impact on the production operation of the API product. You acknowledge that Validic is not responsible for any failure to meet performance standards caused by your misuse or mis-assignment of severity level designations.
SUPPORT REQUEST ESCALATION
At Validic, our support team always works to ensure that the appropriate resources and level of focus are applied to your request to ensure a timely resolution. If you are not satisfied with the progress of your Support Request, however, you can request an escalation. By invoking the escalation process, additional levels of Validic management attention, procedure reinforcement and resource prioritization are brought to bear on resolving your Support Request.
Contact information for Validic Technical Support is: email@example.com
Effective Date: February 12, 2018
Prior versions of this document are available here.