For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Help CenterAPI KeysStatusSign In
GuidesAPI ReferenceChangelog
GuidesAPI ReferenceChangelog
  • Introduction
    • Getting started
  • Email API
  • Transactional SMS
  • Transactional WhatsApp
  • Marketing Campaigns
  • Contact Management
  • Events
    • GETGet events
    • POSTCreate an event
    • POSTCreate events in batch
  • Object Management
  • Accounts and Settings
      • GETGet all external feeds
      • POSTCreate external feed
      • GETGet external feed details
      • PUTUpdate external feed
      • DELDelete external feed
  • Sales CRM
  • Conversations
  • Ecommerce
  • Loyalty
LogoLogo
Help CenterAPI KeysStatusSign In
Accounts and SettingsExternal Feeds

Update external feed

PUT
https://api.brevo.com/v3/feeds/:uuid
PUT
/v3/feeds/:uuid
1import { BrevoClient } from "@getbrevo/brevo";
2
3async function main() {
4 const client = new BrevoClient({
5 apiKey: "YOUR_API_KEY_HERE",
6 });
7 await client.externalFeeds.updateExternalFeed("b1c2d3e4-f5a6-47b8-89c0-d1e2f3a4b5c6", {
8 name: "Updated Product Catalog",
9 url: "https://api.newstore.com/products/v2",
10 });
11}
12main();
Updates configuration of an existing external feed. **Use this to:** - Update feed URLs when data sources change - Modify authentication credentials - Change cache and retry settings - Update custom headers - Rename feeds for better organization **Key information returned:** - Success confirmation message **Important considerations:** - Only provided fields will be updated - Feed UUID must exist in your account - Authentication changes require verification - URL changes should be tested before campaign use - Monitor campaigns using this feed after updates
Was this page helpful?
Previous

Delete external feed

Next
Built with

Updates configuration of an existing external feed.

Use this to:

  • Update feed URLs when data sources change
  • Modify authentication credentials
  • Change cache and retry settings
  • Update custom headers
  • Rename feeds for better organization

Key information returned:

  • Success confirmation message

Important considerations:

  • Only provided fields will be updated
  • Feed UUID must exist in your account
  • Authentication changes require verification
  • URL changes should be tested before campaign use
  • Monitor campaigns using this feed after updates

Authentication

api-keystring

The API key should be passed in the request headers as api-key for authentication.

Path parameters

uuidstringRequiredformat: "uuidv4"
UUID of the feed to update

Request

Feed configuration updates
namestringOptional
Name of the feed
urlstringOptionalformat: "url"
URL of the external data source
authTypeenumOptional
Authentication type for accessing the feed
Allowed values:
usernamestringOptional
Username for basic authentication
passwordstringOptional
Password for basic authentication
tokenstringOptional

Token for token-based authentication

headerslist of objectsOptional
Custom HTTP headers for the feed request
maxRetriesintegerOptional1-5
Maximum number of retry attempts for failed requests
cachebooleanOptional
Whether to cache the feed response

Response

External feed updated successfully

Errors

400
Bad Request Error
404
Not Found Error