> ## Documentation Index > Fetch the complete documentation index at: https://bavlio.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Update Sender Profile > Update an existing sender profile. Updates a sender profile if the authenticated user has access. Only provided fields will be updated - omitted fields remain unchanged. Args: profile_id: The ID of the profile to update updates: The fields to update current_user: Authenticated user information settings: Application settings Returns: The updated sender profile Raises: HTTPException: If profile not found or access denied ## OpenAPI ````yaml https://api.bavlio.com/openapi.json put /api/v1/sender-profiles/{profile_id} openapi: 3.1.0 info: title: Bavlio API description: >- Outreach automation API — lead enrichment, email campaigns, LinkedIn automation, and AI agent. Full docs at https://docs.bavlio.com. version: 1.0.0 servers: [] security: [] tags: - name: API Keys description: >- Create, list, and revoke API keys for programmatic access. JWT authentication required. - name: credits description: Credit balance, cost estimates, and transaction history. - name: campaigns description: Create, manage, launch, and monitor email campaigns. - name: campaign-personalization description: AI-powered email subject and body personalization for campaigns. - name: email-finder description: Find and verify email addresses for prospects. - name: email-verification description: Validate email addresses and prune invalid entries from datasets. - name: sender-profiles description: Manage sender identity profiles for outreach. - name: sender-profile-chat description: Interactive chat for building sender profiles. - name: templates description: Email template CRUD. - name: suppression description: Do-not-contact suppression list management. - name: datasets description: Lead dataset listing, download, and updates. - name: user-extractions description: Uploaded lead file management and processing. - name: enrichment-chat description: Interactive chat for data enrichment sessions. - name: enrichment-processing description: Batch lead enrichment processing. - name: File Upload (CSV/Excel) description: Upload and preview CSV/Excel lead files. - name: connected-accounts description: LinkedIn account connections via Unipile. - name: linkedin-content description: LinkedIn post creation, scheduling, and management. - name: linkedin-playground description: Direct LinkedIn actions (profile lookup, messaging, engagement). - name: bavimail-proxy description: BaviMail domain, alias, and email management. - name: agent description: Bavi AI agent chat with SSE streaming. - name: notifications description: Notification preferences and delivery. - name: referral description: Referral code management and stats. - name: feedback description: User feedback submission. - name: authentication description: JWT token verification and user info. - name: Google OAuth description: Google OAuth login flow and access tokens. - name: Google Sheets OAuth description: Google Sheets import and access management. - name: stripe description: Stripe checkout, billing portal, and subscription status. JWT only. - name: users description: User quota and usage information. - name: Health description: Health checks and system status. - name: Personalization description: Core lead personalization engine. - name: Session Management description: Enrichment session lifecycle. - name: Session Processing description: Session data processing. - name: webhooks description: Inbound webhook handlers (Stripe, BaviMail, Unipile). paths: /api/v1/sender-profiles/{profile_id}: put: tags: - sender-profiles summary: Update Sender Profile description: |- Update an existing sender profile. Updates a sender profile if the authenticated user has access. Only provided fields will be updated - omitted fields remain unchanged. Args: profile_id: The ID of the profile to update updates: The fields to update current_user: Authenticated user information settings: Application settings Returns: The updated sender profile Raises: HTTPException: If profile not found or access denied operationId: update_sender_profile_api_v1_sender_profiles__profile_id__put parameters: - name: profile_id in: path required: true schema: type: string title: Profile Id requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SenderProfileUpdate' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/SenderProfile' '401': description: Unauthorized - Invalid or missing JWT token '403': description: Forbidden - Insufficient permissions '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' '429': description: Too Many Requests - Rate limit exceeded security: - HTTPBearer: [] components: schemas: SenderProfileUpdate: properties: profile_name: anyOf: - type: string maxLength: 100 minLength: 1 - type: 'null' title: Profile Name description: New name for the profile description: anyOf: - type: string maxLength: 500 - type: 'null' title: Description description: New description sender_data: anyOf: - additionalProperties: true type: object - type: 'null' title: Sender Data description: New sender data (replaces existing data completely) is_default: anyOf: - type: boolean - type: 'null' title: Is Default description: Whether this should be the default profile type: object title: SenderProfileUpdate description: Request model for updating a sender profile. SenderProfile: properties: id: anyOf: - type: string - type: 'null' title: Id description: Unique profile identifier user_id: type: string title: User Id description: User ID who owns this profile profile_name: type: string maxLength: 100 minLength: 1 title: Profile Name description: >- User-friendly name for this profile (e.g., 'Sales Team Profile', 'Personal Brand') description: anyOf: - type: string maxLength: 500 - type: 'null' title: Description description: Optional description of when/how to use this profile sender_data: $ref: '#/components/schemas/DynamicSenderData' description: The actual sender data with arbitrary fields created_at: anyOf: - type: string format: date-time - type: 'null' title: Created At description: Profile creation timestamp updated_at: anyOf: - type: string format: date-time - type: 'null' title: Updated At description: Last update timestamp usage_count: type: integer title: Usage Count description: Number of times this profile has been used default: 0 is_default: type: boolean title: Is Default description: Whether this is the default profile default: false type: object required: - user_id - profile_name - sender_data title: SenderProfile description: >- Sender profile model for storing reusable sender configurations. This model stores a named profile containing DynamicSenderData, which can have ANY arbitrary fields. There is no predefined schema for the sender data. Examples of valid sender data: - {"full_name": "John", "company": "TechCorp", "role": "Sales"} - {"sender_name": "Jane", "brand": "AI Solutions", "linkedin": "jane-doe"} - {"name": "Bob", "agency": "Marketing Pro", "phone": "+1234", "timezone": "EST"} - Any other combination of fields the user needs HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError DynamicSenderData: properties: data: additionalProperties: true type: object title: Data description: Raw sender data with variable columns type: object required: - data title: DynamicSenderData description: Flexible sender data model for handling variable columns. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ````