---
title: "Controller Handle Commit Predict"
method: POST
path: "/integrations/commit/predict"
tags: ["integrations"]
---

# Controller Handle Commit Predict

`POST /integrations/commit/predict`

Represents a user formally submitting an ad-hoc import and persistent prediction schedule.

## Request body

- CommitPredictPayload
  - `flow_id` string, required — Flow ID these predictions will be run off of. Important to specify because this is how we track down the exact model we'll use for predictions.
  - `connection_id` string, nullable — Connection ID to use for credentials. If not provided, we use the connection attached to the flow (older meltano deployments)] = None.
  - `specifier` object, required — The specifier specifying the table where we'll be importing data from. For now, we derive the output table name from this table rather than allowing user-specified output table names.
  - `mappings` object — Field mappings, useful incase you are trying to run on a table with the same information but different column names. Keys of the object are keys on the table we'll be running predictions on, Values of the object are keys on our training table.
  - `blocking` boolean, nullable — Whether or not to block until full job is done. For backwards compatbility with old UI
  - `step_title` string, nullable — Which deployment user-friendly name (Snowflake, Postgres, etc) is running
  - `step_key` string, nullable — Which deployment key (postgre-sql-output, etc) is running

## Response `201`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/akkio/apis/fastapi.md) · [All operations](https://skmtc.net/akkio/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/akkio/fastapi/revisions/6662a407c637/schema)
