---
title: "Create Secret"
method: POST
path: "/connect/settings/{service}"
tags: ["Connect Settings"]
---

# Create Secret

`POST /connect/settings/{service}`

Create a new secret for a given service.

The `Example model` contains models for all services that can be created.
When calling this endpoint for a specific service, only the credentials
for that service should be provided in the payload.

The payload should be structured with the credentials inside a 'credentials' key.
For example, for an S3 integration:

{
    "credentials": {
        "alias": "my-s3-integration",
        "target": "my-target",
        "name": "my-bucket-name"
    }
}

Not all fields from all_input_models need to be sent in the payload,
only those relevant to the specific service being created.

Response will be the instance credentials that was created.

## Parameters

- `#/paths/~1connect~1settings~1%7Bservice%7D/get/parameters/0` — unresolved $ref
- `#/paths/~1connect~1settings~1apikeys/get/parameters/1` — unresolved $ref

## Request body

- object
  - `ansible` object
    - `alias` string — Alias for Ansible integration instance.
    - `logs` string — Optional S3 bucket for execution logs. If not given, the logs will be uploaded to the same S3 bucket with the playbooks.
    - `playbooks` string — S3 bucket with playbooks directory.
    - `s3_access_role` string — Fylamynt IAM role for bucket policy in target account.
    - `ssh_private_key` string — Ansible Controller Private ssh key.
  - `azure_openai` object
    - `alias` string — Alias for OpenAI integration instance.
    - `api_key` string — API Key for your API.
    - `azure_endpoint` string — Azure Endpoint for your OpenAI service API.
    - `model` string — The deployment Name of the model deployed in user's Azure OpenAI Service.
  - `bitbucket` object
    - `access_token` string — Bitbucket Cloud Access Token for authentication using Access Token.
    - `alias` string — Alias for Bitbucket repo instance.
    - `url` string — Bitbucket repository URL, ex: Bitbucket personal repo -> `https://bitbucket.org/<username>/<repo-name>` for Bitbucket workspace repo -> `https://bitbucket.org/<workspace-name>/<repo-name>`.
  - `cloudformation` object
    - `alias` string — Alias for Cloudformation template.
    - `filePath` string — Absolute filepath of template file.
    - `ref` string — Github commit ref, (ie: main/master).
    - `repoId` string — The GitHub repo as a source for the Cloudformation template.
  - `datadog` object
    - `alias` string — Alias for Datadog integration instance.
    - `api_key` string — Datadog API key for your org.
    - `app_key` string — Datadog application key for your org.
  - `eks` object
    - `alias` string — Alias for EKS Permissions resource instance.
    - `role_arn` string — IAM Role ARN to be used for the EKS cluster.
    - `target` string — AWS Target Account for the EKS Cluster Role.
  - `elasticsearch` object
    - `alias` string — Alias for Datadog integration instance.
    - `api_key_id` string — Elasticsearch API key id.
    - `api_key_value` string — Elasticsearch API key value.
    - `cloud_id` string — Unique Id to configure your client to work with your Elastic Cloud deployment.
  - `git` object
    - `access_token` string — Github Access Token for authentication using Access Token.
    - `alias` string — Alias for GitHub repo instance.
    - `url` string — Git repository URL, ex: GitHub personal repo -> `https://github.com/<username>/<repo-name>` for Organization repo -> `https://github.com/<org-name>/<repo-name>`.
  - `gke` object
    - `alias` string — Alias for GKE integration instance.
    - `service_account_key` string — Provide Service Account Key in JSON Format.
  - `http` object
    - `alias` string — Alias for Http Endpoint integration instance.
    - `api_key` string — API Key for authentication.
    - `authorization_type` string — Select a method for HTTP request authorization.
    - `password` string — Password for authentication.
    - `token` string — Bearer token for authentication.
    - `url` string — A valid URL string based on the secure HTTPS protocol is required.
    - `username` string — Username for authentication.
  - `humio` object
    - `alias` string — Alias for Humio integration instance.
    - `humio_api_token` string — API Token obtained from Humio.
    - `humio_url` string — Provide Humio Cloud URL, example: https://cloud.us.humio.com.
  - `jenkins` object
    - `alias` string — Alias for Jenkins integration instance.
    - `api_token` string — API Token from authorized user.
    - `server_url` string — Jenkins server url:port.
    - `username` string — Jenkins Username associated with the token.
  - `jira` object
    - `JIRA_ACCESS_TOKEN` string — Jira Access Token.
    - `JIRA_CONSUMER_KEY` string — Consumer Key for Fylamynt Application in Jira.
    - `JIRA_CONSUMER_NAME` string — Consumer Name for Fylamynt Application in Jira.
    - `JIRA_KEY_CERT` string — Jira Key Certificate.
    - `JIRA_PUBLIC_KEY` string — Public Key for Fylamynt Application in Jira.
    - `JIRA_TOKEN_SECRET` string — Jira Token Secret.
    - `JIRA_URL` string — URL of your Jira account.
    - `alias` string — Alias for Jira integration instance.
  - `new_relic` object
    - `account_id` integer — Unique account id to recognize your new relic account.
    - `alias` string — Alias for New Relic integration instance.
    - `api_key` string — New Relic API key.
  - `pagerduty` object
    - `alias` string — Alias for PagerDuty integration instance.
    - `pagerduty_api_token` string — API Token obtained from PagerDuty.
  - `pulumi` object
    - `access_token` string — Pulumi Access Token.
    - `alias` string — Alias for Pulumi integration instance.
    - `backend` string — S3 bucket with Pulumi Config.
    - `passphrase` string — Passphrase for accessing Pulumi Config.
    - `team` string — Pulumi Organization.
  - `s3` object
    - `alias` string — Alias for S3 integration instance.
    - `name` string — S3 bucket name.
    - `target` string — Select an AWS Target Account for the S3 bucket.
  - `servicenow` object
    - `alias` string — Alias for ServiceNow integration instance.
    - `instance_url` string — ServiceNow instance URL.
    - `password` string — Password for authorized user on ServiceNow instance.
    - `username` string — Username for authorized user on ServiceNow instance.
  - `slack` object
    - `access_token` string — Slack OAuth2 token.
    - `alias` string — Alias for Slack integration instance.
    - `expire_time` string — Slack OAuth2 token expire time.
    - `refresh_token` string — Slack OAuth2 refresh token.
    - `scope` string — Permission scope for the Fylamynt App.
    - `slack_client_id` string — The ID associated with the Slack App.
    - `slack_client_secret` string — Slack App Client Secret.
    - `slack_signing_secret` string — Secret that Slack is signing every request with.
    - `slack_team_id` string — Id of Slack team/workspace that the token belongs to.
    - `slack_team_name` string — Name of Slack team/workspace that the token belongs to.
    - `slack_user_id` string — ID of the Slack user authenticated with Fylamynt.
    - `slack_user_name` string — Real name or username of the Slack user authenticated with Fylamynt.
  - `splunk` object
    - `access_token` string — Token used to access the Splunk instance.
    - `alias` string — Alias for Splunk integration instance.
    - `splunk_url` string — URL of the Splunk instance (e.g. 65.132.55.921). Do not include the port number.
  - `splunk_on_call` object
    - `alias` string — Alias for Splunk On-Call integration instance.
    - `api_id` string — API ID obtained from Splunk On-Call (VictorOps).
    - `api_key` string — API Key obtained from Splunk On-Call (VictorOps).
  - `spot` object
    - `alias` string — Alias for Spot integration instance.
    - `api_token` string — A Spot Programmatic API Token is recommended or you may use a Personal Access Token.
  - `ssh` object
    - `alias` string — Alias for SSH target instance.
    - `hostIdentifier` string — Identifier for SSH target host such as hostname or public IPv4.
    - `privateKey` string — Private RSA key to run command without username/password.
  - `sumologic` object
    - `access_id` string — Unique access_id to access your Sumo Logic account.
    - `access_key` string — API key for authorization.
    - `alias` string — Alias for Sumologic integration instance.
  - `terraform` object
    - `alias` string — Alias for Terraform Cloud integration instance.
    - `organization` string — Terraform Cloud organization.
    - `token` string — Terraform Cloud API token (User or team token only).
  - `terraform_cli` object
    - `alias` string — Alias for Terraform CLI instance.
    - `git_repo` string — The GIT repo as a source for the Terraform module.
    - `root` string — Directory with root module (defaults to .).
    - `s3_bucket` string — An S3 bucket as a source for the Terraform module.
    - `source_type` string — Different terraform source options.
  - `twilio` object
    - `accountSid` string — Account SID from Twilio dashboard to identify user at twilio end.
    - `alias` string — Alias for Twilio integration instance.
    - `authToken` string — Authentication token for Twilio account.
  - `zendesk` object
    - `alias` string — Alias for Zendesk integration instance.
    - `api_token` string — API token for authorization.
    - `email` string — Email id associated with your Zendesk account.
    - `subdomain_name` string — Enter Zendesk Subdomain name - https://<subdomain_name>.zendesk.com.

## Response `201`

Created

- object
  - `body` object — Response body.
    - `s3` object
      - `alias` string — Alias for the integration.
      - `connection_status` boolean — Connection status of the integration.
      - `date_updated` integer — Timestamp of last update.
      - `date_verified` integer — Timestamp of last verification.
      - `integration_id` string — Unique identifier for the integration.
      - `is_default` string — Default status of the integration.
      - `workspace_id` string — Workspace ID associated with the integration.
      - `name` string — S3 bucket name.
      - `target` string — Select an AWS Target Account for the S3 bucket.
  - `statusCode` integer — HTTP status code.

## Other responses

- `400` — Bad Request
- `404` — Not Found
- `409` — Conflict
- `422` — Unprocessable Entity
- `500` — Internal Server Error

---

[API](https://skmtc.net/spot/apis/spot-by-flexera-api.md) · [All operations](https://skmtc.net/spot/apis/spot-by-flexera-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/spot/spot-by-flexera-api/revisions/2e5445f30576/schema)
