Cloudron Forum

@girish thanks for pointing out to code. As always: In vino veritas - and in Source-Code

@nebulon, @BrutalBirdie Thx to both of you, the call is now working. curl -kX POST -H "Content-Type: application/json" https://my.smthg.com/api/v1/apps/install?access_token=857f7d7eb583cfb951e5a50c75a762b94304d4ba50d4a0c94950643eaab7959a -d '{"appStoreId": "io.n8n.cloudronapp@2.37.0","subdomain": "workflow","domain": "somethg.com","accessRestriction": {"users":[],"groups":[]}}' { "id": "c6c79d78-7c7c-414b-acf7-8b5cc39370ed", "taskId": "269" } It needed obviously the header, but also I thought reading the API specs that accessRestriction could be null. It is not the case, so I used @BrutalBirdie assignment (empty users and groups) and the call succeeded. Once again thank you very much.

Ignore me. This was an issue with PowerShell apparently. If run from linux it works fine. Thanks again

@girish well, that solved the problem i was facing, though i do not understand why it does, but anyway, thanks a lot that helped me Solved!! Solution = <Just sign in to the app store in your Cloudron Server as Mr. @girish said> Once more, thank you very much for the support .

Glad you managed to resolve this. Some ago we changed the REST api there which probably caused this issue when using an outdated cloudron cli tool.

@girish said in Some problems with API - PUT user in groups: {"groupIds":["gid-3e96c503-d30f-4db8-aa37-ecaf98fa33fa"]} Thank you, works fine. It was a spelling-error in the "content-type" .

@girish sorry, a school boy mistake, the Content-Type header did the trick, but I made a typo in the backupId, that's why I got the error.

@robi @timconsidine good catch, I don't think it is. Will fix. Opened https://git.cloudron.io/cloudron/box/-/issues/832 to track internally

@plusone-nick I didn't check the part of our code that manage user creation for ages, but 99% sure, that you don't need to provide a password, or not even a username just an email. Then you create the invite link with a second request if you want to have the onboarding process managed by cloudron. Personal note: Remember that as the server owner you are responsible for the content hosted in it, for this is normally a good idea to have some manual approval before creating an account from a form; or you have to provide a good moderation.

That was the piece of information I was missing. Now it works perfect. How much time am I going to save updating WordPress Developer applications... Thank you @girish

@girish gotcha, thanks!

@girish thank you, the output is different now, so I hope that will work. I took that API call from my forum request earlier, but I guess there was a misunderstanding the API call example was for the specific domain, not to update them all. Thanks for your assistance!

The API docs are now also updated for the invite routes.

@girish ah alright, that sent me down the right path. needed to switch from encoded body to raw JSON and that cleared it up. thank you!

@atrilahiji hello, sorry for being late, got sick. like that: "dockerImage": "cloudron/org.wordpress.unmanaged.cloudronapp:20210208-171207-630daccf7",

I have added it to https://docs.cloudron.io/profile/#api-tokens for a start. The API page is a bit outdated and will take more time to freshen up.

@robi I've put it in the corresponding thread here

@nebulon thank you! worked perfectly fine and is very helpful

To add to what @nebulon said, https://cloudron.io/documentation/api/#tag/Services/paths/~1services~1{service}~1logs/get is for the addon logs and https://cloudron.io/documentation/api/#tag/Tasks/paths/~1tasks~1{taskId}~1logs/get for task logs.