Playground V2 doesn't work


Hello, i want to migrate my app from API v1 to v2. To test new API i went to Playground, but when i use some Account API i get errors. 1)Accounts list. I’ve put access token and executed query(–AagrQLGoF5ZxB1OFN7mA) It generates next curl: curl -X GET “–AagrQLGoF5ZxB1OFN7mA” -H “accept: application/json” On response i get 401. Invalid auth token. 2)Accounts create sub. I’ve executed query–AagrQLGoF5ZxB1OFN7mA Curl: curl -X POST “–AagrQLGoF5ZxB1OFN7mA” -H “accept: application/json” -H “Content-Type: application/json” -d “{ “first_name”: “string”, “last_name”: “string”, “email”: “string”, “password”: “string”, “options”: { “share_rc”: false, “room_connectors”: “string”, “share_mc”: false, “meeting_connectors”: “string”, “pay_mode”: “master” }}” But now, instead of POST it sends OPTION request and gets 403 Forbidden.

Is it Playground broken or my mistake?


Hi Sergey, 

Playground is still working, did you authorize the token before running the first API call? For the second one, please take a look at your payload, make sure to replace “string” with actual data. 



Hi. Of course i did. Token is authorized. Payload was attached as sample, it doesn’t matter what JSON it posts because it should have posted POST request but i had OPTION.

By the way i get next error in console

GET\_size=30&page\_number=1&access\_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJuaGs1SDZObVRSaS12TnR2bDRRcjF3IiwiaWF0IjoxNTM5MDY3NzQ3LCJleHAiOjE1MzkwODU3NDd9.WHtJViJBZAk4mliq6fxnK1kUYffq9s2lZd9tQtwXGhU 401 (Unauthorized)


Failed to load\_size=30&page\_number=1&access\_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJuaGs1SDZObVRSaS12TnR2bDRRcjF3IiwiaWF0IjoxNTM5MDY3NzQ3LCJleHAiOjE1MzkwODU3NDd9.WHtJViJBZAk4mliq6fxnK1kUYffq9s2lZd9tQtwXGhU: 
No 'Access-Control-Allow-Origin' header is present on the requested resource. 
Origin '' is therefore not allowed access. The response had HTTP status code 401. 
If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

That’s why it does OPTION first.


Hi Sergey, 

The reason why the you’re getting a “invalid access token” is because your account is not the master account. Only master accounts with sub accounts are allowed to see the subaccounts. 


Sadly, but no. My current user has Admin role and he is sub account of our master account. I took our master account credentials, logged in and tested with it. API returns same errors. Still invalid auth token, still CORS issues in console.

I’ve written to support and they should have added new ticket for this behavior.

If you have some different workaround, please tell me.

Thank you!


Hi Together Networks, 

Can you send us the account ID associated to the master account so that we can take a look at



I’ve sent email to The only thing, im not sure that i put correct ID. If not, please show me where i should take it.


Hi Sergey, 

We got your email and will have our API Engineers take a look at your account to see whats going on with the error. 


Hi Sergey, 

Following up on the v2/accounts API you’re trying to access. To check to see if you have a master account you can check portal page and see if you have this tab for sub accounts. If you don’t see if then you will need to make a request with our sales/support team to have a master account.