Creates a new endpoint for the specified ActiveGate plugin.
The request consumes and produces an application/json
payload.
POST | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/plugins/{id}/endpoints |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/plugins/{id}/endpoints |
To execute this request, you need an access token with WriteConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
The ID of the plugin where you want to create an endpoint.
The JSON body of the request. Contains parameters of the new plugin endpoint.
RemotePluginEndpoint
objectConfiguration of a plugin endpoint.
The short representation of a Dynatrace entity.
The endpoint is enabled (true
) or disabled (false
).
The ID of the endpoint.
The name of the endpoint, displayed in Dynatrace.
The ID of the plugin to which the endpoint belongs.
The list of endpoint parameters.
Each parameter is a property-value pair.
EntityShortRepresentation
objectThe short representation of a Dynatrace entity.
A short description of the Dynatrace entity.
The ID of the Dynatrace entity.
The name of the Dynatrace entity.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"activeGatePluginModule": {"id": "-8844900174269363000"},"enabled": true,"id": "-2183662974968812535","name": "Demo endpoint","pluginId": "custom.remote.python.demo","properties": {"dropdownProperty": "two","password": "","serverIp": "127.0.0.1","username": "dynatrace"}}
Success. The plugin endpoint has been created. Response contains the ID of the new endpoint.
EntityShortRepresentation
objectThe short representation of a Dynatrace entity.
A short description of the Dynatrace entity.
The ID of the Dynatrace entity.
The name of the Dynatrace entity.
{"description": "Dynatrace entity for the REST API example","id": "6a98d7bc-abb9-44f8-ae6a-73e68e71812a","name": "Dynatrace entity"}
We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.
The request consumes an application/json
payload.
POST | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/plugins/{id}/endpoints/validator |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/plugins/{id}/endpoints/validator |
To execute this request, you need an access token with WriteConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
Validated. The submitted configuration is valid. Response doesn't have a body.
In this example, the request creates a new endpoint for the SAP plugin which has the ID of custom.remote.python.sap.
The API token is passed in the Authorization header.
curl -X POST \https://mySampleEnv.live.dynatrace.com/api/config/v1/plugins/custom.remote.python.sap/endpoints \-H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890' \-H 'Content-Type: application/json' \-d '{"pluginId": "custom.remote.python.sap","name": "RESTtest","enabled": false,"properties": {"clientno": "001","serverIp": "127.0.0.1","password": "","instance": "00","username": "DT"},"activeGatePluginModule": {"id": "1768386982494938781"}}'
https://mySampleEnv.live.dynatrace.com/api/config/v1/plugins/custom.remote.python.sap/endpoints
{"pluginId": "custom.remote.python.sap","name": "RESTtest","enabled": false,"properties": {"clientno": "001","serverIp": "192.168.0.1","password": "","instance": "00","username": "DT"},"activeGatePluginModule": {"id": "1768386982494938781"}}
{"id": "8757307336635955682"}
201
The new endpoint looks like this in the UI: