Bypass Solution
The PerimeterX mobile bypass endpoint. You POST the app and device details, and Takion returns the PerimeterX mobile headers (_px3, x-px-authorization or _px2) the protected app expects.
How the Solution Works
To bypass PerimeterX mobile protection:
Provide our API with the device and app details.
Parse the returned headers and use them for requests to the protected application.
Required Details
Since PerimeterX is mobile-based, our API requires a JSON input with the package_name of the Android app (for example com.enflick.android.TextNow for TextNow). Additional optional device information can be supplied for more accurate header generation.
Based on this information, the API returns all necessary headers for the specified app.
Endpoint
The endpoint lives on the px-mobile subdomain:
https://px-mobile.takionapi.tech/generateProduces the X-PX-* mobile headers (session id, authorization, vid, uuid, device fingerprint, …) for the given app package. Send them on your app-API request alongside the matching User-Agent.
The Android/iOS app package the PX headers are for.
com.walmart.androidProxy in ip:port or ip:port:user:pass format.
1.2.3.4:8000:user:passDevice manufacturer to emulate (optional).
SamsungAndroid version to emulate (optional).
14Continent hint for the emulated device (optional).
NADevice language (optional).
enThe PX mobile headers. On a bad request the API returns an error field instead — check for error before reading the headers.
Authentication or quota failure — HTTP 401 with an error message.
Unexpected server error (HTTP 500).
POST /generate HTTP/1.1
Host: px-mobile.takionapi.tech
Content-Type: application/json
Accept: */*
Content-Length: 189
{
"package_name": "com.walmart.android",
"proxy": "1.2.3.4:8000:user:pass",
"manufacturer": "Samsung",
"android_version": "14",
"continent": "NA",
"language": "en",
"ANY_ADDITIONAL_PROPERTY": "anything"
}{
"error": "In order to extend your trial for perimeter x mobile, please contact the discord support"
}Sends an HTTP request from Takion bound to the session_id from /generate, with a realistic mobile TLS fingerprint.
(Important) This endpoint is optional. If your own client already reproduces the mobile TLS + header fingerprint, just attach the generated X-PX-* headers to your own request and skip /mobile/tls. Use it only when you can't match the fingerprint yourself.
1.2.3.4:8000:user:passThe x-px-session-id from /generate.
GETPossible values: https://www.walmart.com/orchestra/…The upstream response (or an error field).
Authentication or quota failure — HTTP 401 with an error message.
Unexpected server error (HTTP 500).
POST /mobile/tls HTTP/1.1
Host: px-mobile.takionapi.tech
Content-Type: application/json
Accept: */*
Content-Length: 257
{
"proxy": "1.2.3.4:8000:user:pass",
"session_id": "text",
"method": "GET",
"url": "https://www.walmart.com/orchestra/…",
"headers": {
"ANY_ADDITIONAL_PROPERTY": "text"
},
"json": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"data": "text",
"ANY_ADDITIONAL_PROPERTY": "anything"
}{
"error": "No proxy provided"
}Last updated