Skip to content
PIE V2 API

Update a service

PUT
/v2/clients/{client_id}/domains/{domain_id}/service/{service_id}
 
curl --request PUT \
  --url https://staging-pie.streamline.enterprises/v2/clients/client-1/domains/south_australia/service/service-1 \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "departure_datetime": "2026-04-15T12:00:00Z", "static_features": {} }'

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
client_id
required
string
Example 
client-1
domain_id
required
string
Example 
south_australia
service_id
required
string
Example 
service-1

Request Body

Section titled “Request Body ”
Media type application/json
object
departure_datetime
string format: date-time
static_features
object
Example generated
{
  "departure_datetime": "2026-04-15T12:00:00Z",
  "static_features": {}
}

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Service updated

Media type application/json
object
domain_id
required
string
service_id
required
string
status
required
string
Allowed values: in_progress available failed not_found
departure_datetime
required
string format: date-time
provided_features
required

Raw features the caller sent at init time (may be a subset)

object
resolved_features
required

Full features after applying domain defaults (what was used for inference)

object
created_at
required
string format: date-time
updated_at
required
string format: date-time
Example 
{
  "domain_id": "south_australia",
  "service_id": "service-1",
  "status": "available",
  "departure_datetime": "2025-07-01T12:00:00Z",
  "provided_features": {
    "route": "Adelaide to Sydney"
  },
  "resolved_features": {
    "route": "Adelaide to Sydney",
    "on_demand": true
  },
  "created_at": "2025-01-15T10:00:00Z",
  "updated_at": "2025-01-16T08:00:00Z"
}

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
}