Skip to main content
POST
/
networks
/
encode
Encode IDs
curl --request POST \
  --url https://api.eflow.team/v1/networks/encode \
  --header 'Content-Type: application/json' \
  --header 'X-Eflow-Api-Key: <api-key>' \
  --data '
{
  "type": "tracking_link_affiliate",
  "ids": [
    1,
    2,
    3
  ]
}
'
{
  "values": [
    {
      "decoded": 123,
      "encoded": "<string>"
    }
  ]
}
Encode numeric Everflow IDs into their encoded string representation. Certain resource IDs are encoded in Everflow URLs. For example, a tracking link like https://YOUR-DOMAIN.com/28KL6/2CTPL/ encodes partner ID 1 as 28KL6 and offer ID 1 as 2CTPL. It is normally not necessary to encode IDs yourself — they are encoded automatically when generating tracking links, signup URLs, etc. This endpoint is available for cases where you need encoded values for internal processes. The type field determines the encoding context:
TypeDescription
tracking_link_affiliatePartner ID in a tracking link URL
tracking_link_offerOffer ID in a tracking link URL
smart_link_affiliatePartner ID in a smart link URL
smart_link_smart_linkSmart link ID in a smart link URL
signup_affiliate_employeeEmployee (account manager) ID in a partner signup URL
signup_advertiser_employeeEmployee (account manager) ID in an advertiser signup URL
signup_affiliate_affiliatePartner (referrer) ID in a partner signup URL

Authorizations

​
X-Eflow-Api-Key
string
header
required

The Everflow API key generated from the Control Center > Security.

Body

application/json
​
type
enum<string>
required

The encoding context. Determines how the IDs are encoded based on their intended use.

Available options:
tracking_link_affiliate,
tracking_link_offer,
smart_link_affiliate,
smart_link_smart_link,
signup_affiliate_employee,
signup_advertiser_employee,
signup_affiliate_affiliate
​
ids
integer[]
required

The numeric IDs to encode.

Response

200 - application/json
​
values
object[]