POST /feeds
Creates a new external feed for dynamic content in email campaigns.
Use this to:
- Set up external data sources for dynamic content
- Configure authentication for protected feeds
- Enable real-time content updates in campaigns
- Establish connections to product catalogs, blogs, or APIs
Key information returned:
- Created feed UUID for reference in campaigns
- Success confirmation
Important considerations:
- Feed URL must be accessible from Brevo infrastructure
- Authentication credentials are securely encrypted
- Test feed accessibility before campaign use
- Consider feed response time for campaign performance
- Monitor feed reliability and uptime
- Use caching for frequently accessed feeds
- Maximum 5 retry attempts allowed for failed requests
- Custom headers support for API integration requirements
Servers
- https://api.brevo.com/v3
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
username |
String | No |
Username for basic authentication (required if authType is 'basic') |
name |
String | Yes |
Name of the feed |
url |
String | Yes |
URL of the external data source |
maxRetries |
Integer | No |
Maximum number of retry attempts for failed requests Default value: 5 |
cache |
Boolean | No |
Whether to cache the feed response Default value: false |
token |
String | No |
Token for token-based authentication (required if authType is 'token') |
authType |
String | No |
Authentication type for accessing the feed Valid values:
Default value: "noAuth" |
password |
String | No |
Password for basic authentication (required if authType is 'basic') |
headers[] |
Array | No |
Custom HTTP headers for the feed request |
headers[].name |
String | Yes |
Header name |
headers[].value |
String | Yes |
Header value |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.