Skip to content
PIE V2 API

Update an event subscription

PUT
/v2/models/{model_id}/event-subscriptions/{subscription_id}
 
curl --request PUT \
  --url https://staging-pie.streamline.enterprises/v2/models/model_price_reco_v1/event-subscriptions/6ba7b811-9dad-11d1-80b4-00c04fd430c8 \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "input": {}, "label": "example", "status": "active" }'

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
model_id
required
string
Example 
model_price_reco_v1
subscription_id
required
string format: uuid
Example 
6ba7b811-9dad-11d1-80b4-00c04fd430c8

Request Body required

Section titled “Request Body required ”
Media type application/json
object
input
object
label
string
nullable
status
string
Allowed values: active paused stale

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Event subscription updated

Media type application/json
object
id
required
string format: uuid
source_model_id
required
string
trigger_event
required
string
Allowed values: training_complete inference_complete
target_model_id
required
string
target_action
required
string
Allowed values: inference training
input_source
required
string
Allowed values: stored trigger_output
input
object
label
string
nullable
status
required
string
Allowed values: active paused stale
created_at
required
string format: date-time
updated_at
required
string format: date-time
warnings

Present when the server detected issues that did not block the operation (e.g. stored subscription input did not validate against the target model’s handler input_schema). Omitted or empty when there are no warnings.

Array<string>
Example 
{
  "trigger_event": "training_complete",
  "target_action": "inference",
  "input_source": "stored",
  "status": "active"
}

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
}