API referenceEndpoints

Links and posts

Telling us which post a link was used in.

Attaching a post

Enrolment hands a creator a link. Attaching tells us which post they used it in, and it is a separate call because it happens at a different moment and, on a marketplace, by a different actor: the creator submits their clip hours after being handed the link.

cURL
curl -X PATCH https://track.acrune.com/v1/links/kp7r2wqm \
  -H "Authorization: Bearer $ACRUNE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "postUrl": "https://tiktok.com/@apexlaps/video/7412…" }'

This is the step that is easy to skip and expensive to skip. A link with no post attached still counts clicks; it simply cannot be ranked against the others, and the ranking is the product.

In bulk

Reconciling a day of submissions is one call, not one call per clip.

curl -X PATCH https://track.acrune.com/v1/links \
  -H "Authorization: Bearer $ACRUNE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "posts": [
         { "linkId": "kp7r2wqm", "postUrl": "https://tiktok.com/@apexlaps/video/7412…" },
         { "linkId": "b3n8xqtd", "postUrl": "https://instagram.com/reel/DA1…" }
       ]
     }'

Up to 200. Link ids that are not on your account come back in missing rather than failing the batch, and a link id belonging to another account is reported as missing, not attached, because a partner must not be able to write to one by naming it.

What a click does

A link is served at /r/:linkId. Following it records the click and redirects to the campaign's destination with an opaque click id set as the campaign's clickParam.

Nothing downstream reads that click id today. It is minted anyway, because a click that was not identified at the time cannot be identified afterwards: if a conversion feed ever arrives, the identifier is already in the history rather than starting from the day it ships.