Persona
Persona is an identity verification platform for KYC, document verification, and fraud prevention. The Persona API provides programmatic access to accounts, inquiries, cases, and connections so you can manage verified identity data and automate compliance workflows. Nexla connects to the Persona REST API to ingest identity and account data as a source or to send updates and actions to Persona as a destination.

Power end-to-end data operations for your Persona API with Nexla. Our bi-directional Persona connector is purpose-built for Persona, 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 Persona or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Persona 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 Persona credential, you need to obtain an API key from your Persona account. Persona uses HTTP Bearer authentication, and the API key is sent in the Authorization header as Bearer <API_KEY> on every request over HTTPS.
To obtain your Persona API key, follow these steps:
-
Sign in to your Persona Dashboard at app.withpersona.com.
-
Navigate to API > API Keys to view the API keys for your organization.
-
Each environment (for example, sandbox and production) has its own API key. Select or create the key for the environment you intend to use with Nexla.
-
Click Create API key, enter a name for the key, and click Create to generate a new key.
-
Optionally, configure the key's permissions under API > API Keys > Edit > Permissions to limit read or write access to specific API resources.
-
Copy the generated API key and store it securely. Your API key carries many privileges, so keep it confidential and do not expose it in publicly accessible areas such as source control or client-side code.
For detailed information about authentication, API keys, and available endpoints, see the Persona API Documentation.
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
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter your Persona API key in the API Key Value field. This value is sent as a Bearer token in the
Authorizationheader to authenticate all requests to the Persona API and must be kept confidential.If your API key is compromised, revoke it in the Persona Dashboard under API > API Keys and generate a new one. API keys carry many privileges and should be treated as sensitive information.
For detailed information about authentication, API keys, and available endpoints, see the Persona 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 Persona connector tile, then select the credential that will be used to connect to Persona, and click Next; or, create a new Persona 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 Persona 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
Persona data sources can also be manually configured to ingest data from any valid Persona 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 Persona 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 Persona destination, and select the Send to Destination option from the menu. Select the Persona connector from the list of available destination connectors, then select the credential that will be used to connect to Persona, and click Next; or, create a new Persona 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 Persona 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.
Manual configuration
Persona destinations can also be manually configured to send data to any valid Persona 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.
Persona APIs typically expect JSON format for most operations. For update 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 Persona endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Persona endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.