UBC TEC Akamai Proxy API

Base URL https://ak.ubc-tec.de

Authentication

Use the API key issued by your UBC TEC operator. Send one of the following headers with each POST.

x-api-key: YOUR_API_KEY
x-key: YOUR_API_KEY
Authorization: Bearer YOUR_API_KEY

For an existing client that supports a custom base URL, set it to the URL above and replace the configured key with your UBC TEC key. Send request bodies as application/json.

Endpoints

POST routeResult
/v3, /v2/sensorSensor payload and session context
/sbsdSBSD body and session context
/pixelPixel form payload

Sensor

Send userAgent, pageUrl, abck (the _abck cookie) and bmsz (the bm_sz cookie). Include the script text on the initial call or the returned context on subsequent calls. Optional fields are ip, acceptLanguage, scriptUrl and the zero-based integer iteration (default 0). The response contains payload and context.

SBSD

Send uuid from the script, userAgent, pageUrl and o (the bm_so cookie). Supply script or context as for the sensor call. Optional fields are ip, acceptLanguage, scriptUrl and the zero-based integer index (default 0). The response contains body, its alias payload, and context.

Pixel

Send userAgent, htmlVar (the numeric bazadebezolkohpepadr value) and scriptVar (the value from the pixel script as a string). Optional fields are ip and acceptLanguage. The response contains payload.

Example request

Save the input for the chosen endpoint to a JSON file, then submit it with your key.

curl https://ak.ubc-tec.de/v3 \
  -H "x-api-key: $API_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary @sensor.json

Sessions and limits

For sensor calls, keep the same bm_sz value for a session. For sensor and SBSD calls, keep the opaque context from the last response in that session. Allow at least 135 seconds for a solve request. The body limit is 8 MiB.

Soldout controls browser compatibility. Check its reference for the currently supported desktop Chrome user-agent strings. Soldout API reference

Errors

StatusMeaning
400Soldout rejected the JSON, a field value or the user agent.
401 / 403A key is missing or invalid.
402The upstream account has insufficient balance.
404 / 405Unknown route or unsupported HTTP method.
413The request body exceeds the limit.
502 / 504The upstream failed or timed out.

GET /healthz is public and reports whether the proxy process is up.