H&M Registration Service
Special service — non-standard schema
Unlike WAF/captcha endpoints, hnm_register takes email + password + proxyurl (NOT url + proxy_config). Use it only for H&M account provisioning.
hnm_register automates H&M new-account creation end-to-end: it solves the registration form, satisfies H&M's password and email rules, and returns the resulting account state plus session cookies.
Service Schema
| Field | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Email to register on H&M |
password | string | Yes | Account password (must satisfy H&M rules) |
proxyurl | string | Yes | Outbound proxy: socks5://, http://, https://, or host:port:user:pass |
Service ID: hnm_register · Status: Stable
Password Rules
H&M enforces a minimum 8-character password with at least one uppercase letter, one lowercase letter, one number, and one symbol. The service does not generate passwords for you — pre-validate before submitting.
Integration Example
hnm-register.js
// Submit H&M registration task to MeshPrivacy
// NOTE: This service uses different fields - no url, no proxy_config
const response = await fetch('https://api.meshprivacy.com/v1/tasks/submit', {
method: 'POST',
headers: { 'Content-Type': 'application/json', 'X-API-Key': API_KEY },
body: JSON.stringify({
service: 'hnm_register',
email: 'newuser+abc@example.com', // required
password: 'StrongPass!2026', // required - must satisfy H&M rules
proxyurl: 'socks5://user:pass@ip:port' // required - NOT proxy_config
// Accepted formats: socks5://, http://, https://, or host:port:user:pass
})
});
const { task_id } = await response.json();
const result = await fetch(`https://api.meshprivacy.com/v1/tasks/result/${task_id}`, {
headers: { 'X-API-Key': API_KEY }
});
const { account_status, cookies } = await result.json();
// Returns registered account confirmation + session cookiesFAQ
This service is hard-wired to the H&M registration endpoint, so the URL is implicit. The schema only takes the inputs that vary between calls.