Wicket

Wicket is a SaaS membership software that is built to integrate with best-in-class software such as MailChimp, Shopify, Eventbrite, and Drupal.

Power end-to-end data operations for your Wicket API with Nexla. Our bi-directional Wicket connector is purpose-built for Wicket, 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 Wicket or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Wicket 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 Wicket credential, you need to obtain your Wicket Tenant ID, Wicket User UUID, and Wicket Secret Key from your Wicket account. Wicket uses JSON Web Token (JWT) authentication for all API requests.

To obtain your Wicket credentials, follow these steps:

1. Sign in to your Wicket account using your administrator credentials.

2. Navigate to your Wicket account settings or API configuration in your Wicket dashboard.

3. To obtain your Wicket Tenant ID, look at your Wicket API URL. The tenant ID is the prefix for your instance hosted in the cloud. For example, in https://your-tenant-api.wicketcloud.com/, your-tenant is the tenant ID you need to enter.

4. To obtain your Wicket User UUID and Wicket Secret Key, you need to contact Wicket customer support. Navigate to Wicket Support to request your API User UUID and Secret Key. You will need a Wicket API User with administrative privileges.

5. When contacting support, specify that you need:

   • Wicket API User UUID: The UUID of an API user with administrative privileges
   • Wicket Secret Key: The API Secret Key associated with the API user

6. Store all credentials securely, as you will need them to configure your Nexla credential. The Secret Key is sensitive information and should be kept confidential.

The Wicket Tenant ID is used to construct the API endpoint URLs. The Wicket User UUID and Secret Key are used to generate JWT tokens for authentication. The JWT tokens are sent in the Authorization header as Bearer tokens for all API requests to the Wicket API. If your credentials are compromised, you should immediately contact Wicket support to revoke them and generate new ones. For detailed information about Wicket API authentication, see the Wicket API documentation.

Authenticate

Credentials required

JSON Web Token is used to access the API by providing token in the Authorization header.

Field	Required	Secret	Description
Wicket tenant ID	Yes	No	Wicket prefix for your instance hosted in the cloud, for example, in https://your-tenant-api.wicketcloud.com/ - 'your-tenant' is the value you need to enter here.
Wicket User UUID	Yes	No	Wicket API User UUID with administrative privileges. To obtain it please contact customer support at https://support.wicket.io/.
Wicket secret key	Yes	Yes	Wicket API Secret Key of the API User with administrative privileges To obtain it please contact customer support at https://support.wicket.io/.

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.

New Credential Overlay – Wicket

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

3. Enter your Wicket tenant ID in the Wicket tenant ID field. This is the Wicket prefix for your instance hosted in the cloud. For example, in https://your-tenant-api.wicketcloud.com/, your-tenant is the value you need to enter here. The Tenant ID is used to construct the API endpoint URLs.

4. Enter your Wicket User UUID in the Wicket User UUID field. This should be the Wicket API User UUID with administrative privileges. To obtain it, please contact customer support at Wicket Support. The User UUID is used as the subject (sub) claim in the JWT token.

5. Enter your Wicket secret key in the Wicket secret key field. This should be the Wicket API Secret Key of the API User with administrative privileges. To obtain it, please contact customer support at Wicket Support. The Secret Key is used to sign the JWT token and is sensitive information that must be kept confidential.

   Your Wicket credentials (Tenant ID, User UUID, Secret Key) can be found in your Wicket account settings or by contacting Wicket Support. The Tenant ID can be extracted from your Wicket API URL (e.g., https://your-tenant-api.wicketcloud.com/). The User UUID and Secret Key must be obtained by contacting Wicket customer support, as they require an API user with administrative privileges.

   If your credentials are compromised, you should immediately contact Wicket support to revoke them and generate new ones. The credentials provide access to your Wicket account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about Wicket API authentication, see the Wicket API documentation.

6. 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 Wicket connector tile, then select the credential that will be used to connect to the Wicket instance, and click Next; or, create a new Wicket 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 Wicket 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.

Fetch all people from the current resource

This endpoint template fetches all people of any resource from your Wicket account. Use this template when you need to access people information, member data, or people metadata for analysis, reporting, or integration purposes. Use the advanced tab for fetching a filtered list of people records.

• This endpoint automatically fetches all people from your Wicket account. No additional configuration is required beyond selecting this endpoint template. The endpoint uses link-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of people data.

This endpoint returns all people from your Wicket account, including people IDs, names, contact information, and other people metadata. The endpoint uses link-based pagination (following the links.next URL) to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of people data.

For detailed information about people, API response structures, pagination, and available people data, see the Wicket API documentation.

Fetch all groups from the current resource

This endpoint template fetches all groups of any resource from your Wicket account. Use this template when you need to access group information, group data, or group metadata for analysis, reporting, or integration purposes. Use the advanced tab for fetching a filtered list of groups.

• This endpoint automatically fetches all groups from your Wicket account. No additional configuration is required beyond selecting this endpoint template. The endpoint uses link-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of group data.

This endpoint returns all groups from your Wicket account, including group IDs, names, descriptions, and other group metadata. The endpoint uses link-based pagination (following the links.next URL) to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of group data.

For detailed information about groups, API response structures, pagination, and available group data, see the Wicket API documentation.

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

Wicket data sources can also be manually configured to ingest data from any valid Wicket 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.

Wicket API endpoints typically follow the pattern https://{tenant}-api.wicketcloud.com/{endpoint_path} where {tenant} is your Wicket tenant ID. The endpoint requires JWT authentication via the Authorization header, which is handled automatically by your credential configuration.

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 Wicket 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 Wicket destination, and select the Send to Destination option from the menu. Select the Wicket connector from the list of available destination connectors, then select the credential that will be used to connect to the Wicket instance, and click Next; or, create a new Wicket 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 Wicket 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.

Create a group

This endpoint template creates a new group on your Wicket instance. Use this template when you need to automatically create groups based on data from your Nexla flows.

• This endpoint sends data as JSON in the request body to create new groups. Each record from your Nexset will be sent as a separate API request to create a group. The request body should contain the group data in the format required by the Wicket API, including all required properties for group creation.

This endpoint sends data as JSON in the request body to create new groups in your Wicket instance. Each record from your Nexset will be sent as a separate API request to create a group. The request body should contain the group data in the format required by the Wicket API, including all required properties for group creation.

The group structure must match the Wicket API's expected format. Ensure your group data includes all required fields. For detailed information about group creation, request body formats, and available group properties, see the Wicket API documentation.

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.

Manual configuration

Wicket destinations can also be manually configured to send data to any valid Wicket 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.

The Wicket APIs typically expect JSON format for most operations. For create operations, the URL typically follows the pattern https://{tenant}-api.wicketcloud.com/{resource_type} where {tenant} is your Wicket tenant ID and {resource_type} is the type of resource you want to create (e.g., groups, people). For update/upsert operations, include the ID of the object to be updated at the end of the URL.

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 Wicket endpoint, open the destination resource menu, and select Activate.

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