Table of Contents

REST API Request

The REST API Request action calls the Finago Office (24SevenOffice) REST API and retrieves data. Use this action to pull data from Finago Office into a data platform, automate periodic data syncs, and build reporting pipelines over accounting, invoicing, and contact data.

Finago Office REST API Request action showing Connection, Configuration, and exit ports for Success, Error, and Continue

Example Example
The example above shows a Flow that uses a dynamic connection to request accounts. The JSON data in the response is converted to a table, and the resulting rows are inserted into a SQL Server table.


When to use this

  • Pull chart-of-accounts, general ledger transactions, invoices, or customer/vendor data from Finago Office into a SQL Server database or data warehouse.
  • Automate a nightly or weekly sync of financial data so reporting dashboards stay current without manual exports.
  • Extract data from Finago Office as part of a larger data integration pipeline that combines multiple source systems.

How it works

  • Input: A configured HTTP request (method, URI, optional query parameters) and an authenticated Connection to the Finago Office REST API.
  • Processing: Flow authenticates against the Finago Office API using OAuth2 credentials (ClientId, ClientSecret, OrganizationId), sends the HTTP request, and handles retry logic for API throttling automatically. You do not need to manage tokens or retry cycles.
  • Output: The response from the API, either as raw JSON (HttpResponse<string>) or a custom data type you define. The action routes execution to the Success, Error, or Continue exit port depending on the result.

Exit ports

Port Fires when
Success The API returned a successful response (HTTP 2xx).
Error The API returned an error, or an exception occurred during execution.
Continue Execution continues regardless of the outcome.

Prerequisites


Properties

Name Required Description
Connection Yes The connection used to authenticate requests to the Finago Office REST API.
Dynamic connection No Overrides the static Connection with credentials stored outside the Workspace (for example, in your own database). To create a connection dynamically at runtime, use the Create Finago Office Connection action.
Configuration Yes Defines the HTTP request to make to the API. See Configuration below.
Disabled No When set to true, the action is skipped during Flow execution.
Description No Free-text notes about the action.

Returns

The return type is defined when configuring the action. It can be a custom data type or the raw JSON response from the API.

Use the built-in HttpResponse<T> type to get additional information about the response, including the HTTP status code and any errors.

Tip

For large data sets (10,000–200,000+ records), store the raw JSON response in a database or blob storage first, then use transformation tools (dbt, SQLMesh, or Azure Data Factory) to reshape the data. This avoids high memory usage from deserializing large payloads in Flow.

If you know the API returns a small number of records, you can use Get JSON DataReader to flatten the JSON to a tabular format and process the data as rows and columns — for example, by inserting directly into a SQL Server table.


Configuration

To define a request to the REST API, you can start from a template or define it manually.

Using a template

  1. Open the Configuration dialog for the action.
  2. Click New Request.
  3. Choose from the list of predefined request templates.

The template collection covers a subset of the available APIs. If you cannot find a template for the request you need, see the Finago Office REST API documentation and define the request manually.

Defining a request manually

See the Finago Office REST API documentation for available endpoints and parameters.

  1. Set the Method (GET, PUT, POST, DELETE, etc.). Most endpoints that fetch data require GET.
  2. Set the URI — the API endpoint path, for example companies/{id}. If the endpoint requires parameters (such as a company ID), insert a Flow variable using the popup that appears when the URI editor gets focus.
  3. Add optional Query Parameters. For example, when requesting transaction lines, add dateFrom and dateTo parameters with date values in ISO format.
  4. Define the Response type. The default is HttpResponse<string>, which returns the raw JSON. You can change this to a custom type, but keep in mind that deserialization allocates more memory and impacts performance for large data sets such as dimensions and general ledger queries.

Notes

  • Flow handles OAuth2 authentication and API throttling/retry automatically. You do not need to manage access tokens or implement backoff logic.
  • For large data sets, avoid deserializing into custom types directly. Store raw JSON first and transform it downstream.
  • The Finago Office REST API is versioned independently of Flow. Check the API documentation for the latest available endpoints and any breaking changes.

See also

Edit this page