If you specifically want to keep the invalid `httpa://` protocol (perhaps for testing or a custom use case), you need to understand that **standard browsers and apps will reject it** since it’s not a recognized scheme like `http://` or `https://`.  

---

### How to Use `httpa://` (Non-Standard Protocol)
#### Option 1: **For Development/Testing (Custom Protocol)**
If this is for a custom app or local environment (e.g., a mock API), you can:
1. **Register `httpa://` as a custom protocol** in your app (e.g., Electron, mobile app, or browser extension).  
   - Example (Electron.js):
     ```javascript
     app.setAsDefaultProtocolClient('httpa');
     ```
   - For **Android/iOS apps**, define it in the manifest/plist file.

2. **Use a URL handler** to intercept `httpa://` links and redirect/log them.

#### Option 2: **Replace with Standard Protocol**
If this was a typo, just correct it to `http://` or `https://` (recommended for production):
```text
https://tattoo.api/api-create?utm_source=APKPUREAds&...

Option 3: Use a Placeholder (No Functional URL)

If you need the literal text httpa:// for documentation/mockups (non-clickable):

httpa://tattoo.api/api-create?utm_...

Why httpa:// Won’t Work by Default

• Browsers (Chrome, Firefox, etc.) and libraries (cURL, requests in Python) only support registered protocols (e.g., http, ftp, data).
• Attempting to open httpa://... will typically result in:
  • Browser: "Invalid URL" or search prompt.
  • Apps: Unsupported URL scheme error.

AQIL FAROOQ MUHAMMAD