Brevo · Schema
redeem
MarketingMarketing AutomationEmail MarketingTransactional EmailSMS MarketingWhatsAppCampaignsCRMSalesE-CommerceLoyaltyEventLive ChatEmailSMSAutomationMessagingContacts
Properties
| Name | Type | Description |
|---|---|---|
| cancelledAt | string | Timestamp when the redemption was cancelled |
| completedAt | string | Timestamp when the redemption was completed |
| contactId | integer | Unique identifier for the contact |
| createdAt | string | Timestamp when the redemption was created |
| debitTransactionId | string | Unique identifier for the debit transaction |
| expiresAt | string | Timestamp when the redemption expires |
| id | string | Unique identifier for the redemption |
| loyaltyProgramId | string | Unique identifier for the loyalty program |
| meta | object | Additional metadata associated with the redemption |
| rejectReason | string | Reason for rejection if the redemption was rejected |
| rejectedAt | string | Timestamp when the redemption was rejected |
| rewardAttributionId | string | Unique identifier for the reward attribution |
| status | string | Current status of the redemption |
| updatedAt | string | Timestamp when the redemption was last updated |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/brevo/main/json-schema/brevo-redeem-schema.json",
"title": "redeem",
"x-generated": "2026-10-12",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/brevo-reward-api-openapi.yml#/components/schemas/redeem",
"type": "object",
"properties": {
"cancelledAt": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the redemption was cancelled"
},
"completedAt": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the redemption was completed"
},
"contactId": {
"type": "integer",
"format": "int64",
"description": "Unique identifier for the contact"
},
"createdAt": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the redemption was created"
},
"debitTransactionId": {
"type": "string",
"format": "uuid",
"description": "Unique identifier for the debit transaction"
},
"expiresAt": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the redemption expires"
},
"id": {
"type": "string",
"format": "uuid",
"description": "Unique identifier for the redemption"
},
"loyaltyProgramId": {
"type": "string",
"format": "uuid",
"description": "Unique identifier for the loyalty program"
},
"meta": {
"type": "object",
"additionalProperties": {
"description": "Any type"
},
"description": "Additional metadata associated with the redemption"
},
"rejectReason": {
"type": "string",
"description": "Reason for rejection if the redemption was rejected"
},
"rejectedAt": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the redemption was rejected"
},
"rewardAttributionId": {
"type": "string",
"format": "uuid",
"description": "Unique identifier for the reward attribution"
},
"status": {
"type": "string",
"description": "Current status of the redemption"
},
"updatedAt": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the redemption was last updated"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/brevo-redeem"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.