Celonis Product Documentation

The Amazon S3 REST API requires you to provide an access key ID and a secret access key in order to connect to the Celonis Platform.

You can create both access key ID and the secret access key in the My Security Credentials of your Amazon S3 instance. When creating these assets, you should assign the following permissions:

A JSON example of these permissions is:

{
    "Version": "2023-11-30",
    "Statement": [
        {
            "Sid": "Celonis S3 Extractor",
            "Effect": "Allow",
            "Principal": {
                "AWS": "<THE ARN OF YOUR IAM USER>"
            },
            "Action": [
                "s3:GetBucketAcl",
                "s3:GetObject",
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::<YOUR BUCKET>",
                "arn:aws:s3:::<YOUR BUCKET>/*"
            ]
        }
    ]
}

For a full list of available endpoints for Amazon S3, see: Amazon S3 API Reference.

When connecting to Amazon S3, note the following points:

The Bamboo REST API uses basic authentication. To connect to your Bamboo instance, you need to provide a username and password.

The default Bamboo extractor allows you to call these endpoints:

For further information about Bamboo and their REST APIs, see: Bamboo Documentation - REST APIs.

The Bitbucket Cloud REST API uses basic authentication or OAuth2:

For both authentication methods you must also supply the project and repository name as parameters.

The default Bitbucket Cloud extractor allows you to call these endpoints:

For more information about Bitbucket Cloud, see: Bitbucket Cloud Documentation - REST APIs.

Conexiom REST API uses the OAuth 2 authentication method. To establish a connection to Conexiom, you must provide the following information:

The default Conexiom extractor allows you to call these endpoints:

For further information about Conexiom, see: Conexiom Knowledge Base.

The Confluence Cloud REST API uses basic authentication or OAuth2:

For both authentication methods you must also supply the project and repository name as parameters.

The default Confluence Cloud extractor allows you to call these endpoints:

For further information about Confluence Cloud's REST API, see: Confluence Cloud - API Documentation.

The EcoVadis REST API uses OAuth2 authentication:

The default EcoVadis extractor allows you to call this endpoints:

For further information about EcoVadis, see: EcoVadis Help Center.

The Gmail REST API uses the OAuth2 authentication method, requiring you to provide a username, password, client ID, and client secret. To access these, you must complete the following steps in your Google Workspace:

The default Gmail extractor allows you to call these endpoints:

For further information about Gmail's REST API, see: Google Workspace - Gmail API Overview.

The Google Calendar REST API uses the OAuth2 authentication method, requiring you to provide a username, password, client ID, and client secret. To access these, you must complete the following steps in your Google Workspace:

The default Google Calendar extractor allows you to call these endpoints:

For further information about Gmail's REST API, see: Google Workspace - Gmail API Overview.

The Greenhouse REST API uses OAuth 2 authentication, requiring you to provide an API URL, username, password, client ID, and client secret. To do this, the user profile must have API credentials access enabled in the Developers Permissions area.

With API credentials access, the user can then access Configure - Dev Center - API Credential Management.

The default Greenhouse extractor allows you to call these endpoints:

For further information, see: Greenhouse Help - Harvest API.

The Happyfox REST API uses basic authentication. To connect to your Happyfox instance, you need to provide a username and password.

The default Happyfox extractor allows you to call these endpoints:

For further information about Happyfox APIs, see: Happyfox Support - Developers - APIs.

The Ironclad REST API uses a bearer token for authentication. For more information about the bearer token, see: Ironclad Developer - Bearer Authentication.

The default Ironclad extractor allows you to call these endpoints:

For further information about the Ironclad REST API, see: Ironclad - Developer - API.

The Jira Cloud REST API uses basic authentication. To connect to your Jira Cloud instance, you need to provide your instance URL, and a username and password.

The following tables and their related APIs are available:

For further information about the Jira Cloud REST API, see: Atlassian Developer - REST API.

To connect to SAP Concur, we recommend using OAuth 2.0. Before configuring the data connection in the Celonis Platform, you need access to an SAP Concur user with the necessary permissions extract data to external systems.

To configure your SAP Concur user, refer to the OAuth2.0 Application Management documentation here: SAP Help Portal - SAP Concur

The Celonis extractor uses the standard REST API of SAP Concur. For more information, see: SAP Concur Developers Center.

The Celonis Extractor performs read-only operations on your SAP Concur data. No writing changes (like updates, deletions) will be performed at any time during the extraction process.

The Celonis Extractor is bound to the API call limits applied by SAP Concur, guarding the system from any performance issues.

Transfer of the data from the SAP Concur system to the target system is secured through HTTPS, which allows for an encrypted exchange of information.

The Zendesk REST API uses basic authentication or OAuth2:

For both authentication methods, you must provide your Zendesk realm. This should be provided in the following format:

https://[companyName].zendesk.com

When connecting to Zendesk, note the following points: