> ## Documentation Index > Fetch the complete documentation index at: https://docs.vocobase.com/llms.txt > Use this file to discover all available pages before exploring further. # Update an agent's inbound configuration > Updates the inbound face's configuration. Takes the same body as `PUT /agent/{id}`, so the inbound side of an agent can have its own prompt, greeting, voice, and behaviour. `agent_name` and `project_id` are ignored if sent — the face inherits both from the parent and may never drift, because pricing is resolved from the serving agent's project. ## OpenAPI ````yaml /openapi.json put /agent/{id}/inbound/config openapi: 3.1.0 info: title: Vocobase API version: '2.0' description: >- API for managing voice AI agents, documents, and calls on the Vocobase platform. servers: - url: https://api.vocobase.com/api/v2 description: Production security: - bearerAuth: [] tags: - name: Config description: >- Read and update account configuration, webhook settings, and telephony credentials. - name: Agents description: Create, read, update, and delete voice AI agents. - name: Voices description: >- List voice tiers, available voices, and stream preview audio for agent configuration. - name: Documents description: Upload, manage, and delete knowledge base documents. - name: Agent Documents description: Link and unlink documents to agents for knowledge base integration. - name: Calls description: Initiate outbound calls and view call history. - name: Phone Numbers description: >- Import DIDs, assign agents for inbound routing, and re-sync carrier Application bindings. - name: Inbound Routing Policies description: >- Define pre-answer routing decisions for inbound calls before AI sessions are created. - name: Telephony Connections description: Create, list, rename, and disconnect named V2 telephony connections. - name: VoiceLink Management description: Manage VoiceLink reseller clients, DID mapping, and readiness sync. - name: Projects description: Organize agents into projects. Every agent belongs to exactly one project. - name: Dictionaries description: Speech-recognition dictionary CRUD and agent attachment. - name: Sessions description: Browser-initiated WebRTC voice sessions for in-app voice agents. - name: Campaigns description: Batch outbound calling. - name: Billing description: Balance, transactions, and usage summaries. - name: Custom Functions description: HTTP endpoints the agent can call mid-conversation. - name: Extraction Sets description: Reusable sets of post-call extraction fields. - name: Lifecycle Hooks description: Automatic pre-call and post-call integration steps. - name: Messaging description: Bring-your-own WhatsApp sending. - name: Integration Logs description: Audit trail for integration calls. - name: Connectors description: Catalog of tools an agent can be connected to. - name: Customers description: B2B2B sub-tenants and their tool connections. - name: Agent Tools description: Binding connectors and connections to an agent. paths: /agent/{id}/inbound/config: put: tags: - Agents summary: Update an agent's inbound configuration description: >- Updates the inbound face's configuration. Takes the same body as `PUT /agent/{id}`, so the inbound side of an agent can have its own prompt, greeting, voice, and behaviour. `agent_name` and `project_id` are ignored if sent — the face inherits both from the parent and may never drift, because pricing is resolved from the serving agent's project. operationId: updateAgentInboundConfig parameters: - name: id in: path required: true schema: type: string format: uuid description: Agent ID. Always the parent. requestBody: required: true content: application/json: schema: type: object additionalProperties: true description: >- Same shape as the `PUT /agent/{id}` body, minus `agent_name` and `project_id`. The opening line is `intro_message`; a field named `greeting` is ignored. example: prompt: You are answering inbound support calls for Northwind. intro_message: Thanks for calling Northwind support, how can I help? responses: '200': description: Success. content: application/json: schema: type: object properties: success: type: boolean const: true data: type: object additionalProperties: true description: The updated inbound face, in the same shape as an agent. example: success: true data: id: f1e2d3c4-b5a6-7890-abcd-ef1234567890 intro_message: Thanks for calling Northwind support, how can I help? '400': $ref: '#/components/responses/ValidationError' '401': $ref: '#/components/responses/Unauthorized' '404': description: >- Agent not found, or `INBOUND_NOT_ENABLED` when the agent has no inbound face yet. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: INBOUND_NOT_ENABLED message: Inbound is not enabled for this agent '429': $ref: '#/components/responses/RateLimitExceeded' '500': $ref: '#/components/responses/InternalError' components: responses: ValidationError: description: Validation error in request body or parameters. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: VALIDATION_ERROR message: agent_name is required and must be max 50 characters Unauthorized: description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: UNAUTHORIZED message: Invalid or missing API key RateLimitExceeded: description: Per-account rate limit exceeded. Retry after a short backoff. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: RATE_LIMITED message: Rate limit exceeded. Retry after 60 seconds. InternalError: description: Unexpected server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: INTERNAL_ERROR message: An unexpected error occurred schemas: ErrorResponse: type: object properties: success: type: boolean const: false error: type: object properties: code: type: string message: type: string required: - code - message required: - success - error securitySchemes: bearerAuth: type: http scheme: bearer description: >- API key in format: `rg_live_xxxx`. Pass as a Bearer token in the Authorization header. ````