> ## Documentation Index > Fetch the complete documentation index at: https://onlytraffic.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Update Pool > Change pool settings. Send only what changes: `daily_limits`, `publish_settings` and `target_weights` merge key by key, `hosts` and `targets` replace the lists when present. The same checks as on creation apply to the merged result. The status is not touched here; use [`POST /shoutouts/pools/{uuid}/status`](/docs/api/shoutouts-pools-status) to pause, resume or archive. An archived pool answers `422 pool_not_editable`. ## OpenAPI ````yaml POST /shoutouts/pools/{uuid} openapi: 3.0.3 info: title: OnlyTraffic Studio API version: 1.1.0 description: >- External API for OnlyTraffic Studio. Manage and retrieve data about your subscribers, CPL campaigns, CPC orders and CPC campaigns. servers: - url: https://studio-api.onlytraffic.com/api/external/v1 security: - ApiKeyAuth: [] tags: - name: Account description: API key holder's wallet, profile, and aggregate state. - name: Accounts description: OnlyFans accounts attached to the API key holder. - name: Agencies description: Agency CRUD and image management. All edits stage in moderation. - name: CPL description: >- Cost-per-lead orders: place, list, cancel, manage settings, browse partner offers. - name: CPC description: Cost-per-click orders and creative management. - name: RevShare description: Revenue-share campaigns and invoices. - name: Swaps description: Two-sided traffic swap orders and offers. - name: Subscribers description: Per-fan delivery feed (cursor-paginated). - name: Transactions description: Per-transaction OF revenue feed (cursor-paginated). - name: Shoutouts description: Cross-promo pools, creatives and the publication log. paths: /shoutouts/pools/{uuid}: post: tags: - Shoutouts summary: Update Pool description: Change pool settings. operationId: updateShoutoutPool parameters: - $ref: '#/components/parameters/ShoutoutPoolIdPath' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ShoutoutPoolUpdateRequest' responses: '200': description: Successful response content: application/json: schema: type: object properties: success: type: boolean example: true data: type: object properties: pool_id: type: string format: uuid example: 550e8400-e29b-41d4-a716-446655440000 '401': description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Pool not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: >- Validation error (same codes as create) or `pool_not_editable` for an archived pool content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: >- Server error. Body always reads `{success:false, error:"server_error", message:"Server error"}` (no internal details leak). content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: parameters: ShoutoutPoolIdPath: name: uuid in: path required: true schema: type: string format: uuid description: 'Pool id: the `pool_id` value from the pools list.' example: 550e8400-e29b-41d4-a716-446655440000 schemas: ShoutoutPoolUpdateRequest: type: object description: >- Only the fields sent change. `daily_limits`, `publish_settings` and `target_weights` merge key by key; `hosts` and `targets` replace the lists. properties: name: type: string maxLength: 100 formats: type: array items: type: string enum: - story - post - bio - friends - mass_dm start_date: type: string format: date end_date: type: string format: date nullable: true rotation_type: type: string enum: - equal - priority - weighted daily_limits: type: object additionalProperties: type: integer minimum: 1 maximum: 20 same_target_cooldown_days: type: integer minimum: 1 maximum: 90 friends_ttl_days: type: integer enum: - 3 - 5 - 7 - 14 - 30 bio_ttl_days: type: integer enum: - 3 - 5 - 7 - 14 - 30 post_ttl_days: type: integer enum: - 1 - 3 - 5 - 7 publish_settings: $ref: '#/components/schemas/ShoutoutPublishSettings' hosts: type: array items: type: integer targets: type: array items: type: integer target_weights: type: object additionalProperties: type: integer minimum: 1 maximum: 5 ErrorResponse: type: object description: Standard error envelope for all 4xx/5xx responses. required: - success - error - message properties: success: type: boolean enum: - false description: Always false on error responses. error: type: string description: Stable snake_case machine-readable error code. Branch on this. example: validation_failed message: type: string description: >- Human-friendly text. For 5xx this is always the literal `Server error`. For 4xx an actionable validation/auth message is returned. details: type: object nullable: true description: >- Optional per-field diagnostic information. On 422 carries `{: ["error_code", ...]}`. On 402 (`insufficient_balance`) carries `{required, current}`. On 426 (`unpaid_invoices`) carries `{count, total, oldest_date_ts}`. Absent on most other errors. additionalProperties: true retry_after: type: integer nullable: true description: >- Seconds until the next request will succeed. Present only on 429 responses (rate limit). Mirrors the `Retry-After` HTTP header. ShoutoutPublishSettings: type: object description: How publications go out. properties: pin_posts: type: boolean description: Pin promo posts on top of the publisher's profile. post_media_mode: type: string enum: - carousel - random description: >- All photos of the creative in one post, or one random photo per post. vault_cleanup: type: boolean description: Hide the published media from the publisher's vault afterwards. vault_folder: type: boolean description: >- File the published media into the OT Shoutouts vault folder (ignored while `vault_cleanup` is on). mass_dm: $ref: '#/components/schemas/ShoutoutMassDmSettings' ShoutoutMassDmSettings: type: object description: Mass message audience and behaviour. properties: send_to: type: array items: type: string maxLength: 50 maxItems: 20 description: >- OnlyFans list names the message goes to, matched by name on every publisher (the built-in `Fans`, `Following` or your own lists). Required while the `mass_dm` format is on. example: - Fans exclude_lists: type: array items: type: string maxLength: 50 maxItems: 20 description: >- List names removed from the audience; `*` stands for any characters (`Alt*`). example: - Alt* unsend_previous: type: boolean description: >- Unsend the earlier promo mailing that reached the same fans before a new one goes out. default: true securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: Your API key from the Studio Dashboard ````