Simply AskingLegal

API Terms of Service

Last updated: August 30, 2026 | Version 1.2

1. Introduction

These API Terms of Service ("API Terms") govern your access to and use of Simply Asking's Application Programming Interfaces ("APIs"), including any associated tools, documentation, code samples, and software.

These API Terms supplement our main Terms of Service. By accessing or using our APIs, you agree to these API Terms. If there is a conflict between these API Terms and the main Terms of Service, these API Terms will govern with respect to your use of the APIs.

2. Definitions

2.1 "API" or "APIs" means the Simply Asking application programming interfaces, including REST APIs, webhooks, SDKs, and any related tools and documentation.

2.2 "API Client" means any software application, website, or service that accesses or uses the APIs.

2.3 "API Credentials" means API keys, tokens, secrets, and other authentication credentials provided to you for API access.

2.4 "Rate Limits" means the maximum number of API requests permitted within a specified time period.

2.5 "End Users" means the individuals who use your API Client to access or interact with Simply Asking services.

3. API Access

3.1 Account Requirements

To use our APIs, you must:

  • Have an active Simply Asking account
  • Be on a plan that includes API access
  • Accept these API Terms
  • Comply with all applicable laws and regulations

3.2 API Credentials

When we provide you with API Credentials:

  • They are personal to your account and may not be shared
  • You are responsible for maintaining their confidentiality
  • You must immediately notify us of any unauthorized use
  • We may revoke or rotate credentials at any time for security reasons

3.3 Authentication

All API requests must be authenticated using valid API Credentials. We support:

  • API Keys (for server-to-server communication)
  • JWT tokens (for session-based access)

4. Permitted Uses

4.1 You May:

  • Build applications that integrate with Simply Asking services
  • Access your own data and your authorized users' data
  • Use the APIs as documented in our API documentation
  • Display Simply Asking data within your application (with proper attribution)
  • Cache API responses for reasonable periods to improve performance

4.2 You May Not:

  • Exceed your plan's rate limits without authorization
  • Access, collect, or store data you're not authorized to access
  • Reverse engineer, decompile, or disassemble the APIs
  • Circumvent any security measures or access controls
  • Use the APIs for competitive intelligence or to build a competing service
  • Sell, resell, or redistribute API access
  • Use the APIs for any illegal or unauthorized purpose
  • Interfere with or disrupt the APIs or servers
  • Remove or alter any proprietary notices or labels

5. Rate Limits and Quotas

5.1 Rate Limiting

To ensure fair usage and system stability, we impose rate limits:

API access is available on our team plans (Build, Scale, and Command). The following limits apply to every team plan:

PlanRequests/MinuteRequests/DayConcurrent Requests
Team plans (Build/Scale/Command)500Per plan allocation30

5.2 Rate Limit Headers

API responses include headers indicating your rate limit status:

  • X-RateLimit-Limit: Maximum requests per period
  • X-RateLimit-Remaining: Requests remaining in current period
  • X-RateLimit-Reset: Unix timestamp when the limit resets

5.3 Exceeding Limits

If you exceed rate limits:

  • Requests will return HTTP 429 (Too Many Requests)
  • Implement exponential backoff in your retry logic
  • Contact us to discuss higher limits if needed

5.4 Burst Protection

We may temporarily reduce your rate limit if we detect:

  • Unusual traffic patterns
  • Potential abuse
  • Actions that threaten system stability

6. Data Use and Privacy

6.1 Data Handling

When accessing data through our APIs:

  • Only access data you're authorized to access
  • Handle all personal data in compliance with applicable privacy laws
  • Do not store personal data longer than necessary
  • Implement appropriate security measures for data protection

6.2 End User Consent

If your API Client accesses End User data:

  • You must obtain appropriate consent from End Users
  • You must clearly disclose how you use their data
  • You must provide End Users with a way to revoke access

6.3 Data Processing Agreement

If you process personal data of EU residents through our APIs, our Data Processing Agreement applies.

7. Security Requirements

7.1 Credential Security

You must:

  • Store API Credentials securely (never in client-side code or public repositories)
  • Use environment variables or secure secret management systems
  • Rotate credentials if you suspect compromise
  • Use HTTPS for all API communications

