Skip to main content

Better Proposals

Better Proposals is a modern document creation and management platform that enables businesses to create, send, and track professional proposals, contracts, and other business documents with advanced analytics and client engagement features.

Better Proposals icon

Power end-to-end data operations for your Better Proposals API with Nexla. Our bi-directional Better Proposals connector is purpose-built for Better Proposals, 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 Better Proposals or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Better Proposals 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 Better Proposals credential, you need to obtain an API key from your Better Proposals account. The API key is required to authenticate with the Better Proposals API.

To obtain your API key, you need to have a Better Proposals account. Once you have access to your account, you can generate an API key from your account settings. The API key is used to authenticate all API requests to the Better Proposals API. For detailed information about API key setup and authentication, refer to the Better Proposals API documentation.

Authenticate

Credentials required

FieldRequiredSecretDescription
API Key ValueYesYesAccount in order to use api key

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.

New Credential Overlay – Better Proposals

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

  2. Enter your Better Proposals API key in the API Key Value field. This is the API key you obtained from your Better Proposals account settings. The API key is sent in the Bptoken header to authenticate all API requests to the Better Proposals API.

    Keep your API key secure and do not share it publicly. The API key provides access to your Better Proposals account and should be treated as a sensitive credential.

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

Resource Type

This endpoint retrieves information for a selected resource type from your Better Proposals account. Use this endpoint when you need to access proposals, templates, document types, companies, currencies, or settings from your Better Proposals account.

  • Select the resource type you want to retrieve from the Resource Type dropdown menu. Available options include:

    • Proposal: Get all proposals (default)
    • Template: Get all templates
    • Document Types: Get all document types
    • Companies: Get all companies
    • Currencies: Get all currencies
    • Settings: Get settings

    The default value is proposal if not specified. You can also add custom resource types if needed.

  • The endpoint uses GET requests to https://api.betterproposals.io/{'{resource_type}'} where {resource_type} is the selected resource type. The endpoint URL is automatically constructed based on the resource type you select.
  • The endpoint uses incrementing page-based pagination, automatically fetching additional pages as needed using the page and per_page query parameters. The endpoint starts from page 1 and continues fetching pages until all available resources have been retrieved. By default, the endpoint retrieves up to 10 items per page.
  • The endpoint will return all resources of the selected type. The response data is extracted from the data array in the API response ($.data[*]), with each resource record processed individually.

This endpoint supports pagination through page and per_page query parameters. Nexla automatically handles pagination to retrieve all available records by incrementing the page number until no more data is returned. The endpoint uses incrementing page-based pagination (iteration.type: paging.incrementing), starting from page 1. By default, the endpoint retrieves up to 10 items per page (page.expected.rows: 10). The response data path is $.data[*], which extracts all items from the data array in the API response. You can add custom resource types if needed by entering the resource type name directly. For detailed information about available resource types, retrieving resources, and API usage, see the Better Proposals API documentation.

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

Better Proposals data sources can also be manually configured to ingest data from any valid Better Proposals 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, path to data, 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 Better Proposals 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 Better Proposals destination, and select the Send to Destination option from the menu. Select the Better Proposals connector from the list of available destination connectors, then select the credential that will be used to connect to the Better Proposals organization, and click Next; or, create a new Better Proposals 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 Better Proposals 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.

Resource Type

This endpoint creates a new resource of the selected type in your Better Proposals account. Use this endpoint when you need to create proposals, document types, or companies from your data sources.

  • Select the resource type you want to create from the Resource Type dropdown menu. Available options include:

    • proposal: Create proposal (default)
    • Create document: Create document type
    • Company: Create company

    The default value is proposal if not specified. You can also add custom resource types if needed.

  • The endpoint uses POST requests to https://api.betterproposals.io/{'{resource_type}'}/create where {resource_type} is the selected resource type. The endpoint URL is automatically constructed based on the resource type you select.
  • The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the resource data to create. The request body should follow the Better Proposals API specification for creating resources, including required fields and field names.
  • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a resource. If you need to create multiple resources, you can send multiple records, but each will be processed as a separate request.

The request body must be properly formatted JSON that matches the Better Proposals API specification for creating the selected resource type. The endpoint requires API key authentication in the Bptoken header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. You can add custom resource types if needed by entering the resource type name directly. For detailed information about creating resources, including required fields, field names, and request formats for each resource type, see the Better Proposals API documentation.

Manual configuration

Better Proposals destinations can also be manually configured to send data to any valid Better Proposals 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, and request body.

The Better Proposals API typically uses JSON format for request bodies, following the pattern https://api.betterproposals.io/{'{resource_type}'}/create for creating resources. API key authentication in the Bptoken header is handled automatically by your credential configuration, so you do not need to include it in the request headers.

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

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