Perigon

Perigon is a news intelligence API that indexes real-time articles, story clusters, journalists, media sources, companies, people, topics, and Wikipedia enrichment data from across the live web. Nexla connects to the Perigon API to ingest this news and entity data into your flows, and to manage Perigon watchlists and source groups. Authentication uses an API key sent as a bearer token.

Power end-to-end data operations for your Perigon API with Nexla. Our bi-directional Perigon connector is purpose-built for Perigon, 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 Perigon or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Perigon 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 Perigon credential, you need an API key from your Perigon account. Perigon authenticates every request with an API key, which Nexla sends as a bearer token in the Authorization header.

To obtain your Perigon API key, follow these steps:

1. Sign up for a Perigon account at perigon.io/sign-up, or sign in to an existing account. A free account can be used to generate an API key for testing.

2. Open your Perigon account dashboard and locate the API key issued for your account.

3. Copy the API key and store it securely. You will paste it into Nexla when creating your credential.

For more detail on authentication and the available endpoints, see the Perigon Authentication documentation and the Perigon API Reference.

Authenticate

Credentials required

An authentication method that requires sending a unique secret token with each API request

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests

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.

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 Perigon API key in the API Key Value field. This value is sent as a bearer token in the Authorization header on every request to the Perigon API and must be kept confidential.

   If your API key is compromised, revoke or rotate it in your Perigon account and update this credential with the new value.

   For more information about authentication and available endpoints, see the Perigon Authentication documentation and the Perigon API Reference.

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

[Rest API] Search articles

Search and filter the full corpus of news articles indexed by Perigon.

This endpoint accepts optional query parameters such as a search query, source, language, page, and size to filter and page through matching articles. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Search stories

Search and filter news stories (clusters of related articles) tracked by Perigon.

This endpoint accepts optional query parameters such as a search query, category, page, and size to filter and page through matching stories. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Get story counts

Get aggregate counts of stories matching a set of filters, bucketed over time.

This endpoint accepts an optional search query parameter to define the set of stories to count. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Get story history

Get the historical timeline of updates for a specific story cluster.

This endpoint accepts a cluster ID query parameter identifying the story whose history should be retrieved. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Search journalists

Search and filter the database of journalists tracked by Perigon.

This endpoint accepts optional query parameters such as a journalist name, page, and size to filter and page through matching journalists. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Get journalist by ID

Retrieve a single journalist profile by its Perigon journalist ID.

This endpoint accepts the journalist ID as a path parameter identifying the profile to retrieve. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Search sources

Search and filter the 200,000+ media sources available via Perigon.

This endpoint accepts optional query parameters such as a source domain, name, page, and size to filter and page through matching media sources. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Search companies

Search and filter the database of companies referenced in Perigon news content.

This endpoint accepts optional query parameters such as a search query, ticker symbol, page, and size to filter and page through matching companies. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Search people

Search and filter the database of notable people tracked by Perigon.

This endpoint accepts optional query parameters such as a person name, page, and size to filter and page through matching people. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Search topics

Search and filter the taxonomy of topics used to classify Perigon content.

This endpoint accepts optional query parameters such as a topic name, page, and size to filter and page through matching topics. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Search Wikipedia

Search and filter the Wikipedia corpus indexed by Perigon for entity enrichment.

This endpoint accepts optional query parameters such as a search query, page, and size to filter and page through matching Wikipedia entries. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Summarize search results

Generate an AI summary over a set of articles matching the given search filters.

This endpoint accepts an optional search query parameter to define the set of articles to summarize. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] List watchlists

List all saved watchlists (custom entity/topic filters) for the authenticated account.

This endpoint accepts optional page and size query parameters to page through the account's watchlists. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] Get watchlist

Retrieve a single watchlist by its ID.

This endpoint accepts the watchlist ID as a path parameter identifying the watchlist to retrieve. For detailed information about request parameters and response fields, see the Perigon API Reference.

[Rest API] List source groups

List custom source groups (curated bundles of publisher domains) for the authenticated account.

This endpoint accepts optional page and size query parameters to page through the account's source groups. For detailed information about request parameters and response fields, see the Perigon API Reference.

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

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

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

[Rest API] Create watchlist

Create a new watchlist (a saved set of entities/topics to monitor) for the authenticated account.

This endpoint sends each Nexset record as a JSON request body to create a new watchlist. The record must match the watchlist structure expected by the Perigon API. For detailed information about the request body and response fields, see the Perigon API Reference.

[Rest API] Update watchlist

Partially update a watchlist owned by the authenticated account. Only provided fields are updated.

This endpoint sends each Nexset record as a JSON request body to update the watchlist identified by its ID. Only the fields present in the record are changed. For detailed information about the request body and response fields, see the Perigon API Reference.

[Rest API] Delete watchlist

Delete a watchlist by its ID.

This endpoint deletes the watchlist identified by its ID. For detailed information about the request and response fields, see the Perigon API Reference.

[Rest API] Create source group

Create a new custom source group (a curated bundle of publisher domains).

This endpoint sends each Nexset record as a JSON request body to create a new source group. The record must match the source group structure expected by the Perigon API. For detailed information about the request body and response fields, see the Perigon API Reference.

[Rest API] Delete source group

Delete a custom source group by its ID.

This endpoint deletes the source group identified by its ID. For detailed information about the request and response fields, see the Perigon API Reference.

Manual configuration

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

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

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