2025-09-11

ℹ️

API /v3/request brings enhanced traceability and security for server-to-server partners while leaving existing widget-based integrations untouched. The centerpiece is the new userIp field, enabling precise client identification and better abuse mitigation.

Key changes

1. New endpoint

• POST /v3/request is now available.

❗️

Deprecation notice
The legacy endpoint POST /v2/request remains operational only for backward compatibility. It will be shut down later - migrate to /v3/request ASAP to avoid service disruption.

2. Required field: userIp

• Must be included in every /v3/request body.
• Accept the first public IP address if a chain is provided (e.g., from X-Forwarded-For).
• Supports both IPv4 and IPv6.

3. Validation rules

• IPv4: validate using an ip2long() equivalent (PHP link provided for reference).
• IPv6: validate with the standard IPv6 filter.

Action checklist

✅ Switch server-to-server calls to POST /v3/request.

✅ Always supply a valid public userIp.

✅ Handle the 400 INVALID_USER_IP error in your integration.