I would really recommend waiting for Cyclos 4.6, which will have a swagger REST implementation. If you really can't wait use something like the following code (but please understand that we can't give any additional support, because in a few months it will be much easier):
Step 1: request captcha
Url (post):
https://example.com/network/web-rpc/captchaService
Header:
None
Body:
{
"operation":"generate",
"params":[]
}
Next you get an id display the captcha that is generate in your page, e.g.:
https://example.com/network/content/cap ... 2071682440
Step 2: register user
Url (post):
https://example.com/network/web-rpc/userService
Header:
None
Body:
{
"operation":"publicRegister",
"params":[
{
"name":"Test User 09-21",
"email":"
test09.21@mail.com",
"username":"testUser0921",
"group":{
"internalName":"name of group here"
},
"agreement":true,
"password":"12345678",
"confirmPassword":"12345678",
"mobilePhones":[
{
"name":"Mobile phone",
"hidden":true,
"rawNumber":"xxx"
}
],
"captchaId":"-2912315512071883144",
"captchaText":"bbpgy8",
"addresses":[
{
"name":"Address 1",
"addressLine1":"Address",
"zip":"3511AR",
"city":"Nederland"
}
],
"customValues":[
{
"field":{
"internalName":"gender"
},
"enumeratedValues":[
{
"internalName":"gender.man"
}
]
}
]
}
]
}
Succesfull response:
{
"result": {
"class": "org.cyclos.model.users.users.UserRegistrationResult",
"id": "-2912315512071768456",
"status": "EMAIL_VALIDATION",
"username": "testxUser0921"
}
}