Repository navigation
v2.2.28
·
2 commits
to master
since this release
Immutable
release. Only release title and notes can be modified.
Breaking Changes
- Removed the
LeadFyndrclient and all associated endpoints, requests, and response classes. TheClientandClientImplno longer expose theleadFyndr()method. - Deleted all files previously located under
src/Generated/V2/Clients/LeadFyndr/andsrc/Generated/V2/Schemas/Leadfyndr/.
New Features
- Added
checkAuthinfo2(CheckAuthinfo2Request $request): CheckAuthinfo2OKResponseto theDomainClientinterface andDomainClientImpl. - Introduced a complete
CheckAuthinfo2namespace undersrc/Generated/V2/Clients/Domain/containing updated request, response, and body classes. - The operation now sends a
POSTrequest to/v2/authinfo2/check-domainwith a domain name in the request body.
High-Level Summary of New Features
This release introduces a streamlined domain eligibility check for AuthInfo2 transfers, completely replacing the legacy LeadFyndr access flow. The new checkAuthinfo2 method allows developers to quickly verify if a domain qualifies for an AuthInfo2 request. Upon submission, the API returns a structured response indicating whether the domain is eligible (eligible: true/false). If ineligible, the response provides specific diagnostic reasons via a reasons object, detailing if the domain is already managed by Mittwald, not registered at DENIC, or if an AuthInfo2 was already triggered within the last 30 days. This simplifies domain transfer validation and provides clearer error handling for migration workflows.
Internal Refactoring
- Repurposed and renamed several response and schema classes from the deprecated LeadFyndr module to support the new
CheckAuthinfo2domain functionality. - Updated request/response validation schemas, HTTP method mappings, and URL builders to align with the revised API specification.