Skip to main content

Vantage

Vantage is a cloud cost intelligence and FinOps platform that provides API access to cloud provider data, pricing, cost reports, forecasts, and financial commitments. Its REST API lets you programmatically read cost analytics and manage resources such as cost reports, cost alerts, workspaces, virtual tags, and managed accounts.

Vantage icon

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

To obtain your Vantage API access token, follow these steps:

  1. Sign in to your Vantage account at console.vantage.sh.

  2. Open the Settings screen and select API Access Tokens from the left navigation menu.

  3. Enter a name for the new token, choose a team if applicable, and select the Read and/or Write scope depending on how you intend to use the connector. Read scope is sufficient to ingest data as a source; Write scope is required to create or update resources as a destination.

  4. Click Create, then click Show to reveal your token and copy it. Store the token securely, as it grants access to your Vantage cost data.

Owner-level users can also create service tokens, which are associated with the account rather than an individual user. For more detail on token types, scopes, and authentication, see the Vantage API documentation.

Authenticate

Credentials required

Authenticate to Vantage API using a Bearer token passed in the Authorization header.

FieldRequiredSecretDescription
API KeyYesYesYour Vantage API key for authentication.
Base URLYesNoThe base URL for the Vantage API.

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 Vantage API access token in the API Key field. This token is sent as a bearer token in the Authorization header for all API requests and must be kept confidential.

  4. Enter the API base URL in the Base URL field. In most cases this is https://api.vantage.sh.

    If your API access token is compromised, revoke it in the Vantage Settings > API Access Tokens screen and generate a new one. The token grants access to your Vantage cost data and should be treated as sensitive information.

    For detailed information about authentication, scopes, and available endpoints, see the Vantage API documentation.

  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/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 Vantage connector tile, then select the credential that will be used to connect to Vantage, and click Next; or, create a new Vantage 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 Vantage 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] List Providers

Returns a list of all available cloud providers supported by Vantage.

This endpoint returns the cloud providers that Vantage supports. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] List Services

Returns a list of all available cloud services that can be tracked and analyzed by Vantage.

This endpoint returns the cloud services Vantage can track and analyze. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] List Products

Returns a list of all available cloud products and services across supported providers.

This endpoint returns cloud products and services across supported providers. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] List Reports

Returns a list of all available cost and usage reports configured in the Vantage account.

This endpoint returns the cost and usage reports configured in your Vantage account. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] List Access Grants

Returns a paginated list of all access grants in the account.

This endpoint returns the access grants defined in your Vantage account. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] Get all cost alerts

Retrieves all cost alerts in the account.

This endpoint returns every cost alert configured in your Vantage account, including thresholds and notification settings. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] Get All Cost Reports

Returns a paginated list of cost reports, optionally filtered by folder.

  • This endpoint accepts an optional Folder Token parameter to return only the cost reports contained in a specific folder.

This endpoint returns cost reports in your Vantage account. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure and filter parameters, see the Vantage API documentation.

[Rest API] Get Forecasted Costs for Cost Report

Returns paginated forecasted costs for a cost report, optionally filtered by date range, provider, or service.

  • This endpoint accepts a Cost Report Token and optional Start Date, End Date, Provider, and Service parameters to scope the forecast.

This endpoint returns forecasted costs for the specified cost report. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure and filter parameters, see the Vantage API documentation.

[Rest API] List Financial Commitments

Returns a paginated list of all financial commitments across resources.

This endpoint returns the financial commitments tracked across your resources in Vantage. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] Get all invoices

Retrieves a paginated list of all invoices with optional filtering by managed account.

  • This endpoint accepts an optional Managed Account Token parameter to return only the invoices for a specific managed account.

This endpoint returns invoices in your Vantage account. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure and filter parameters, see the Vantage API documentation.

[Rest API] Get invoice by token

Retrieves the details of a specific invoice by its token.

  • This endpoint requires an Invoice Token parameter that identifies the invoice to retrieve.

