API Terms of Service

These API Terms of Service ("API Terms") are additional terms that apply specifically to your use of the EverFlow Veterinary Codes API ("API"). These API Terms supplement and are incorporated into our main Terms of Service.

1. API License and Access

1.1 API License

Subject to these API Terms and your executed licensing agreement, EverFlow grants you a limited, non-exclusive, non-transferable license to access and use our API to integrate EVC coding functionality into your software applications.

1.2 API Key Management

API access is controlled through unique API keys. You agree to:

• Keep your API keys confidential and secure
• Not share API keys with unauthorized parties
• Immediately notify us of any suspected compromise
• Use API keys only for authorized applications
• Implement secure storage and transmission of API keys

1.3 Authentication Example

2. Usage Limits and Rate Limiting

2.1 Rate Limits

API usage is subject to rate limits based on your subscription tier:

Subscription Tier	Requests per Hour	Burst Limit	Concurrent Connections
Starter	1,000	100/minute	5
Professional	10,000	500/minute	20
Enterprise	50,000	2,000/minute	100
Custom	Negotiable	Negotiable	Negotiable

2.2 Rate Limit Handling

When rate limits are exceeded, the API will return HTTP status code 429. Your application should implement appropriate retry logic with exponential backoff.

3. API Usage Requirements

3.1 Proper Attribution

All applications using our API must include proper attribution:

• Display "Powered by EverFlow Veterinary Codes" in your user interface
• Include acknowledgment of VetSCT compatibility in documentation
• Maintain EVC branding standards as specified in brand guidelines

3.2 Caching Requirements

To ensure optimal performance and reduce unnecessary API calls:

• Cache code data for a minimum of 1 hour
• Implement cache invalidation for updated codes
• Use ETags and conditional requests when available
• Do not cache more than 24 hours without revalidation

3.3 Error Handling

Your application must properly handle all API error responses and implement graceful degradation when the API is unavailable.

4. Prohibited Uses

You may not use the API to:

• Create competing coding standards or derivative works
• Reverse engineer or attempt to recreate our coding methodology
• Circumvent rate limits or access controls
• Store or redistribute EVC codes outside the terms of your license
• Use the API for real-time monitoring or surveillance of the service
• Create applications that violate veterinary practice regulations
• Resell API access to third parties without authorization

5. Data Usage and Privacy

5.1 Usage Analytics

We collect and analyze API usage data to:

• Monitor performance and reliability
• Prevent abuse and unauthorized access
• Generate billing and usage reports
• Improve our services

5.2 Data Retention

API usage logs are retained for 24 months for analytics and billing purposes. Detailed request/response data is purged after 90 days.

5.3 Privacy Compliance

When processing veterinary data through our API, you must:

• Comply with applicable state veterinary privacy laws
• Implement appropriate data security measures
• Obtain necessary client consents for data processing
• Not transmit personally identifiable information unless authorized

6. API Versioning and Changes

6.1 Version Management

Our API uses semantic versioning (e.g., v1.2.3). We maintain backwards compatibility within major versions and provide migration paths for major version updates.

6.2 Deprecation Policy

When deprecating API features:

• We provide 90 days advance notice for minor changes
• We provide 180 days advance notice for major version changes
• Critical security updates may have shorter notice periods
• Deprecated endpoints will continue to function during transition periods

6.3 Service Updates

We may update our code database without notice. Your application should handle new codes gracefully and not break when encountering unknown code formats.

7. Service Level Agreement (SLA)

7.1 Availability

We strive to maintain 99.9% uptime for our API service, measured monthly. Planned maintenance is excluded from availability calculations.

7.2 Performance

Target API response times:

• Simple queries: < 100ms (95th percentile)
• Complex queries: < 500ms (95th percentile)
• Bulk operations: < 2 seconds (95th percentile)

7.3 Maintenance Windows

Scheduled maintenance typically occurs:

• Sundays 2:00-4:00 AM EST
• With 7 days advance notice for major updates
• Emergency maintenance as needed with minimal notice

8. Billing and Payment

8.1 Usage-Based Billing

API usage fees are calculated based on:

• Number of API requests per month
• Data transfer volume
• Support tier and features accessed
• Number of connected practices or installations

8.2 Billing Cycles

Fees are billed monthly in arrears based on actual usage. You will receive detailed usage reports with each invoice.

8.3 Overages

Usage beyond subscription limits incurs overage charges as specified in your licensing agreement.

9. Support and Documentation

9.1 API Documentation

We provide comprehensive API documentation including:

• Endpoint references and examples
• Code samples in multiple programming languages
• Integration guides for popular platforms
• Best practices and troubleshooting guides

9.2 Developer Support

Support levels vary by subscription tier:

• Starter: Email support, community forums
• Professional: Priority email support, phone support
• Enterprise: Dedicated technical account manager

10. Compliance and Certification

10.1 EVC Certification

Vendors may apply for EVC Certified Partner status by demonstrating:

• Proper implementation of EVC standards
• Compliance with integration requirements
• Successful completion of certification testing
• Ongoing adherence to partnership standards

10.2 Audit Rights

We reserve the right to audit your API usage and implementation to ensure compliance with these terms and your licensing agreement.

11. Termination and Suspension

11.1 Immediate Suspension

We may immediately suspend API access if:

• You violate rate limits repeatedly
• Your usage threatens system stability
• Payment is overdue by more than 30 days
• You breach these API Terms

11.2 Termination Notice

Either party may terminate API access with 30 days written notice. Enterprise customers may have different termination terms as specified in their agreements.

12. API-Specific Disclaimers

13. Virginia Tech VTSL Partnership Acknowledgment

All API implementations must acknowledge our partnership with Virginia Tech Veterinary Terminology Services Lab (VTSL) and the compatibility of EVC with SNOMED VetSCT standards as specified in your licensing agreement.