Skip to main content
Replace an endpoint’s target list. The new list can use a different provider than the old one, so you can move a live slug between a Dedicated deployment and another supported target without renaming it. Endpoint slugs are immutable. To use a different slug, create a new endpoint and delete the old one. The PATCH request doesn’t accept slug.

Errors

Authorizations

Authorization
string
header
required

Send Authorization: Bearer <api_key>. The legacy Authorization: Api-Key <api_key> scheme is also accepted.

Path Parameters

endpoint_id
string
required

Body

application/json

PATCH body. Replaces the endpoint's full target list. The slug is immutable after creation; to change it, create a new endpoint and delete this one.

targets
EndpointTargetRequestV1 · object[] | null

The endpoint's upstream targets. Exactly one target is supported at this time.

Required array length: 1 element
Example:

Response

200 - application/json

A Gateway endpoint: a slug and its priority-ordered targets (index 0 tried first).

id
string
required

Stable identifier for the endpoint.

slug
string
required

Globally-unique routing slug.

Example:

"baseten/mymodel-4"

region
enum<string>
required

Region this endpoint's routing serves.

Available options:
UNRESTRICTED,
EU
created_at
string<date-time>
required

Creation time, ISO 8601.

updated_at
string<date-time>
required

Last update time, ISO 8601.

targets
EndpointTargetV1 · object[]
required

The endpoint's upstream targets. Exactly one target is supported at this time.