This endpoint returns the details of a single invoice. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] List managed accounts

Retrieves a paginated list of all managed accounts.

This endpoint returns the managed accounts in your Vantage account. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] Get authenticated user info

Returns information about the currently authenticated user.

This endpoint returns details about the user associated with the API access token used for the request. For detailed information about the response structure, see the Vantage API documentation.

[Rest API] Get Products

Returns a paginated list of all products, optionally filtered by provider, service, or name.

  • This endpoint accepts optional Provider ID, Service ID, and Product Name parameters to narrow the results.

This endpoint returns products tracked by Vantage. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure and filter parameters, see the Vantage API documentation.

[Rest API] List Workspaces

Returns a paginated list of all workspaces in the account.

This endpoint returns the workspaces in your Vantage account. Nexla automatically paginates the request to retrieve all available records. For detailed information about the response structure, see the Vantage 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

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

Creates a new cost alert with threshold and notification settings.

  • Configure the cost alert parameters such as Title, Interval, Threshold, Unit type, Workspace token, Report tokens, and notification targets like Email recipients, Slack channels, and Teams channels.

Each record from your Nexset is sent as a separate API request to create a cost alert. The record must include the fields required by the Vantage API. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Create Cost Report

Creates a new cost report with the specified configuration and filters.

  • Configure the cost report parameters such as Title, Workspace Token, Groupings, Filter, Saved Filter Tokens, Folder Token, Start Date, End Date, Date Interval, Chart Type, and related settings.

Each record from your Nexset is sent as a separate API request to create a cost report. The record must include the fields required by the Vantage API. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Create invoice

Creates a new invoice for a specified billing period and account.

Each record from your Nexset is sent as a separate API request to create an invoice. The record must include the fields required by the Vantage API. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Create managed account

Creates a new managed account with the specified details.

  • Configure the managed account parameters such as Account Name, Contact Email, Access Credential Tokens, Billing Rule Tokens, and Email Domain.

Each record from your Nexset is sent as a separate API request to create a managed account. The record must include the fields required by the Vantage API. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Create network flow report

Creates a new network flow report with specified filters, date range, and grouping options.

  • Configure the network flow report parameters such as Workspace Token, Report Title, Filter, Start Date, End Date, Date Interval, Groupings, Flow Direction, and Flow Weight.

Each record from your Nexset is sent as a separate API request to create a network flow report. The record must include the fields required by the Vantage API. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Create virtual tag config

Creates a new virtual tag configuration for organizing and categorizing cloud costs.

  • Configure the virtual tag parameters such as Key, Overridable, Backfill Until, Collapsed Tag Keys, and Values.

Each record from your Nexset is sent as a separate API request to create a virtual tag configuration. The record must include the fields required by the Vantage API. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Update virtual tag config

Updates an existing virtual tag configuration with new mapping rules and settings.

  • Provide the Token that identifies the virtual tag configuration to update, along with the fields to change such as Key, Overridable, Backfill Until, Collapsed Tag Keys, and Values.

Each record from your Nexset is sent as a separate API request to update a virtual tag configuration. The record must include the token of the configuration to update along with the fields to change. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Create Workspace

Creates a new workspace with the specified name and optional currency conversion settings.

Each record from your Nexset is sent as a separate API request to create a workspace. The record must include the fields required by the Vantage API. For detailed information about request body formats and available fields, see the Vantage API documentation.

[Rest API] Update Workspace

Updates an existing workspace with new name, currency, and conversion settings.

  • Provide the Workspace Token that identifies the workspace to update, along with the fields to change.

Each record from your Nexset is sent as a separate API request to update a workspace. The record must include the workspace token along with the fields to change. For detailed information about request body formats and available fields, see the Vantage API documentation.

Manual configuration

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

Vantage APIs expect JSON format for write operations. For update operations, include the token of the resource to be updated as required by the endpoint.

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

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