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.
Logo
Get supportSee a Demo
HomeAPI ReferenceSDKs
HomeAPI ReferenceSDKs
    • SDKs
    • WebView
  • API Reference
      • POSTCreate Attribution Events
      • POSTActivate Offer
      • POSTBoost Offer
      • POSTActivate Placement Slot
Get supportSee a Demo
API ReferenceAttributions

Activate Placement Slot

POST
/v2/issuers/:organizationId/users/:userId/placements/:placementId/slot/:slotId/activate
POST
/v2/issuers/:organizationId/users/:userId/placements/:placementId/slot/:slotId/activate
$curl -X POST https://rewards-api.getkard.com/v2/issuers/organization-123/users/user-123/placements/018f8d6b-1abc-7def-9012-345678901234/slot/slot-a/activate \
>     -H "Authorization: Bearer <token>"
1{
2  "data": {
3    "type": "placementSlotAttribution",
4    "id": "c94a93a7-beb9-4e58-960c-2c812f849398",
5    "attributes": {
6      "placementId": "018f8d6b-1abc-7def-9012-345678901234",
7      "slotId": "slot-a",
8      "eventCode": "ACTIVATE",
9      "medium": "CTA",
10      "eventDate": "2025-01-01T00:00:00Z",
11      "offerIds": [
12        "offer-1",
13        "offer-2",
14        "offer-3"
15      ]
16    }
17  }
18}
Record when a user activates a batch-activation placement slot. Writes a slot-level `placementSlotAttribution` ACTIVATE event and fans out a per-offer `offerAttribution` ACTIVATE event for every offer resolved by the slot's content strategy. The slot-level event id and the resolved `offerIds` are returned so the partner can render the batch immediately without an extra `getBatchesByPlacement` round-trip. <b>Required scopes:</b> `attributions:write`
Was this page helpful?
Previous

Get Files

Next
Built with

Record when a user activates a batch-activation placement slot. Writes a slot-level placementSlotAttribution ACTIVATE event and fans out a per-offer offerAttribution ACTIVATE event for every offer resolved by the slot’s content strategy. The slot-level event id and the resolved offerIds are returned so the partner can render the batch immediately without an extra getBatchesByPlacement round-trip.

Required scopes: attributions:write

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

organizationIdstringRequired
Your issuer organization ID, provided by Kard
userIdstringRequired
The ID of the user as defined on the issuers system
placementIdstringRequired

Unique identifier of the placement (UUID v7)

slotIdstringRequired
Stable identifier for the slot within the placement

Response

This endpoint returns an object.
dataobject

Errors

400
Invalid Request
401
Unauthorized Error
500
Internal Server Error