Skip to content
Who Sees What

‹ Developers

Who Sees What Developer Terms

Effective Date: These Developer Terms (Version 1.0) take effect on the date they are first published at whoseeswhat.com/legal/developer-terms.

These Developer Terms apply to anyone who writes code against, or configures an AI tool or agent to call, the Who Sees What REST API or MCP server (together, the “developer surfaces”), including a Customer’s own developers and any AI tool or agent acting on a Customer’s behalf. They supplement, and do not replace, the Digadop Terms of Service and the Acceptable Use Policy, both of which continue to apply. Capitalized terms not defined here have the meanings given in the Terms of Service. The developer surfaces are a Who Sees What Enterprise capability available only under the Customer’s own Order; nothing in these Developer Terms grants any right beyond what the Terms of Service and the applicable Order already grant.

Sample code license

The code samples published on the developer pages (the REST API, API reference, and MCP server pages) are licensed to you under the MIT No Attribution License (MIT-0). You may copy, modify, and reuse those samples for any purpose, with no attribution required. This license covers the samples only. It does not grant any right in the Who Sees What Service itself, which remains governed by the Terms of Service and the applicable Order.

Use by AI tools and agents

You may configure an AI tool or agent to call the documented Who Sees What REST API or MCP tools on your behalf, using a credential issued to your organization, provided the tool or agent stays within the documented API and MCP surfaces, within the Acceptable Use Policy, and within the published rate limits. A credential belongs to the Customer’s organization, not to an individual developer: it is created in the Who Sees What web app by a user with Salesforce org-admin rights, and it is scoped to one Salesforce org at the time it is minted (see Getting a credential). Configuring a tool or agent with a credential does not expand what that credential can see or do.

You are responsible for the actions an AI tool or agent takes with a credential issued to your organization, in the same way you are responsible for a script you write yourself.

Salesforce platform

Who Sees What calls Salesforce APIs on your behalf, under your own connected Salesforce org’s access and your own agreement with Salesforce. Every call made through the developer surfaces, including reads and the one documented setup write (whoseeswhat_setup_auditor_permission_set), runs on the one stored Salesforce connection Who Sees What holds for that org: the connection of the user who most recently connected the org in the Who Sees What web app, with that user’s full object and field permissions (see How a call works). What a call can read or change is therefore limited by the Connected Org your organization authorized and by that connecting user’s Salesforce permissions. It is not limited by the Salesforce permissions of the person, tool, or agent holding the credential, or of the administrator who created it. Using the developer surfaces does not modify your agreement with Salesforce.

Rate limits

The REST API and the MCP server share one rate limit, published on the MCP server page. This page does not restate those numbers; the MCP page is the single source.

Contact

Questions about these Developer Terms can be sent to legal@digadop.com.

Stony Point, Inc., doing business as Digadop 8742 Peachtree Park Ct, Windermere, FL 34786, USA


© 2026 Stony Point, Inc. d/b/a Digadop. Version 1.0, effective on first publication at whoseeswhat.com/legal/developer-terms.