Connection details for a robot client (ADR 0145 §4). Read-tier because it hands out a dial target and the deployment's own token, not because it is harmless — the token is the credential guarding both wires, so the response carries no internal Kubernetes identifier.
POST
/v1/inference-deployments/{inferenceDeploymentId}/connectioncurl -X POST 'https://api.embodiflow.io/v1/inference-deployments/{inferenceDeploymentId}/connection' \
-H 'Authorization: Bearer $EMBODIFLOW_PAT'Authorization
Send a personal access token with every request.
- Authorization: Bearer PAT
Path parameters
- inferenceDeploymentIdstringrequired
Responses
Success
- dataobjectrequired
- inferenceDeploymentIdstringrequired
- wiresarray<InferenceConnectionWireDto>required
- tokenstring | nullrequired
- issuedAtstringrequired
- expiresAtstring | nullrequired
- unmodifiedClientGuidancestringrequired
Response example
{
"data": {
"inferenceDeploymentId": "string",
"wires": [
{
"protocol": "openpi-ws",
"target": "string",
"tls": false
}
],
"token": "string",
"issuedAt": "string",
"expiresAt": "string",
"unmodifiedClientGuidance": "string"
}
}Servershttps://api.embodiflow.io/v1https://api.embodiflow.dev/v1