Skip to content
PIE V2 API

Set model version status. When transitioning from training to active, any active event subscriptions for training_complete are automatically triggered.

POST
/v2/models/{model_id}/versions/{model_version}/new_status
 
curl --request POST \
  --url https://staging-pie.streamline.enterprises/v2/models/model_price_reco_v1/versions/1/new_status \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "status": "pending" }'

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
model_id
required
string
Example 
model_price_reco_v1
model_version
required
string
Example 
1

Request Body required

Section titled “Request Body required ”
Media type application/json
object
status
required
string
Allowed values: pending training active failed

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Model version status set

Media type application/json
object
model
required
object
id
required
string
name
required
string
description
required
string
handlers
required
object
training
required
One of:
object
type
required
string
Allowed value: lambda
arn
required
string
version
string
inference
required
One of:
object
type
required
string
Allowed value: lambda
arn
required
string
version
string
handler_contracts

Typed input/output contracts per handler type. When set, subscription staleness is driven by changes to these schemas rather than the handlers field. Contract fields are JSON Schema Draft 2020-12 documents.

object
training
object
input_schema

JSON Schema Draft 2020-12 document for the payload accepted by this handler. When set on inference, direct inference requests validate input against this schema before dispatch. Stored event-subscription payloads are validated against the target’s schema for the action (warnings-only on mismatch).

object
output_schema

JSON Schema Draft 2020-12 document for the handler’s successful output on job completion. Mismatches are logged as warnings but do not fail completion (external handlers may diverge).

object
inference
object
input_schema

JSON Schema Draft 2020-12 document for the payload accepted by this handler. When set on inference, direct inference requests validate input against this schema before dispatch. Stored event-subscription payloads are validated against the target’s schema for the action (warnings-only on mismatch).

object
output_schema

JSON Schema Draft 2020-12 document for the handler’s successful output on job completion. Mismatches are logged as warnings but do not fail completion (external handlers may diverge).

object
metadata
required
object
status
required
string
Allowed values: pending active
version
required
object
version
required
string
description
required
string
metadata
required
object
status
required
string
Allowed values: pending training active failed
triggered_events
required

Event subscriptions triggered by a training-to-active transition. Empty for other transitions.

Array<object>
object
subscription_id
required
string format: uuid
job_id

Present when the target action was successfully triggered

string
error

Present when the target action failed to trigger

string
Example 
{
  "model": {
    "id": "model_price_reco_v1",
    "name": "Price recommendation",
    "description": "Domain-level price model",
    "handlers": {
      "training": {
        "type": "lambda",
        "arn": "arn:aws:lambda:us-west-2:123456789012:function:train",
        "version": "1"
      },
      "inference": {
        "type": "lambda",
        "arn": "arn:aws:lambda:us-west-2:123456789012:function:infer"
      }
    },
    "handler_contracts": null,
    "metadata": {
      "team": "pricing"
    },
    "status": "active"
  },
  "version": {
    "status": "pending"
  }
}

400

Section titled “400 ”

Validation error — malformed input, invalid path parameters, or request that fails syntactic validation.

Media type application/json
object
success
required
boolean
message
required

Human-readable error message

string
Example 
{
  "success": false
}

401

Section titled “401 ”

Missing or invalid Authorization bearer token, expired token, or token rejected by the authorization layer (e.g. API Gateway JWT authorizer or application validation).

Media type application/json
object
success
required
boolean
message
required

Human-readable error message

string
Example 
{
  "success": false
}

403

Section titled “403 ”

Authenticated caller lacks the permission required for this operation.

Media type application/json
object
success
required
boolean
message
required

Human-readable error message

string
Example 
{
  "success": false
}

404

Section titled “404 ”

Requested resource was not found.

Media type application/json
object
success
required
boolean
message
required

Human-readable error message

string
Example 
{
  "success": false
}

422

Section titled “422 ”

Semantically invalid request — e.g. domain not active, no model assigned, feature contract mismatch, or invalid feature definitions.

Media type application/json
object
success
required
boolean
message
required

Human-readable error message

string
Example 
{
  "success": false
}