GlassFrog
GlassFrog is a cloud-based organizational management platform purpose-built for Holacracy practitioners. Developed by the founders of Holacracy, GlassFrog helps businesses implement, support, and manage self-organizing governance models by providing real-time visibility into roles, circles, accountabilities, projects, and actions. The platform enables organizations to maintain transparent governance records, run tactical and governance meetings, and track who is responsible for what—eliminating ambiguity and empowering distributed decision-making. GlassFrog's API (v3) provides programmatic access to your organization's governance data, including circles, roles, accountabilities, people, projects, and actions, enabling integration with external analytics, reporting, and data management tools.

Power end-to-end data operations for your GlassFrog API with Nexla. Our bi-directional GlassFrog connector is purpose-built for GlassFrog, 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 GlassFrog or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your GlassFrog workflows fast, secure, and fully governed.
Features
Type: API
- 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
To connect Nexla to GlassFrog, you need a GlassFrog account and an API key. GlassFrog API keys are associated with individual user accounts and carry the same permissions as that user. The GlassFrog API (v3) uses JSON and requires an API key for all requests.
Obtain a GlassFrog API Key
GlassFrog allows you to create multiple API keys—one per integration—so that individual keys can be revoked without disrupting other connections.
-
Sign in to your GlassFrog account at app.glassfrog.com.
-
Click your name or avatar in the top-right corner of the application to open the account dropdown menu.
-
Select Profile & Settings from the dropdown.
-
Navigate to the API tab within your profile settings.
-
Enter a descriptive label for the new API key in the label field (for example,
Nexla Integration) to help identify its purpose later. -
Click the button to generate the new API key.
-
Copy the API key immediately and store it in a secure location. The full key value is displayed only at the time of creation.
GlassFrog API keys provide access to your organization's governance data with the same permissions as your user account. Treat API keys like passwords—do not share them in publicly accessible locations or commit them to version control. If a key is compromised, navigate back to Profile & Settings > API and delete the affected key, then create a replacement.
For additional information about GlassFrog API keys, refer to the official GlassFrog support documentation at support.glassfrog.com/glassfrog-api-keys.
Authenticate
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
GlassFrog API v3 authenticates requests using an API key, which can be supplied either as a URL query parameter (
?api_key=YOUR_KEY) or as the value of theX-Auth-Tokenrequest header. Nexla uses the header-based method, which keeps the key out of logged URLs. Enter the GlassFrog API key you generated in Prerequisites in the API Key field. This key authenticates Nexla with the GlassFrog API and must remain confidential. -
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 and can be selected for use with a new data source or destination.
Use as a data source
The GlassFrog API connector enables you to ingest your organization's governance data—including circles, roles, people, accountabilities, projects, actions, and metrics—from GlassFrog into Nexla for reporting, analytics, and integration with other systems. This connector is particularly useful for organizations that want to analyze role distribution, track governance health, or synchronize holacratic structure data with external platforms.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the GlassFrog API connector tile, then select the credential that will be used to connect to the GlassFrog API, and click Next; or, create a new GlassFrog API 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 GlassFrog API 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.
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
GlassFrog API sources can also be manually configured to ingest data from any valid GlassFrog API v3 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, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All GlassFrog API v3 endpoints use the base URL https://api.glassfrog.com/api/v3/ and return JSON responses. The API is read-focused, so GET is the most common method; common endpoint paths include /circles, /roles, /people, /projects, /actions, /checklist_items, /metrics, and /triggers.
GlassFrog API v3 responses wrap records in a JSON object whose top-level key matches the resource name—for example, a request to /circles returns a circles array. Enter the corresponding path (e.g., $.circles[*], $.roles[*]) in the Set Path to Data in Response field so Nexla treats each element as a separate record. Responses often also include a linked object containing referenced data, such as people linked to roles; enter $.linked in the Path to Metadata in Response field to preserve it alongside each record.
You do not need to add the GlassFrog authentication header manually—the X-Auth-Token header is handled automatically by Nexla based on your credential configuration. For a full reference of available endpoints and supported query parameters, refer to the GlassFrog API documentation and the GlassFrog API v3 Postman reference.
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 GlassFrog API 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 GlassFrog API destination, and select the Send to Destination option from the menu. Select the GlassFrog API connector from the list of available destination connectors, then select the credential that will be used to connect to the GlassFrog organization, and click Next; or, create a new GlassFrog API 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 GlassFrog API endpoints. Select the endpoint to which this destination will send data from the Endpoint pulldown menu, then click on a template below to expand it and view configuration details.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to send a test payload. The result will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the destination is configured correctly before saving.
Manual configuration
GlassFrog API destinations can also be manually configured to send data to any valid GlassFrog API v3 endpoint. You can also configure Nexla to automatically send the response received from the GlassFrog API after each call to a new Nexla webhook data source. 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.
GlassFrog API v3 accepts and returns JSON, so select JSON as the Content Format. Use POST to create new resources (such as projects or actions), PATCH to partially update existing resources, and DELETE to remove resources. For update or delete operations, include the ID of the resource at the end of the URL (e.g., https://api.glassfrog.com/api/v3/projects/12345); for create operations, use the collection endpoint (e.g., https://api.glassfrog.com/api/v3/projects). You do not need to add the GlassFrog authentication header manually—the X-Auth-Token header is handled automatically by Nexla based on your credential configuration. For a complete reference of GlassFrog API v3 write endpoints and required request body structures, refer to the GlassFrog API documentation and the GlassFrog API v3 Postman reference.
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 GlassFrog API endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the GlassFrog API endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.