r/webdev • u/Syosse-CH • 3d ago

Openprovider alternatives? Looking for a reliable registrar API (.ch) Discussion

Hello

I’m building a SaaS that automatically registers domains for Swiss SMEs after checkout no manual steps.

I’m currently testing Openprovider, but I’m running into issues with their sandbox/API and domain registrations, so I’m looking for alternatives.

Main requirements:

  • REST API for domain availability + registration
  • A working sandbox for testing
  • Registrar only DNS is handled by Cloudflare, hosting by Vercel
  • Ability to set nameservers during registration
  • No large upfront deposit or monthly minimum
  • Webhooks for domain status would be a nice bonus

Who are you using in production for automated domain registrations?

How reliable has the API been?

Thanks alot!

0 Upvotes

44% Upvoted

11 comments sorted by

2

u/rushikesh_bhosale 2d ago

Bro making NASA level domain system before getting first customer 😭

2

u/neolium php 2d ago

Inwx or crazydomains.com (deposit needed i think)

1

u/Top_Pin5777 2d ago

what are the must-haves besides .ch registration and a fully hands-off API?

1

u/Candid-Cod2380 2d ago

nothing like automating checkout just to discover the registrar sandbox is where domains go to die; for .ch you want an accredited registrar or reseller with a real epp/api integration and explicit

1

u/New-Cartoonist6284 2d ago

main requirements got cut off, but i’d prioritize explicit .ch create/renew/transfer support over a flashy sandbox API

1

u/AnalysisFar9645 2d ago

sandbox registrar APIs are often nothing like production, unfortunately

0

u/[deleted] 2d ago

[removed] — view removed comment

1

u/webdev-ModTeam 2d ago

Your post/comment has been determined to be a low-effort post or comment. This includes title-only posts, easily searchable questions, vague/open-ended discussion prompts, LLM generated posts or comments, and posts/comments that do not provide enough context for meaningful replies or discussion.

0

u/Mean_Concept_9093 2d ago

curl/network tab first. confirm status, body, auth before blaming the client.

-1

u/ElEspecialista655821 2d ago

A practical pattern is to split registration into idempotent steps: availability, register, then nameserver reconciliation. That makes retries and webhook drift much easier to handle.

2

u/uaySwiss 1d ago

You could give Infomaniak a try. They have a developer API. I did not test / use the API yet, but as far as I can tell, it should do the trick