Reverse engineered TikTok (previously Musically) Private API written in PHP, this project is no longer maintained.

This API was reverse engineered using MITM (Man in the middle) Attacks to intercept encrypted API requests between the TikTok iOS Application and the TikTok API Server.

The tools used to capture the endpoints were Charles Proxy, SSL Proxying, and SSL Kill Switch for SSL Certificate Pinning.

Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. Charles allows you to set up a local VPN connection that monitors any devices traffic including sockets.

Transport Layer Security (TLS) which has replaced Secure Socket Layer (SSL) creates an E2EE (end-to-end encrypted) connection between a client and a server (eg your phone and a website). TikTok's API used TLS encryption, so any data send between the TikTok App and the TikTok servers through Charles Proxy is completely encrypted and cannot be read. However, SSL Proxying can be used to surcumvent this protection.

By installing a custom SSL Certificate on your device, you hold the decryption keys to the encrypted data and can view all requests in plain text.

The strongest protection developers take to secure their APIs from being intercepted is SSL Certificate Pinning. This article explains Certificate Pinning in greater detail however it is a checker built into the application. It ensures that the SSL/TLS Certificate is one approved by a certificate authority (CA). This causes all requests where Charles Proxy is attempting to intercept requests using SSL Proxying as the device trusted SSL/TLS Certificate is invalid.

This can be circumvented on a Jailbroken iOS Device by installing SSL Kill Switch. This software provides the ability to patch low-level functions responsible for handling SSL/TLS connections in order to override and disable the system's default certificate validation, as well as any kind of custom certificate validation (such as certificate pinning).

Security through ambiguity does not work. However, TikTok now send a unique ID header with every single request that comprised of many factors. This header is verified by the server and if the unique ID is incorrect, the request is rejected. The unique ID is assumed to contain details such as Timestamp, Device ID and API endpoints. This unique ID algorithm can be reverse engineered. The difficulty is reverse engineering the whole iOS application. There have been many projects that have succesfully reverse engineered these unique IDs.

See examples in /examples Most API endpoints are depreciated at this point, proof of concept testing may occur.