All communication Communication with the GraphQL Cloud API server has to be authorized via an access TOKEN. The valid TOKEN has to be inserted into the header of each API call. A TOKEN can be created by a user with full account access in the cloud IP cam platform.
Using user TOKEN covers most of your integration use cases.
User TOKEN is one of two authorization options. The second option is use It is recommended in most of integration use cases.
OAuth 2.0 is a second option how to create access token. It is much more complex.
Authorization header
Code Block |
---|
“AuthorizationAuthorization : Bearer TOKEN”$TOKEN |
Where TOKEN $TOKEN
is created token in the preview step.
...
Code Block |
---|
curl -X POST -H 'Authorization: Bearer TOKEN$TOKEN' -H "Content-Type: application/json" --data-binary '{"query":"{cameraList{name}}"}' https://system2.netrex.cz/api/graphql.php |
Response:
Code Block | ||
---|---|---|
| ||
{"data":{"cameraList":[{"name":"myCamera"}]} |
...
For testing purposes you can user use our embedded API explorer, Postman or your own GraphQL client application.
...
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Be careful on TOKEN. Be sure what you do. You can update/delete important data on your account. |