Connector Studio is a low-code experience, enabling users to create a connector to a data sources where a pre-built, Solver connector is not available. Connector Studio is currently in preview and available in Solver’s Demo Environment. Anticipated production availability is December 2026.
A connector created in Connector Studio is available in the tenant you are currently logged into. There are four main steps in creating a connector
- Define the connector
- Give a descriptive name for the connector you are about to create.
- Upload an optional branding logo.
- Authentication and Endpoints
- Provide the authentication information to be used when creating an integration.
- Define the endpoints to be connected to and the attributes
- Connector Properties
- Optional properties that include paging
- Publishing the Connector: Publish the connector so that users that can create integrations can see this new connector and begin creating integrations with it.
The next section will go over requirements and need to knows, prior to creating your first connector in connector studio.
Data Source Requirements
Before using Connector Studio, it is important to review your source systems API requirements and license terms. When reviewing the API requirements and licensing, the following is important to review.
- Review the table below of supported Data Source and Authentication Methods. If your source system does not provide an API one of the below formats, Connector Studio currently does not support it.
- Source system API provider requirements
- The API must be publicly available
- Enabling an API on your source system may incur fees that are not included with Connector Studio.
These fees can include
– Accessing the API
– Number of API requests per hour/day/month
Review and discuss your organization’s license terms with the source system you wish to connect to Solver, before using Connector Studio. - Your provider may have requirements to query the data. Currently connector studio only supports paging.
Supported Data Sources and Authentication
Connector Studio supports various data source formats and authentications. The below table represents currently supported data formats.
| Data and Auth Format | Avaialbe | Notes |
|---|---|---|
| REST Responses – OAuth 2 – Basic – API Key – Session Tokens – No AUth | Oct 2026 (Demo) | Review your data providers documentation for authentication requirements. – OAuth2 requires a client app to be created on your source system. |
| Delimited Responses | Nov 2026 (Demo) | |
| OData Responses | Dec 2026 (Production) |
API Requests
Some data providers have a tiered system that enables you to make a certain number or API requests per month based off the subscription you have purchased.
- The number of requests made are based off of all of your applications extracting data, not just limited to Solver.
Review these limits prior to creating a connector and ensure there are mechanisms to notify you should you be getting close to any API limits your provider may be imposing.
Creating a Connector
Accessing Connector Studio
In order to use Connector Studio, you must first be given “Can view Connector Studio” permissions. Being granted this permission will enable you to
- See all connectors that have been configured in Connector Studio.
- Full permissions to any connector in Connector Studio including Create, Edit and Delete permissions.
- Use a service account with restricted permissions when creating a connector. User account passwords can be viewed in connector studio.
Follow these instructions to grant permissions to Connector Studio and other features in Solver. Once enabled, upon next login, Connector Studio will appear in the Settings menu.
Creating a Connector
To create a connector in Connector Studio
- Navigate to Settings > Connector Studio.
- All connectors that have been created will appear. If no connectors have been created click Create a Connector to begin.
- If connectors exist, in the upper right hand corner click New Connector to create a new connector.
- The first screen prompts users to provide a connector
- Name – descriptive name of the connector/product being created.
- Description (optional) – additional information about the connector being created. Users can add information about where the API information is located and the data that is being made available. This information will appear when creating an integration
- Logo (optional) – logo the the data source being created.
- Once completed, click Continue.
- Users will be taken to the wizard where they will see two options
- Authentication & Endpoints
- Properties
- Click Authenticate.
- On the screen that appears, complete the following
- Authentication Type: choose an authentication type that is supported by the API you plan to connect to. This authentication is used throughout the Connector Studio wizard and also when creating an integration.
- Header requests are supported as part of authenticating and making API requests. Review your source systems API requirements to identify any headers that ay be needed.
- Based off the select authenticaiton type, additional text boxes will appear.
- API-Key/Bearer/Basic/No Auth – Provide the necessary username/password/key necessary to authenticate.
- the provided information is not validated until users create an endpoint.
- OAuth2 – OAuth2 requires the configuration of an “App” or “App Registration” (terminology varies by product) in the source system to establish OAuth authentication
- ClientID: when you successfully create the above mentioned app, a Client ID is assigned.
- As part of creating a ClientID, a Client Secret is also created. Client secrets should not be shared.
- Authorization URL: read your providers documentation for the authorization URL.
- For systems that require you to define scopes, include the scopes in the Authorization URL.
- Token URL: read your providers documentation for the token URL.
- Look specifically for the token URL and not the token refresh URL.
- Redirect URI: In the connection box, a redirect URI has been provided. In the app that you have created in your source system, add this URI to the list of approved redirect URIs.
- An additional URI is needs to be added: {environmentURL}/api/dw/oauth/v2/authorizationCallback
where environmentURL can be https://us.app.solverglobal.com
- An additional URI is needs to be added: {environmentURL}/api/dw/oauth/v2/authorizationCallback
- ClientID: when you successfully create the above mentioned app, a Client ID is assigned.
- API-Key/Bearer/Basic/No Auth – Provide the necessary username/password/key necessary to authenticate.
- Authentication Type: choose an authentication type that is supported by the API you plan to connect to. This authentication is used throughout the Connector Studio wizard and also when creating an integration.
- If you have chosen OAuth, click Connect to Authenticate. This is required in order to successfully view data when creating endpoints.
- Tokens have an expiration time which varies by provider. When using Connector Studio for extended periods of time, it is possible that previewing data may stop working due to your token expiring. If this happens, simply click Back to reauthenticate.
- Once the authentication information is completed, click Continue.
- On the next screen that appears, users will create the endpoints that they want to make available to end users.
The left side of the menu displays the friendly names of the endpoints that have been created. The checkbox next to each endpoint allows you to enable/disable that specific endpoint. By disabling it, the endpoint is visible in Connector Studio but not available when creating an integration.
- URL: provided the URL of the endpoint that you would like to connect to.
- Include filters in your URL to optimize your data loads.
- Depending on the provider, the endpoint name may be case sensitive. Type in the endpoint name with the exact casing that matches the providers documentation.
- Friendly Name: provide a friendly name for the endpoint you are creating
- URL: provided the URL of the endpoint that you would like to connect to.
- Click Run Preview. Assuming the previously provided credentials are correct, clicking preview will display:
- Response Format: information that the connector needs to read the API. This typically does not need to be changed.
- Path to Data: the string in the API response where the transaction data is found. This typically does not need to be changed.
- Attribute List: the attribute list will populate with all attributes of the URL provided.
- Depending on the provider, this list may need to be case sensitive. Follow the format seen in the JSON View.
- Table/Raw JSON view
- Table View shows the top 5 rows of data to give a visual of how the data will look when creating and integration
- Raw JSON view show the API response. This is useful should you remove attributes from the above Attribute List and want to re-add them later.
- For response that provide a next URL, take note of the string. This string is used later when working with Connector Properties.
- Review the table data and the attribute list. It is recommended to remove attributes that you do not need as this will be a performance improvement when running an integration.
- Repeat the process, creating as many endpoints as needed.
- Once you have added your endpoints, click Continue.
- Returning back to the Connector Studio wizard, users can click the properties section to define properties of the connector, if supported. This is an optional section.
These properties include:- Paging: Choose this option for APIs that support paging. It is always recommended to use paging and set the value no more the 2000 results per request. Any request larger than this can result in slower integrations. Paging requires a couple pieces of information:
- Offset Parameter: the string that represents the start value when requesting data.
- Offset Value: the number to start at, this will typically be 0
- Top Parameter: the string that represents the number of records to request.
- Top value: the number of records per request. This number is customizable but is recommended to not exceed 2000.
- Offset Parameter: the string that represents the start value when requesting data.
- Next URL: choose this option if you system does paging natively and provides a “nextURL”. Choosing this option require the user to
- Next Page URL Location: Choose from the dropdown the location of the next URL.
- Next Page URL: provide the string the provider is using to identify the nextURL in the response.
- Paging: Choose this option for APIs that support paging. It is always recommended to use paging and set the value no more the 2000 results per request. Any request larger than this can result in slower integrations. Paging requires a couple pieces of information:
- Once completed, click Review & Create.
- The final page will show the details of the connector you just created. There are a couple options.
- Save and Publish: Choose this option to save your connector and publish it. By publishing the connector, you are making this connector available to anyone who can create an integration on the tenant.
- Save Draft: Choose this option to save your work as a draft.
- The work done in a draft is not available to users who are responsible for creating an integration.
- As mentioned above, any users with Connector Studio permissions can edit a draft.
- Only one draft per connector is allowed, based of the connector name.
- Cancel: takes you back to the configuration screen.
Clicking Save and Publish or Save Draft will save your work and take you back to the Connector Studio landing page where you should see your newly created connector. The cards should show the information about your connector including
- Connector Name
- Description (if added)
- Logo
- the default connector studio logo will appear if no logo was added.
- Version number: an auto incrementing number with each published version. The numbering sequence is 1.0.N, where N starts at 0.
- States
- Production – a published connector users can create an integration from.
- Production – Draft – a published connector that also has a draft in progress.
- Draft – an unpublished connector, only visible in connector studio.
Edit a Connector
To edit a connector from within Connector Studio, simply click on the connector you would like to edit. Follow the above steps in terms of creating and editing endpoints.
Deleting a Connector
Users can delete connectors only if there are no integrations using that connector. To delete a connector
- On the Connector Studio landing page, click the Trash Can for the connector you’d like to delete.
- Users will be prompted with a message to confirm the action. Click Delete to delete the connector.
- If a draft exists, or you need to delete the draft, upon clicking the Trash Can, users will be prompted to choose between deleting the draft and deleting the production version.
- Deleting the draft will delete just the draft, allowing you to “restore” your editing back to the current production version.
- Deleting the production version will delete the connector, including the draft and the production connector itself.
As mentioned above, if you attempt to delete a connector but integrations have been created from it, users will see a message upon click delete that the action is not allowed. The user must delete all integrations referencing the connector before being able to delete the connector from Connector Studio.
Unsupported Features
The following are known, unsupported features. Please submit your issues to Solver Support who can triage your questions to the appropriate teams.
- Be sure to review our list of supported data responses. Anything not on this list is not supported.
- Nested array responses
- Some APIs present data in a nested array, think of this as line item details for a summary level transaction. Nested response are currently not supported and solver will return the first array of that response.
An example of this could be{"id":"1","SalesPerson",[{"SalesPersonId:"10","SalesPersonId":"12"}]}
You can see in this example that for the SalesPerson attribute there are two Ids, 10 & 12. In this case, Connector Studio can only grab the first value in the array, 10.
- Some APIs present data in a nested array, think of this as line item details for a summary level transaction. Nested response are currently not supported and solver will return the first array of that response.
- OAuth with non-standard access token parameters. Review your providers OAuth Access Token Parameters documentation, typically found in their developer portal. If there are any additional parameter values outside of the below list, this is an unsupported OAuth response.
- access_token
- token_type
- expires_in
- refresh_token
- scope