Sigma Computing

Sigma Computing is a cloud-native analytics and business intelligence platform that lets teams explore, model, and share data directly against their cloud data warehouse using a spreadsheet-like interface. Its REST API provides programmatic access to organization resources such as members, teams, workbooks, data models, and warehouse connections, enabling administration and integration workflows.

Power end-to-end data operations for your Sigma Computing API with Nexla. Our bi-directional Sigma Computing connector is purpose-built for Sigma Computing, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Sigma Computing or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Sigma Computing workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Sigma Computing credential, you need an OAuth2 client ID and client secret for the Sigma REST API, along with your organization's API base URL and token endpoint. Sigma authenticates API requests with a bearer token that your client credentials generate; tokens are short-lived and are refreshed automatically by Nexla. Generating API credentials requires the Admin account type in Sigma.

To obtain your Sigma Computing credentials, follow these steps:

1. Sign in to Sigma with an Admin account.

2. Open Administration, either from Sigma Home or from your user avatar menu.

3. In the side panel, select Developer access. Your organization's API base URL is displayed at the top of this page. Note this value, as it is required when creating your Nexla credential.

4. Click Create new to open the credential creation modal.

5. Under Select scopes, check the box for REST API.

6. Enter a unique Name for the credentials (for example, "Nexla integration"), and optionally add a Description.

7. Under Owner, select the organization member whose permission level the API calls should run as.

8. Click Create to generate the credentials.

9. Immediately copy and securely store both the client ID and client secret. The client secret cannot be retrieved after the dialog is closed.

Your Sigma OAuth2 token endpoint follows the pattern https://<api-base-host>/v2/auth/token (for example, https://api.sigmacomputing.com/v2/auth/token on GCP). Both the base URL and token endpoint vary by the cloud provider and region that hosts your Sigma organization, and both are shown under Administration > Developer access. For details about API authentication, base URLs, and available endpoints, see the Sigma Computing API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	No	OAuth2 client ID issued by Sigma for API access.
Client Secret	Yes	Yes	OAuth2 client secret issued by Sigma for API access.
Base URL	Yes	No	API base URL.
Access Token URL	Yes	No	Sigma OAuth2 token endpoint, e.g. https://api.sigmacomputing.com/v2/auth/token.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter the Client ID and Client Secret issued by Sigma in the corresponding fields. These are the OAuth2 credentials you generated in Prerequisites, and Nexla uses them to obtain a bearer token for each API session.

4. Enter your organization's Base URL and Access Token URL. Both values are shown under Administration > Developer access in Sigma and depend on the cloud provider and region hosting your organization.

   If your client secret is compromised, generate a new API credential in Sigma under Administration > Developer access and delete the affected one. The client secret grants access to your Sigma organization at the owner's permission level and should be treated as sensitive information.

   For detailed information about API authentication, base URLs, and available endpoints, see the Sigma Computing API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Sigma Computing connector tile, then select the credential that will be used to connect to the Sigma Computing instance, and click Next; or, create a new Sigma Computing credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Sigma Computing endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Members

Retrieve members.

• This endpoint returns the members of your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about members, response fields, and pagination, see the Sigma API reference.

[Rest API] List Teams

Retrieve teams.

• This endpoint returns the teams in your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about teams, response fields, and pagination, see the Sigma API reference.

[Rest API] List Files

Retrieve files.

• This endpoint returns the files in your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about files, response fields, and pagination, see the Sigma API reference.

[Rest API] List Connections

Retrieve connections.

• This endpoint returns the data warehouse connections configured in your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about connections, response fields, and pagination, see the Sigma API reference.

[Rest API] List Workbooks

Retrieve workbooks.

• This endpoint returns the workbooks in your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about workbooks, response fields, and pagination, see the Sigma API reference.

[Rest API] List Data Models

Retrieve data models.

• This endpoint returns the data models in your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about data models, response fields, and pagination, see the Sigma API reference.

[Rest API] List API Credentials

Retrieve API credentials.

• This endpoint returns the API credentials registered in your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about API credentials, response fields, and pagination, see the Sigma API reference.

[Rest API] List Account Types

Retrieve account types.

• This endpoint returns the account types defined in your Sigma organization. Results are paginated, and Nexla automatically follows the pagination tokens to fetch all available records.

For detailed information about account types, response fields, and pagination, see the Sigma API reference.

[Rest API] Get Workbook

Retrieve a single workbook by ID.

• Provide the Workbook ID (the Sigma workbook UUID) to retrieve a single workbook. This endpoint returns one record and is not paginated.

For detailed information about the workbook object and its response fields, see the Sigma API reference.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Sigma Computing data sources can also be manually configured to ingest data from any valid Sigma REST API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Sigma Computing data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Sigma Computing destination, and select the Send to Destination option from the menu. Select the Sigma Computing connector from the list of available destination connectors, then select the credential that will be used to connect to the Sigma Computing organization, and click Next; or, create a new Sigma Computing credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Sigma Computing endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Member

Invite and create a new member in the Sigma organization.

• Each record from your Nexset is sent as a JSON request body to invite and create a new member. Ensure the record fields match the member payload expected by the Sigma API.

For details about the member payload and required fields, see the Sigma API reference.

[Rest API] Create Team

Create a new team in the Sigma organization.

• Each record from your Nexset is sent as a JSON request body to create a new team. Ensure the record fields match the team payload expected by the Sigma API.

For details about the team payload and required fields, see the Sigma API reference.

[Rest API] Create Connection

Create a new data warehouse connection in Sigma.

• Each record from your Nexset is sent as a JSON request body to create a new data warehouse connection. Ensure the record fields match the connection payload expected by the Sigma API.

For details about the connection payload and required fields, see the Sigma API reference.

[Rest API] Update Connection

Update an existing data warehouse connection in Sigma.

• Each record from your Nexset is sent as a JSON request body to update an existing connection. Include the connection identifier so Sigma can locate the connection to modify.

For details about the update payload and required fields, see the Sigma API reference.

[Rest API] Create Data Model

Create a new data model from a code specification in Sigma.

• Each record from your Nexset is sent as a JSON request body containing the data model code specification. Ensure the record fields match the spec payload expected by the Sigma API.

For details about the data model spec payload and required fields, see the Sigma API reference.

[Rest API] Delete Connection

Delete a data warehouse connection in Sigma.

• Each record from your Nexset triggers deletion of a data warehouse connection. Include the connection identifier so Sigma can locate the connection to delete.

Deleting a connection is irreversible. For details about this operation, see the Sigma API reference.

[Rest API] Create API Credential

Create a new API credential in Sigma.

• Each record from your Nexset is sent as a JSON request body to create a new API credential. Ensure the record fields match the credential payload expected by the Sigma API.

For details about the API credential payload and required fields, see the Sigma API reference.

Manual configuration

Sigma Computing destinations can also be manually configured to send data to any valid Sigma REST API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Sigma Computing APIs expect JSON request bodies for write operations. For update or delete operations, include the identifier of the object to be modified as required by the target endpoint.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Sigma Computing endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Sigma Computing endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.