Skip to content

API Sandbox

Try any documented endpoint directly from this page. Requests are sent from your browser to the environment in "API base URL" (by default the host serving these docs), using your own credentials.

This is not a simulated environment

Calls run against real data for the account behind your credentials. Write endpoints (*_add, *_edit, *_save) create or change real records. Prefer a test account.

Endpoints authenticate with your api_secret_key (Profile > API Access Data in the manager dashboard).

How the sandbox handles your credentials

  • Credentials live in memory for the current page only. Nothing is written to localStorage or sessionStorage, so a key cannot be read back by other scripts on this origin after you navigate away. Only the non-secret "API base URL" is remembered.
  • The api_secret_key is always sent in the request body, never in the query string, so it cannot end up in browser history or server access logs. To do that, the sandbox issues v2 calls as POST even for endpoints documented as GET - the API accepts the key from the body, and endpoint parameters are still sent in the query string. Your own integration can use the documented GET form shown on each endpoint page; if you do, treat the resulting URLs as secrets.
This sandbox sends real requests to the environment in "API base URL", which is limited to this site's own origin and the production host. Requests with your credentials read and write real data. Endpoints that create, change or delete records need an explicit confirmation before each send, and that confirmation resets whenever you switch endpoint. Credentials are kept in memory for this page only: nothing is stored in the browser, and keys are sent in the request body rather than the URL.