---
title: "Run a scheduled mapper now"
method: POST
path: "/v1/import/mappers/{id}/run"
tags: ["Import"]
---

# Run a scheduled mapper now

`POST /v1/import/mappers/{id}/run`

## Request

- Base URL: `https://api.prod.keyban.io`
- URL: `https://api.prod.keyban.io/v1/import/mappers/{id}/run`
- Auth: API key in header `X-Api-Key`

Trigger an immediate fetch-and-import of a scheduled (`url`) mapper, without waiting for its next scheduled occurrence and without altering the schedule. The run executes asynchronously through the exact same pipeline as a scheduled occurrence and shows up in the import history with `source = scheduled`; the response names its import job so it can be followed right away (`GET /v1/imports/:importId`). Two runs of the same mapper never overlap: while one is still importing the endpoint answers 409 (`IMPORT_RUN_IN_PROGRESS`).

## Path parameters

- `id` string, uuid, required

## Response `202`

Run enqueued

- ImportMapperRunDto
  - `importId` string, required: Identifier of the import job carrying the run, as exposed by `GET /v1/imports` — follow its progress there (`data.source = scheduled`).

## Other responses

- `400`: The mapper is not a scheduled (url) mapper
- `409`: A run of this mapper is still importing

---

[API](https://skmtc.dev/keyban/apis/keyban-rest-apis.md) · [All operations](https://skmtc.dev/keyban/apis/keyban-rest-apis/llms.txt) · [OpenAPI document](https://skmtc.dev/keyban/apis/keyban-rest-apis/revisions/0bb79a1da961?raw)