From 2f864f42f5c8079dacbe57ab0150449184eae59d Mon Sep 17 00:00:00 2001
From: Erik Hollensbe All API requests must have an API token header specified in the eg. All API requests must have an API token header specified in the eg. Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/networkAuthorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/networkRate Limiting
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
All API requests must have an API token header specified in the Authorization: Bearer xxxxx format. You can generate your API key by logging into ZeroTier Central and creating a token on the Account page.
eg. curl -X GET -H \"Authorization: bearer xxxxx\" https://my.zerotier.com/api/v1/network
The ZeroTier Central API implements rate limiting. Paid users are limited to 100 requests per second. Free users are limited to 20 requests per second.
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/centralv1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
This API controls the ZeroTier service that runs in the background on your computer. This is how zerotier-cli, and the macOS and Windows apps control the service.
API requests must be authenticated via an authentication token. ZeroTier One saves this token in the authtoken.secret file in its working directory. This token may be supplied via the X-ZT1-Auth HTTP request header.
For example: curl -H \"X-ZT1-Auth: $TOKEN\" http://localhost:9993/status
The token can be found in:
You can get the OpenAPI spec here as well: https://docs.zerotier.com/openapi/servicev1.json