API/MCP Terms of Use

Table of contents

Heading 2
Heading 3
Heading 4
Heading 5
Heading 6

Appendix 2 – Use of API and MCP

This appendix specifies the provisions of the agreement regarding the extent of the use of the DatAds software via API and MCP.

1. Subject Matter

This appendix applies to the use of the DatAds software via the following technical interfaces:

  • Public API at https://public.api.datads.io ("API"), authentication via API key;
  • MCP server at https://mcp.datads.io/mcp ("MCP"), authentication via OAuth.

Which endpoints and tools are available via API and MCP can be found in the current technical documentation at https://public.api.datads.io/docs.

2. Access and Authentication

2.1 API. Access is granted via an API key, which must be transmitted in the "x-api-key" header. One API key is valid for exactly one client (data area). If the customer has multiple clients, a separate key is generated for each client. Keys are generated in the dashboard and are displayed in full only at the time of generation; DatAds does not store them in plain text. Lost keys can be revoked and regenerated by the customer.

2.2 MCP. The connection is authorized using the credentials of a registered user and technically acts as that user; it accesses all data that this user can also access via the browser. The provisions of the agreement regarding user access ("Named User License") apply accordingly: an MCP connection is personally assigned to the authorizing user and may not be shared or used by other persons. The customer is responsible for all calls made via the connection.

2.3 Authorization of connections. MCP connections can only be established via providers and systems technically approved by DatAds. There is no entitlement to the approval of a specific provider. Connecting customer-owned or other non-approved systems is not covered by the contractually agreed remuneration and requires a separate agreement between the parties. DatAds is entitled to refuse approval, particularly if the intended use extends beyond the customer's own internal business purposes.

3. Usage Limits

The use of the API and MCP is subject to technical usage limits. These include, in particular, rate limits (number of permitted requests per time unit), request limits, limits for paginated data retrieval, and other volume and bandwidth restrictions.

Rate limits are applied per API key and per endpoint group or tool and may be tiered by time units. Additionally, caps per IP address may apply.

Upon conclusion of this agreement, the following rate limits apply:

Endpoint group Rate limit
Metadata: /v1/ad-accounts, /v1/campaigns, /v1/ad-groups, /v1/ads, /v1/ai-tags, /v1/metrics, /v1/industries 100 requests / minute
Insights: /v1/insights/breakdown, /v1/insights/charts, /v1/insights/stats 10 requests / minute
Benchmarks: /v1/benchmarks 10 requests / minute
Reports – overview: /v1/reports/{type} 100 requests / minute
Reports – retrieval: /v1/reports/{type}/{reportId}, /v1/reports/testing-log/{reportId}/comparison-cells 10 requests / minute
All endpoints, per IP address 50 requests / second

‍

The values above reflect the status at the time of contract conclusion. The values published in the technical documentation at https://public.api.datads.io/docs are authoritative. The customer is responsible for reviewing the values published there before and during use and for configuring their systems accordingly.

4. Historical data

Following the initial full data retrieval from the connected advertising accounts, data is available for a period of at least twelve months, provided the respective advertising platform makes this data available. Subsequently, the data is updated continuously, extending the retrievable period accordingly.

5. Consequences of exceeding limits

If a usage limit is exceeded, further requests will be rejected with an HTTP 429 ("Too Many Requests") status code until the current time window resets. Exceeding a limit does not automatically result in access being blocked. DatAds reserves the right to block access in the event of continued abusive behavior, either after prior notice or—if necessary for data and operational security—without prior notice.

6. Purpose limitation of retrieved data

Data retrieved via the API and MCP may be used by the customer exclusively for their own internal business purposes. Specifically, sharing or making data accessible to third parties, using it to provide services to third parties, integrating it into the customer's own products or services offered to third parties, or any form of resale is prohibited. The provisions of the contract remain unaffected.

7. Customer obligations

  • In the event of a response with a 429 status code or a server error (5xx), retry attempts must be performed using exponential backoff; repeated requests without a waiting period are prohibited.
  • Where technically feasible and reasonable, results should be cached on the customer's side to reduce avoidable requests.
  • Circumventing usage limits, particularly through the parallel use of multiple API keys, user accounts, or IP addresses for the same purpose, is prohibited.
  • API keys, tokens, and other authentication credentials must be treated as confidential in accordance with the contract and protected against unauthorized access by third parties.

8. Changes to usage limits, discontinuation of versions

8.1 DatAds reserves the right to adjust usage limits at any time. Adjustments are made by updating the technical documentation at https://public.api.datads.io/docs. The customer is responsible for complying with the values published there and for making any necessary adjustments to their own systems.

8.2 DatAds will notify the customer of the discontinuation of an API or MCP version at least 30 days prior to the effective date. The provisions of the service level agreement and update policy remain unaffected.

8.3 Notifications pursuant to Section 8.2 will be sent via email to the technical contact address provided by the customer: daniel@datads.io.

9. Availability

The availability of the API and MCP is subject to the terms of the service level agreement. DatAds publishes information on the current operational status at https://status.datads.io.

‍