Guide · Integration

Anaplan API: how to find action, import, export and process IDs

By Umang Chauhan · November 14, 2026 · 6 min read

The five IDs an Anaplan Integration API call needs, where to find each one, and how to run a process from a script with your own token.

ID{ }200

To run an Anaplan process from a script or scheduler you need the right IDs in the right URL. None of them are shown in the main modelling screens, which is why people end up hunting for them in browser tools. Here is what you need and where it lives.

The IDs an Integration API call uses

From a name you recognise to an ID the API accepts

  1. Workspace ID

    Which workspace

  2. Model ID

    Which model in it

  3. Action ID

    Process, import, export or other action

  4. File ID

    Only for imports and exports that use a file

Anaplan calls resolve a workspace, a model and then one object inside it.
  • Workspace ID and model ID identify where the model lives. The Model Summary in Anaplan Toolkit shows them for the model you have open.
  • Process, import, export and action IDs identify what to run. Actions & File IDs lists every one with a one-click copy, searchable by name.
  • File IDs identify the file an import reads or an export writes, which you need when you upload or download data around a run.

Running a process

With the IDs and a valid token, a process is started by a POST to its tasks endpoint. The shape, with placeholders, looks like this:

curl -X POST \
  "https://api.anaplan.com/2/0/workspaces/$WORKSPACE_ID/models/$MODEL_ID/processes/$PROCESS_ID/tasks" \
  -H "Authorization: AnaplanAuthToken $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"localeName": "en_US"}'

Imports, exports and other actions follow the same pattern with imports, exports or actions in place of processes. The response includes a task ID; request that task to see whether the run succeeded.

A tidy workflow

  1. Open the model and the Toolkit panel, then choose Actions & File IDs.
  2. Search for the process by name and copy its ID.
  3. Open Process Steps to confirm the order of the actions inside it.
  4. Check Lock Monitor if you plan to trigger the run on a schedule, so you know when the model is usually free.
  5. Store IDs in your scheduler's configuration, not in the script, so a model copy can be pointed at without code changes.

IDs change when a model is copied, so scripts that target a production model need its own set. That matters for releases too; see ALM and revision tags.

Do this audit in minutes, not days

Anaplan Toolkit is a free Chrome and Firefox extension that reads the structure of the model you have open: modules, line items, lists, formulas, usage and storage. It talks only to Anaplan and sends nothing anywhere else.

Get Anaplan Toolkit

More guides

All Anaplan guides →