For the complete documentation index, see llms.txt. This page is also available as Markdown.

Opt Out Offer

Opt-out Offer

post

The Opt-out Offer endpoint is used to record when a customer declines an offer. This helps track conversion rates and customer preferences.

Authorizations
AuthorizationstringRequired

Composite Authentication Scheme (Client Key, Date, and Signature)

This scheme requires the client to provide three mandatory headers in every request:

1. X-Api-Key (Client Key)

  • Purpose: Public identifier for the API consumer.
  • Example: X-Api-Key: a1b2c3d4e5f6g7h8

2. Date (Timestamp)

  • Purpose: Timestamp used for generating the signature and preventing replay attacks.
  • Format: RFC 7231 format (e.g., in GMT).
  • Example: Date: Sun, 09 Nov 2025 04:04:00 GMT

3. Authorization (Computed Signature)

  • Purpose: The cryptographic signature that verifies the request's authenticity and integrity.
  • Format: SIGNATURE [authHeader]

Signature Generation Logic: The authHeader value is derived from a cryptographic hash (e.g., HMAC-SHA256) of canonical request components (HTTP Method, Path, and the contents of the Date header), signed with the private Client Secret.

Path parameters
partner_codestringRequired

Partner code identifier. Client Solutions Engineer (CSE) should provide this value.

offer_idstringRequired

The offer ID returned from the Create Offer endpoint.

Responses
204

No Content - Opt-out recorded successfully

No content

post/partners/{partner_code}/offers/{offer_id}/opt_out/
POST /x/partners/{partner_code}/offers/{offer_id}/opt_out/ HTTP/1.1
Host: api.xcover.com
Authorization: YOUR_API_KEY
Accept: */*

No content

Last updated

Was this helpful?