Dear Diogo,
thanks a lot for claryfing 
I thought I was making some mistake
in the calls to the APIs.
Considering my use case: in our group we use swan to analyse data
collected from some detectors (data is already stored on a EOS project). For each run we create a notebook from a template notebook to run the analysis.
My first idea was to automatically create a notebook for each run so that we can easily access it in SWAN and run analysis.
After finding out jupyter hub has APIs to spawn processes and running notebooks I also considered to test them to see if I could already run notebooks so that they could be ready to be presented to the end user.
After your reply I get to understand the access to APIs must be really motivated by a strong need so since I don’t have one I would try to run a jupyter hub instance myself on openshift (it’s a little bit of a pity though since SWAN is working really well), skip trying implementing the feature or work around the oauth limitation by changing the authorization workflow and let the user login via a browser on my daq software (if this is compatible with your terms of usage).
Cheers,
Gianluca