TREASURYUNCLASSIFIED // EXTERNAL

Version 1.0 G-Invoicing – Pull Features or BizApps API 7/25/2022

1

G-Invoicing – Pull Features or BizApps

Description/ 

Purpose

This specification describes how to call the application programming interface 

(API) to extract Feature reference data (including Feature Flags) or Business 

Application (BizApp) reference data (including BizApp Conditions) from GInvoicing. 

• Features are used to control the availability of new software features

• Feature Flags provide the list of agencies capable of using a feature

• BizApps narrow the business purpose of GT&C agreements

• BizApp Conditions control certain attributes of a GT&C

Status Codes

Common HTTP Status Codes:

• 200 – Okay

• 400 – Bad request

• 403 – Forbidden

• 500 – Internal server error

Summary

These two REpresentational State Transfer (REST) services provide data in JavaScript Object 

Notation (JSON) format to an external agency partner. One resource is available to pull all Feature 

reference data and Feature Flags. A second service returns BizApp reference data and BizApp 

Conditions. Clients must have a certified Partner ID (see note below) and System ID, but there is no 

other authorization requirement.

There are no Federal Intragovernmental Data Standards(FIDS) for Feature or BizApp information. 

JSON constraints and sample JSON may be obtained following the OpenAPI | Swagger Editor

instructions to view Feature Service 1_0 or BizApp Service 1_0. Two examples of a Feature are 

“Batch Order Upload” and “GTC Revert”. Two examples of a BizApp are “Standard Order 

Processing” and “GSA Fleet Leasing (7600EZ)”.

More information about how Features and BizApps are employed may be found within the Feature

Management and BizApp presentation on the G-Invoicing website.

Note: Only an authorized Partner ID (and accompanying System ID) will elicit a response from GInvoicing. See the System Integration Guide or G-Invoicing Playbook for information on how to 

partner with G-Invoicing, or contact us at IGT@fiscal.treasury.gov
TREASURYUNCLASSIFIED // EXTERNAL

Version 1.0 G-Invoicing – Pull Features or BizApps API 7/25/2022

2

Entity Relationships

The data structures for Features and BizApps intersect. Two basic rules are that all BizApps are 

Features, but not every Feature is a BizApp. The connector between these two data sets is the 

Feature Code contained in the BizApp data, which points to a Feature. Agency readiness to use a 

particular BizApp on a GT&C may be viewed through the Requesting and Servicing Agency 

Account IDs (aka, Feature Flags) associated with the Feature. BizApp Type (e.g., STD, EZ) dictates 

the type of documents allowed under a GT&C.

Another important relationship is from Agency Account to the General Terms and Conditions 

(GT&C) agreement (not depicted above). The JSON body of a Pull GT&C response contains the 

Agency Account IDs for the Requesting and Servicing partners. Knowing these two IDs allows for 

G-Invoicing and agency systems to determine which Features are available for use under a specific

GT&C agreement.
TREASURYUNCLASSIFIED // EXTERNAL

Version 1.0 G-Invoicing – Pull Features or BizApps API 7/25/2022

3

Resources

1. Get Feature Flags

This endpoint allows systems to extract all reference data describing G-Invoicing’s Features, along 

with agency Feature Flags indicating agency availability to use each Feature as a requesting partner 

and (separately) as a servicing partner.

The response contains all active Features, and each feature is available to 0:M (zero-to-many) 

agencies, separately on the requesting side and on the servicing side. The JSON for Feature Service

1_0 is structured as such.

HTTP method: GET

Path: /ginv/services/v1_0/feature/feature-flags/

Request:

Parameters

Name: systemId

Description: Identifies the system that is exchanging data with G-Invoicing 

In: header

Type: string [100] 

Required: true 

Example 

GET /ginv/services/v1_0/feature/feature-flags/ 

Host: ws.igt.fiscal.treasury.gov

Accept: application/json 

Accept Encoding: gzip, deflate 

Connection: Keep-Alive

2. Get BizApps

This endpoint allows systems to extract all reference data describing G-Invoicing’s Business 

Applications, along with BizApp Conditions which control certain attributes under a GT&C (e.g., 

maximum value of an EZ_10K invoice must be less than or equal to $10,000).

The response contains all active BizApps and all active BizApp Conditions. The JSON for BizApp

Service 1_0 is structured as such.

HTTP method: GET

Path: /ginv/services/v1_0/reference/bizapp/ 

Request:

Parameters
TREASURYUNCLASSIFIED // EXTERNAL

Version 1.0 G-Invoicing – Pull Features or BizApps API 7/25/2022

4

Name: systemId

Description: Identifies the system that is exchanging data with G-Invoicing 

In: header

Type: string [100] 

Required: true 

Example 

GET /ginv/services/v1_0/reference/bizapps/ 

Host: ws.igt.fiscal.treasury.gov

Accept: application/json 

Accept Encoding: gzip, deflate 

Connection: Keep-Alive

Revision History

Doc. 

Vers.

API

Vers.

Date of 

Change

G-Inv Rel. Change/Revision Description Page/Section 

Affected

0.1 1_0 7/22/22 4.6 (Feature),

5.0 (BizApp)

Initial draftfor internalreview. All

1.0 1_0 7/25/22 4.6 (Feature),

5.0 (BizApp)

Corrected path/resource names. Published to website. Resource 1+2

End of Specification