API Terms of Service#

These terms apply when you use mnemonic’s APIs. They are meant to be simple and practical. By using the API, you agree to follow these terms.

1. Scope and Access#

The API is available to:

  • Customers with a valid agreement with mnemonic

  • Third parties that are authorized by the customer or by mnemonic

We grant access based on the relevant customer agreement, technical setup, and security requirements.

We may suspend or revoke access if needed for security, operational, or contractual reasons. This includes, but is not limited to, the following situations:

  • The customer agreement is terminated

  • A user account is disabled

  • We detect misuse, security issues, or behavior that puts our systems or data at risk

2. Permitted Use / Restrictions#

The API may be used for legitimate customer purposes, such as integrating mnemonic services and data with your own internal systems, workflows, and security processes.

You must not:

  • Reverse engineer the API or related services, except where this is explicitly allowed by law

  • Use the API in a way that creates abuse, excessive load, or instability

  • Circumvent rate limits, access controls, or other security mechanisms

  • Use the API or data produced by mnemonic to build, support, or operate competing services without written consent from mnemonic

If you use the API in a third-party or multi-tenant setup, you are responsible for handling the data safely and in line with your agreement with mnemonic.

API credentials are personal to the assigned user or integration and must not be shared with third parties. You are also responsible for protecting any data returned by the service.

3. Authentication & Security Responsibilities#

You are responsible for protecting API keys, tokens, and other credentials used to access the API.

This means you must:

  • Store credentials securely

  • Limit access to people and systems that actually need them

  • Rotate or replace credentials when necessary, for example after suspected exposure or as part of normal security practice

  • Report suspected misuse, credential compromise, or other security incidents to mnemonic without undue delay

mnemonic may suspend credentials that appear to be compromised or that exceed fair or acceptable use, in order to protect the service and other users.

4. Rate Limits & Usage Policies#

Some services have technical rate limits. Where such limits are in place, it is your responsibility to handle API responses according to the API documentation.

For all services, mnemonic may notify you if your usage is too high or otherwise problematic. If we do, you must follow the instructions we give without undue delay.

Accounts or integrations that significantly exceed allowed usage may be disabled without notice if this is necessary to protect our systems.

You are expected to avoid unnecessary polling, excessive re-fetching, or other inefficient usage patterns. If an integration causes problematic traffic, mnemonic may require you to change how it fetches or processes data.

5. Availability & Support#

If you have questions about API usage, you can contact developers@mnemonic.no.

We do not guarantee uninterrupted availability unless that is explicitly stated in your agreement with mnemonic.

6. Versioning & Breaking Changes#

You are expected to follow our API compatibility and deprecation policy:

https://docs.mnemonic.no/api/general_integration_guide/01-compatibility_deprecation.html

It is your responsibility to keep your integration up to date with supported API versions and announced breaking changes.