Polygon
Polygon provides comprehensive financial market data APIs, offering real-time and historical stock, options, forex, and crypto data to help businesses build sophisticated financial applications and trading systems.
Power end-to-end data operations for your Polygon API with Nexla. Our bi-directional Polygon connector is purpose-built for Polygon, 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 Polygon or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Polygon 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
Before creating a Polygon credential, you need to obtain your Bearer Token (API Key) from your Polygon account. Polygon uses Bearer Token authentication for all API requests, with the token sent in the Authorization header.
To obtain your Polygon Bearer Token, follow these steps:
-
Sign in to your Polygon account, or create a new account at Polygon.
-
Navigate to your Polygon dashboard or account settings in the Polygon interface.
-
Look for the API Keys or API section in your account settings or dashboard.
-
If you don't have an API key yet, click Create API Key or Generate API Key to create a new API key.
-
Configure your API key settings:
- Enter a name for the API key (e.g., "Nexla Integration")
- Review and select the permissions or scopes for the key (if applicable)
-
Click Create or Generate to create the API key.
-
Copy the Bearer Token (API Key) immediately after it's generated, as it may not be accessible again after you navigate away from the page.
-
Store the Bearer Token securely, as you will need it to configure your Nexla credential. The Bearer Token is sensitive information and should be kept confidential.
The Bearer Token is sent in the Authorization: Bearer {token} header for all API requests to the Polygon API. The Bearer Token authenticates your requests and grants access to Polygon resources based on your account permissions. If your Bearer Token is compromised, you should immediately revoke it in your Polygon account settings and generate a new one. For detailed information about obtaining Bearer Tokens, API authentication, and available endpoints, refer to the Polygon API documentation.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| Polygon Bearer Token | Yes | Yes | Authorization header to the request with your API Key as the token. |
Create a credential in Nexla
- After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Polygon

-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Polygon uses Bearer Token authentication for all API requests, with the token sent in the
Authorizationheader. Enter your Polygon Bearer Token in the Polygon Bearer Token field. This is the Bearer Token (API Key) you obtained from your Polygon account settings (API Keys section). The Bearer Token is sent in theAuthorization: Bearer {token}header for all API requests to the Polygon API. The Bearer Token is sensitive information and must be kept confidential.Your Polygon Bearer Token can be found in your Polygon account settings under the API Keys section. The Bearer Token is sent in the
Authorization: Bearer {token}header for all API requests to the Polygon API.If your Bearer Token is compromised, you should immediately revoke it in your Polygon account settings and generate a new one. The Bearer Token provides access to your Polygon account data and should be treated as sensitive information. Keep your Bearer Token secure and do not share it publicly.
For detailed information about obtaining Bearer Tokens, API authentication, and available endpoints, see the Polygon API documentation.
-
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 Polygon connector tile, then select the credential that will be used to connect to your Polygon account, and click Next; or, create a new Polygon 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 Polygon 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
Polygon data sources can also be manually configured to ingest data from any valid Polygon API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom query 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.
Polygon API typically uses the GET method. Endpoint URLs include the API version and resource path (e.g., https://api.polygon.io/v3/reference/tickers/{ticker}, https://api.polygon.io/v1/open-close/{ticker}/{date}). For the Response Data Path, use $.results[*] to extract all items from a results array, or $ to extract the entire response for single-record endpoints, depending on the endpoint.
Once all of the relevant settings have been configured, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.