Membership is FREE – with unlimited access to all features, tools, and discussions. Premium accounts get benefits like banner ads and newsletter exposure. ✅ Signature links are now free for all. Share your own thoughts and experience, accounts may be terminated for violations.
  • Welcome to AcornDomains.co.uk, a friendly community for UK domain investors, developers and anyone interested in domain names.

    Whether you're looking to buy or sell domains, learn more about the UK domain market, get feedback on your names, or simply chat with other domainers, you're in the right place. AcornDomains has been bringing together people from across the UK domain industry for many years, from complete beginners to experienced investors.

    Have a look around, join the discussions and, if you haven't already, create a free account and introduce yourself.

Nominet "Nominet XML" not EPP

Status
Not open for further replies.
I didn't know 123 had an API, when did this happen?

I saw the original post and the reply, from my (so far limited) exposure, I would suggest that it is EPP, however the data model used by Nominet seems to be different in places from other registrars. EPP is only the protocol, not the data definition.

From memory, Centralnic have some sample EPP libraries, if you're building a system you might be better off using a seperate "plug in" for each registry and mapping your customer data out to each plug in and leaving the plug in code to handle the customer -> registry mapping
 
I read it and I think the guy was going a bit OTT. It's close enough, it was never going to be exact because the extensions built into the EPP scheme weren't flexible enough to accomodate the way nominet handles things.

Okay its not going to be exact plug and play between differerent EPP servers but it's not going to need huge modifications to work on others.
 
Status
Not open for further replies.
Top Bottom