Brightflag

Brightflag is a legal spend management and matter management platform for corporate legal teams. This connector pulls legal spend data from Brightflag through its REST API, including invoice summary records and the law-firm vendors configured in your Brightflag environment.

Power end-to-end data operations for your Brightflag API with Nexla. Our bi-directional Brightflag connector is purpose-built for Brightflag, 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 Brightflag or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Brightflag 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 Brightflag credential, you need an OAuth2 client ID and client secret for your Brightflag environment, along with your Brightflag instance URL. Brightflag authenticates API requests with the OAuth2 client credentials flow: your client ID and client secret are exchanged for a bearer access token at the /oauth/token endpoint, and that token is then sent as a Bearer token on all API calls.

To obtain your Brightflag API credentials, follow these steps:

1. Identify your Brightflag instance URL. This is the base URL of your Brightflag environment (for example, https://enterprise.brightflag.com) and is region-specific. If you are unsure of your instance URL, confirm it with your Brightflag administrator.

2. Request API access from Brightflag Support by contacting your account team or emailing support@brightflag.com. Brightflag issues the OAuth2 client ID and client secret directly; they are not self-generated from the application UI.

3. Store the client ID and client secret securely. The client secret is sensitive and should be treated like a password — never share it. If it is compromised, contact Brightflag Support to have it rotated.

For more details, see the Brightflag API portal.

Authenticate

Credentials required

Field	Required	Secret	Description
Brightflag Instance URL	Yes	No	The base URL of your Brightflag environment, e.g. https://enterprise.brightflag.com (region-specific, provided by your Brightflag admin).
Client ID	Yes	No	OAuth2 client ID issued by Brightflag support for API access.
Client Secret	Yes	Yes	OAuth2 client secret issued by Brightflag support for API access.

Create a credential in Nexla

1. After selecting the data source 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 Brightflag environment base URL in the Brightflag Instance URL field (for example, https://enterprise.brightflag.com). This URL is used both to exchange your credentials for an access token and as the base for all API requests.

4. Enter the Client ID and Client Secret issued to you by Brightflag support. Nexla uses these to obtain a bearer access token from the /oauth/token endpoint, which is then sent on all Brightflag API calls.

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

Retrieves invoice summary records from Brightflag (invoice, PO, and gross-total data), optionally filterable by invoiceNumber, vendorRef, matterRef, and status-change date range.

• This endpoint fetches data from the /api/v1/invoice-summary endpoint of your Brightflag instance and returns the response as JSON.

[Rest API] Vendors

Retrieves all law firm vendors configured in Brightflag, including vendor reference, name, contact email, and preferred-counsel flag.

• This endpoint fetches data from the /api/v1/vendors endpoint of your Brightflag instance and returns the response as JSON.

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

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