Skip to main content

Authorization

Follow this guide to create a new Polygon credential that will allow Nexla to authenticate to and exchange data with your Polygon account.
polygon_api_auth.png

Polygon

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:

  1. Sign in to your Polygon account, or create a new account at Polygon.

  2. Navigate to your Polygon dashboard or account settings in the Polygon interface.

  3. Look for the API Keys or API section in your account settings or dashboard.

  4. If you don't have an API key yet, click Create API Key or Generate API Key to create a new API key.

  5. 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)
  6. Click Create or Generate to create the API key.

  7. 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.

  8. 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.

Create a Polygon Credential

  • To create a new Polygon credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Polygon

PolygonCred.png

Credential Name & Description

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

    Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Bearer Token Authentication

Polygon uses Bearer Token authentication for all API requests. The Bearer Token is sent in the Authorization header to authenticate API requests to the Polygon API.

  1. 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 the Authorization: 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.

Save the Credential

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. 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.