Avaza

Avaza is a unified work management platform that combines project management, time tracking, expense management, and invoicing capabilities in one solution, helping teams collaborate effectively and streamline their business operations.

Power end-to-end data operations for your Avaza API with Nexla. Our bi-directional Avaza connector is purpose-built for Avaza, 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 Avaza or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Avaza 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 an Avaza credential in Nexla, you need to set up an OAuth 2.0 integration in your Avaza account and obtain the required credentials. This integration enables programmatic access to the Avaza API without requiring user interaction for each request.

OAuth 2.0 Setup

OAuth 2.0 authentication provides secure, token-based access to the Avaza API with automatic token refresh. The OAuth flow allows Nexla to access your Avaza account on your behalf. For detailed information about setting up OAuth 2.0 authentication, see the Avaza API OAuth2 documentation.

1. Access Avaza Account Settings: Sign in to your Avaza account and navigate to your account settings or developer settings.

2. Create an OAuth App: Create a new OAuth app in your Avaza account. This will generate a Client ID and Client Secret that you'll use for authentication.

3. Configure OAuth Settings: Configure your OAuth app settings, including redirect URIs and scopes. The redirect URI should match the callback URL provided by Nexla during the OAuth flow.

4. Obtain Client Credentials: Copy your Client ID and Client Secret from the OAuth app settings. These credentials are used to authenticate with the Avaza OAuth 2.0 service.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	No	Avaza Client ID
Access Scope	No	No	Avaza Access Scope
Client Secret	No	Yes	Avaza Client Secret for Token URL

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 – Avaza

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 Avaza Client ID in the Client ID field. This should be the Client ID obtained from your OAuth app in your Avaza account.

4. Enter your Avaza Client Secret in the Client Secret field. This should be the Client Secret obtained from your OAuth app in your Avaza account.

5. Optionally, enter the access scope in the Access Scope field if you need to specify custom scopes for your OAuth integration.

6. Complete the OAuth authorization flow by following the prompts to authorize Nexla to access your Avaza account. The OAuth flow will automatically handle token exchange and refresh.

   The OAuth 2.0 flow provides secure, token-based access to the Avaza API with automatic token refresh. The authorization process requires you to sign in to your Avaza account and grant permissions to Nexla. For detailed information about Avaza API authentication, see the Avaza API OAuth2 documentation.

7. 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 Avaza connector tile from the list of available connectors, then select the credential that will be used to connect to the Avaza instance, and click Next; or, create a new Avaza 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 Avaza 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.

Get Bils

This endpoint retrieves a list of bills from your Avaza account. Use this endpoint when you need to access bill information for expense tracking, accounting, or financial reporting purposes.

• This endpoint automatically retrieves all bills from your Avaza account using GET requests to https://api.avaza.com/api/Bill. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses incrementing page-based pagination with pageNumber and pageSize query parameters, automatically fetching additional pages as needed. By default, the endpoint retrieves up to 1000 bills per page (as specified by pageSize=1000), starting from page 1 (pageNumber=1).
• The endpoint will return all bills in your account. The response contains a Bills array, and each bill record includes bill details, amounts, dates, vendors, and other bill-related information.
• The response data is extracted from the Bills array in the API response ($.Bills[*]), with each bill record processed individually.

This endpoint supports pagination through pageNumber and pageSize query parameters. Nexla automatically handles pagination to retrieve all available bills by incrementing the page number until no more data is returned. The endpoint expects up to 1000 rows per page (as indicated by page.expected.rows: 1000), and requests are processed sequentially (request.parallelism.count: 1). The response structure contains a Bills array at the root level, and each bill record is extracted from this array using the JSON path $.Bills[*]. For detailed information about retrieving bills, including available fields and response structures, see the Avaza API documentation.

Get Bill Payments

This endpoint retrieves a list of bill payments from your Avaza account. Use this endpoint when you need to access payment information for bills, including payment dates, amounts, and payment methods.

• This endpoint automatically retrieves all bill payments from your Avaza account using GET requests to https://api.avaza.com/api/BillPayment. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses incrementing page-based pagination with pageNumber and pageSize query parameters, automatically fetching additional pages as needed. By default, the endpoint retrieves up to 1000 payments per page (as specified by pageSize=1000), starting from page 1 (pageNumber=1).
• The endpoint will return all bill payments in your account. The response contains a Payments array, and each payment record includes payment details, amounts, dates, and associated bill information.
• The response data is extracted from the Payments array in the API response ($.Payments[*]), with each payment record processed individually.

This endpoint supports pagination through pageNumber and pageSize query parameters. Nexla automatically handles pagination to retrieve all available bill payments by incrementing the page number until no more data is returned. The endpoint expects up to 1000 rows per page (as indicated by page.expected.rows: 1000), and requests are processed sequentially (request.parallelism.count: 1). The response structure contains a Payments array at the root level, and each payment record is extracted from this array using the JSON path $.Payments[*]. For detailed information about retrieving bill payments, including available fields and response structures, see the Avaza 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

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

Avaza API endpoints typically follow the pattern https://api.avaza.com/api/{resource}, and response data is usually found in arrays such as $.Bills[*] for bills or $.Payments[*] for bill payments. For a complete list of available Avaza API endpoints, see the Avaza API documentation.

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