7.2 Application Security

Your API Client must:

  • Validate and sanitize all user inputs
  • Implement proper error handling
  • Not expose sensitive information in logs or error messages
  • Follow secure coding best practices

7.3 Incident Reporting

You must promptly notify us at security@simplyasking.io if you:

  • Discover a security vulnerability in our APIs
  • Suspect unauthorized access to your API Credentials
  • Experience a security incident affecting Simply Asking data

8. Availability and Support

8.1 Service Level

  • We aim for 99.9% API uptime
  • Scheduled maintenance will be announced in advance

8.2 API Versioning

  • We will version future API releases (e.g., v1, v2)
  • We commit to providing at least 12 months notice before deprecating any API version
  • Deprecated versions will continue to function during the deprecation period
  • New features may only be available in the latest version

8.3 Breaking Changes

We consider the following to be breaking changes:

  • Removing an endpoint or method
  • Removing or renaming a required parameter
  • Changing the data type of a response field
  • Reducing rate limits

Non-breaking changes (which may be made without notice):

  • Adding new endpoints
  • Adding optional parameters
  • Adding new response fields
  • Increasing rate limits
  • Bug fixes

8.4 Support

API support is available based on your plan:

  • Team plans (Build, Scale, Command): Priority email support, response within 24 hours

9. Attribution and Branding

9.1 Attribution

When displaying data retrieved from Simply Asking:

  • Include appropriate attribution (e.g., "Powered by Simply Asking")
  • Do not imply partnership or endorsement unless authorized
  • Follow our brand guidelines for logo usage

9.2 Trademark Usage

  • You may not use "Simply Asking" or our logos without permission
  • Approved integration partners may use our "Works with Simply Asking" badge
  • Contact support@simplyasking.io for brand asset requests

10. Monitoring and Enforcement

10.1 Monitoring

We monitor API usage to:

  • Ensure compliance with these terms
  • Detect and prevent abuse
  • Optimize system performance
  • Provide usage analytics to customers

10.2 Enforcement Actions

If we determine you've violated these API Terms, we may:

  • Issue a warning
  • Temporarily suspend API access
  • Permanently revoke API access
  • Terminate your account
  • Take legal action

We will attempt to notify you before taking enforcement action, except in cases of:

  • Serious security threats
  • Illegal activity
  • Risk of harm to other users

11. Liability and Indemnification

11.1 Disclaimers

THE APIS ARE PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND. WE DO NOT GUARANTEE:

  • Uninterrupted or error-free operation
  • That the APIs will meet your requirements
  • The accuracy or reliability of any data

11.2 Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, OUR LIABILITY FOR ANY CLAIMS ARISING FROM YOUR USE OF THE APIS IS LIMITED TO THE AMOUNT YOU PAID US IN THE 12 MONTHS PRECEDING THE CLAIM.

11.3 Indemnification

You agree to indemnify and hold us harmless from any claims, damages, or expenses arising from:

  • Your use of the APIs
  • Your API Client
  • Your violation of these API Terms
  • Any third-party claims related to your API Client

12. Termination

12.1 By You

You may stop using the APIs at any time. Delete your API Credentials and cease all API access.

12.2 By Us

We may suspend or terminate your API access:

  • For violation of these terms
  • For non-payment
  • If required by law
  • If we discontinue the APIs
  • At our discretion with 30 days notice

12.3 Effect of Termination

Upon termination:

  • Your API Credentials become invalid
  • You must stop using the APIs
  • You must delete any cached API data
  • Provisions that should survive termination (indemnification, limitation of liability) will survive

13. Changes to API Terms

We may update these API Terms. We will:

  • Post the updated terms on our website
  • Update the "Last Updated" date
  • Notify you of material changes via email or in-app notification
  • Give you 30 days notice before changes take effect

Continued use of the APIs after changes take effect constitutes acceptance.

14. Contact

API Support: support@simplyasking.io Security Issues: security@simplyasking.io Legal Questions: legal@simplyasking.io Partnership Inquiries: support@simplyasking.io

By using the Simply Asking APIs, you acknowledge that you have read, understood, and agree to be bound by these API Terms of Service.