Integration Parameters
The integration creation endpoint is generic and can be used for all native integrations. For specific integration parameters for a given service, please review the respective documentation below.us-east-1
dev
/some/path
. The root of the environment is /
.Authorizations
An access token in Infisical
Body
The ID of the integration auth object to link with integration.
The environment to sync secret from.
The name of the external integration providers app entity that you want to sync secrets with. Used in Netlify, GitHub, Vercel integrations.
Whether the integration should be active or disabled.
The ID of the external integration providers app entity that you want to sync secrets with. Used in Netlify, GitHub, Vercel integrations.
The path of the secrets to sync secrets from.
The target environment of the integration provider. Used in cloudflare pages, TeamCity, Gitlab integrations.
The target environment ID of the integration provider. Used in cloudflare pages, teamcity, gitlab integrations.
The service based grouping identifier of the external provider. Used in Terraform cloud, Checkly, Railway and NorthFlank.
The service based grouping identifier ID of the external provider. Used in Terraform cloud, Checkly, Railway and NorthFlank.
External integration providers service entity owner. Used in Github.
The self-hosted URL of the platform to integrate with.
Path to save the synced secrets. Used by Gitlab, AWS Parameter Store, Vault.
AWS region to sync secrets to.
Scope of the provider. Used by Github, Qovery.
Response
Default Response