> ## Documentation Index
> Fetch the complete documentation index at: https://developers.everflow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Encode IDs

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:

| Type                         | Description                                               |
| ---------------------------- | --------------------------------------------------------- |
| `tracking_link_affiliate`    | Partner ID in a tracking link URL                         |
| `tracking_link_offer`        | Offer ID in a tracking link URL                           |
| `smart_link_affiliate`       | Partner ID in a smart link URL                            |
| `smart_link_smart_link`      | Smart link ID in a smart link URL                         |
| `signup_affiliate_employee`  | Employee (account manager) ID in a partner signup URL     |
| `signup_advertiser_employee` | Employee (account manager) ID in an advertiser signup URL |
| `signup_affiliate_affiliate` | Partner (referrer) ID in a partner signup URL             |


## OpenAPI

````yaml openapi/utilities.yaml post /networks/encode
openapi: 3.0.3
info:
  title: Everflow Network API - Utilities
  description: Utility endpoints for encoding and decoding IDs.
  version: 1.0.0
servers:
  - url: https://api.eflow.team/v1
security: []
tags:
  - name: Encoding
paths:
  /networks/encode:
    post:
      tags:
        - Encoding
      summary: Encode IDs
      requestBody:
        required: true
        content:
          application/json:
            example:
              type: tracking_link_affiliate
              ids:
                - 1
                - 2
                - 3
            schema:
              type: object
              required:
                - type
                - ids
              properties:
                type:
                  type: string
                  enum:
                    - tracking_link_affiliate
                    - tracking_link_offer
                    - smart_link_affiliate
                    - smart_link_smart_link
                    - signup_affiliate_employee
                    - signup_advertiser_employee
                    - signup_affiliate_affiliate
                  description: >
                    The encoding context. Determines how the IDs are encoded
                    based on their intended use.
                ids:
                  type: array
                  items:
                    type: integer
                  description: The numeric IDs to encode.
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  values:
                    type: array
                    items:
                      type: object
                      properties:
                        decoded:
                          type: integer
                          description: The original numeric ID.
                        encoded:
                          type: string
                          description: The encoded string representation.
      security:
        - API Key: []
components:
  securitySchemes:
    API Key:
      description: The Everflow API key generated from the Control Center > Security.
      in: header
      name: X-Eflow-Api-Key
      type: apiKey

````