Master
Master Service APIs
APIs to create, update or search masters.
funds
Unique id for a tenant.
comma seperated list of Ids
name is the name of the fund . Example :Municipal Fund,Capital Fund. Also name is unique.
code is a unique number given to each fund . ULB may refer this for the short name
identifier of the Fund
parent adding a parent will create the fund as a sub-fund (child) of a fund already created (parent fund).
active is a boolean value which says whether fund is in use or not . If Fund is active, then accounting of transactions under the fund is enabled. If Fund becomes inactive, and no transactions can be accounted under the Fund.
isParent is updated internally so that system can identify whether the fund is parent or child. Only child which is not parent for any other fund can only participate in transaction .
level identifies what is the level of the fund in the tree structure. Top most parent will have level 0 and its child will have level as 1
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Fund retrieved Successfully
Invalid Input
financialyears
Unique id for a tenant.
comma seperated list of Ids
finYearRange is the name of the Financial Year . for example for accounting year 2017 and 2018 it may be named 2017-18
startingDate is the date on which Accounting Year starts. Usually it is 1st April of that year.
endingDate is the date on which Financial Year ends. Usually it is 31st march of next year
active says whether Financial Year is active or not . Over a period system will have number of Financial years. Reports ,searches,transactions will need to display this.If the active value is true then Financial Year is listed, if value is false it wont be listed
isActiveForPosting refers whether posting allowed for the Financial Year or not . This value will be true for current year and few previous year for which data entry will be happening. Once the account is closed this value is set to false . All transactions will happen if and only if isActiveForPosting is true
isClosed refers whether the account is closed or not . Once the account is closed and balance is transferred this value is set to false if the account is closed no transaction can happen on that financial year.
transferClosingBalance informs whether While closing account balance is transferred or not .
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
FinancialYear retrieved Successfully
Invalid Input
Create new financialyears
Unique id for a tenant.
Contract class for web request. Array of FinancialYear items are used in case of create or update
FinancialYear created Successfully
Invalid Input
Update any of the financialyears
Unique id for a tenant.
Contract class for web request. Array of FinancialYear items are used in case of create or update
FinancialYear updated Successfully
Invalid Input
fiscalperiods
Unique id for a tenant.
comma seperated list of Ids
name of the FiscalPeriod
financial year of the FiscalPeriod
startingDate is the date on which period starts.
endingDate is the date on which period ends.
active says whether fiscal period is active or not . Over a period system will have number of fiscal period. Reports ,searches,transactions will need to display this.If the active value is true then fiscal period is listed, if value is false it wont be listed
isActiveForPosting refers whether posting allowed for the fiscal period or not . This value will be true for current year and few previous year for which data entry will be happening. Once the account is closed this value is set to false . All transactions will happen if and only if isActiveForPosting is true
isClosed refers whether the account is closed or not . Once the account is closed and balance is transferred this value is set to false if the account is closed no transaction can happen on that fiscal period.
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
FiscalPeriod retrieved Successfully
Invalid Input
Create new fiscalperiods
Unique id for a tenant.
Contract class for web request. Array of FiscalPeriod items are used in case of create or update
FiscalPeriod created Successfully
Invalid Input
Update any of the fiscalperiods
Unique id for a tenant.
Contract class for web request. Array of FiscalPeriod items are used in case of create or update
FiscalPeriod updated Successfully
Invalid Input
functions
Unique id for a tenant.
comma seperated list of Ids
name is the name of the function .
code is a unique number given to each function . ULBs may refer this for the short name.
level identifies what is the level of the function in the tree structure. Top most parent will have level 0 and its child will have level as 1
active is a boolean value which says whether function is in use or not . If Function is active, then accounting of transactions under the Function is enabled. If Function becomes inactive, and no transactions can be accounted under the Function. Only leaf function can be used in transaction ie function which is not parent to any other function
parent id of the Function
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Function retrieved Successfully
Invalid Input
Update any of the functions
Unique id for a tenant.
Contract class for web request. Array of Function items are used in case of create or update
Function updated Successfully
Invalid Input
functionaries
Unique id for a tenant.
comma seperated list of Ids
code is uniue identifier and ULB may refer this for short name.
name is the name of the functionary
active states whether the functionary is active or not . Only active functionaries will be used in transaction
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Functionary retrieved Successfully
Invalid Input
Create new functionaries
Unique id for a tenant.
Contract class for web request. Array of Functionary items are used in case of create or update
Functionary created Successfully
Invalid Input
Update any of the functionaries
Unique id for a tenant.
Contract class for web request. Array of Functionary items are used in case of create or update
Functionary updated Successfully
Invalid Input
fundsources
Unique id for a tenant.
comma seperated list of Ids
code of the Fundsource
name of the Fundsource
type of the Fundsource
parent of the Fundsource
llevel of the Fundsource
Whether Fundsource is Active or not. If the value is TRUE, then Fundsource is active,If the value is FALSE then Fundsource is inactive,Default value is TRUE
is parent of the Fundsource
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Fundsource retrieved Successfully
Invalid Input
Create new fundsources
Unique id for a tenant.
Contract class for web request. Array of Fundsource items are used in case of create or update
Fundsource created Successfully
Invalid Input
Update any of the fundsources
Unique id for a tenant.
Contract class for web request. Array of Fundsource items are used in case of create or update
Fundsource updated Successfully
Invalid Input
schemes
Unique id for a tenant.
comma seperated list of Ids
fund of the Scheme
code of the Scheme
name of the Scheme
valid from of the Scheme
valid to of the Scheme
Whether Scheme is Active or not. If the value is TRUE, then Scheme is active,If the value is FALSE then Scheme is inactive,Default value is TRUE
description of the Scheme
boundary of the Scheme
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Scheme retrieved Successfully
Invalid Input
Update any of the schemes
Unique id for a tenant.
Contract class for web request. Array of Scheme items are used in case of create or update
Scheme updated Successfully
Invalid Input
banks
Unique id for a tenant.
comma seperated list of Ids
code is the code of the bank
name is the Bank Name .
description more detailed description of the bank
active states whether the bank is active in the system or not .
type of the Bank
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Bank retrieved Successfully
Invalid Input
bankbranches
Unique id for a tenant.
comma seperated list of Ids
bank is the bank of the branch
code is the branch code
name is the branch name
address2 is the secondary address of the branch
address2 of the BankBranch
city is the name of the bank branches city
state is the name of the state
pincode is the pincode of the branch
phone is the phone number of the branch
fax is the fax number of the branch
contactPerson is the name of the person in contact
active states whether branch is active. i.e is usable by the system or not if not active it cannot be used
description is the more detailed description of the branch
micr is the micr code of the bank branch
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
BankBranch retrieved Successfully
Invalid Input
Create new bankbranches
Unique id for a tenant.
Contract class for web request. Array of BankBranch items are used in case of create or update
BankBranch created Successfully
Invalid Input
Update any of the bankbranches
Unique id for a tenant.
Contract class for web request. Array of BankBranch items are used in case of create or update
BankBranch updated Successfully
Invalid Input
bankaccounts
Unique id for a tenant.
comma seperated list of Ids
bank branch of the BankAccount
chart of account of the BankAccount
fund of the BankAccount
account number of the BankAccount
account type of the BankAccount
description of the BankAccount
Whether BankAccount is Active or not. If the value is TRUE, then BankAccount is active,If the value is FALSE then BankAccount is inactive,Default value is TRUE
pay to of the BankAccount
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
BankAccount retrieved Successfully
Invalid Input
Create new bankaccounts
Unique id for a tenant.
Contract class for web request. Array of BankAccount items are used in case of create or update
BankAccount created Successfully
Invalid Input
Update any of the bankaccounts
Unique id for a tenant.
Contract class for web request. Array of BankAccount items are used in case of create or update
BankAccount updated Successfully
Invalid Input
subschemes
Unique id for a tenant.
comma seperated list of Ids
scheme of the SubScheme
code of the SubScheme
name of the SubScheme
valid from of the SubScheme
valid to of the SubScheme
Whether SubScheme is Active or not. If the value is TRUE, then SubScheme is active,If the value is FALSE then SubScheme is inactive,Default value is TRUE
department id of the SubScheme
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
SubScheme retrieved Successfully
Invalid Input
Create new subschemes
Unique id for a tenant.
Contract class for web request. Array of SubScheme items are used in case of create or update
SubScheme created Successfully
Invalid Input
Update any of the subschemes
Unique id for a tenant.
Contract class for web request. Array of SubScheme items are used in case of create or update
SubScheme updated Successfully
Invalid Input
suppliers
Unique id for a tenant.
comma seperated list of Ids
code of the Supplier
name of the Supplier
address of the Supplier
mobile of the Supplier
email of the Supplier
description of the Supplier
Whether Supplier is Active or not. If the value is TRUE, then Supplier is active,If the value is FALSE then Supplier is inactive,Default value is TRUE
pan no of the Supplier
tin no of the Supplier
registation no of the Supplier
bank account of the Supplier
ifsc code of the Supplier
bank of the Supplier
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
Supplier retrieved Successfully
Invalid Input
Update any of the suppliers
Unique id for a tenant.
Contract class for web request. Array of Supplier items are used in case of create or update
Supplier updated Successfully
Invalid Input
accountdetailtypes
Unique id for a tenant.
comma seperated list of Ids
name of the AccountDetailType
description of the AccountDetailType
table name of the AccountDetailType
Whether AccountDetailType is Active or not. If the value is TRUE, then AccountDetailType is active,If the value is FALSE then AccountDetailType is inactive,Default value is TRUE
fully qualified name of the AccountDetailType
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
AccountDetailType retrieved Successfully
Invalid Input
Create new accountdetailtypes
Unique id for a tenant.
Contract class for web request. Array of AccountDetailType items are used in case of create or update
AccountDetailType created Successfully
Invalid Input
Update any of the accountdetailtypes
Unique id for a tenant.
Contract class for web request. Array of AccountDetailType items are used in case of create or update
AccountDetailType updated Successfully
Invalid Input
accountdetailkeys
Unique id for a tenant.
comma seperated list of Ids
key of the AccountDetailKey
account detail type of the AccountDetailKey
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
AccountDetailKey retrieved Successfully
Invalid Input
Create new accountdetailkeys
Unique id for a tenant.
Contract class for web request. Array of AccountDetailKey items are used in case of create or update
AccountDetailKey created Successfully
Invalid Input
Update any of the accountdetailkeys
Unique id for a tenant.
Contract class for web request. Array of AccountDetailKey items are used in case of create or update
AccountDetailKey updated Successfully
Invalid Input
accountentities
Unique id for a tenant.
comma seperated list of Ids
account detail type of the AccountEntity
code of the AccountEntity
name of the AccountEntity
Whether AccountEntity is Active or not. If the value is TRUE, then AccountEntity is active,If the value is FALSE then AccountEntity is inactive,Default value is TRUE
description of the AccountEntity
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
AccountEntity retrieved Successfully
Invalid Input
Create new accountentities
Unique id for a tenant.
Contract class for web request. Array of AccountEntity items are used in case of create or update
AccountEntity created Successfully
Invalid Input
Update any of the accountentities
Unique id for a tenant.
Contract class for web request. Array of AccountEntity items are used in case of create or update
AccountEntity updated Successfully
Invalid Input
accountcodepurposes
Unique id for a tenant.
comma seperated list of Ids
name of the AccountCodePurpose
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
AccountCodePurpose retrieved Successfully
Invalid Input
Create new accountcodepurposes
Unique id for a tenant.
Contract class for web request. Array of AccountCodePurpose items are used in case of create or update
AccountCodePurpose created Successfully
Invalid Input
Update any of the accountcodepurposes
Unique id for a tenant.
Contract class for web request. Array of AccountCodePurpose items are used in case of create or update
AccountCodePurpose updated Successfully
Invalid Input
chartofaccounts
Unique id for a tenant.
comma seperated list of Ids
glcode is the Account Code or Account Head in Accounting terms.It may be Major head,Minor head or Detailed head.It is numeric examples are 1,110,1101,1101001,2,210,21000,210010
name is the name of the account code . for example 110 glcode has the name "Tax Revenue"
accountCodePurpose is the mapped AccountCodePurpose . This mapping can happen at any level say Major,minor or detailed. When Account code is searched 1. If mapped at major code then it lists major and all other codes under that major code 2. If mapped at minor code then it list minor code and all other codes under that minor code 3. If mapped at detailed code then it lists only that code
description is the more detailed description about the account code
isActiveForPosting true will be considered for transactions. All major,minor codes will be false and only detailed code will be true . Further any account code can be disabled for transaction by making this field false
parentId is the id of other account code in the chart of account .Chart of account is created in tree structure. Any code can have other code as parent . All minor code will have manjor code as parent . All detailed code will have minor code as parent only leaf account code that is which is not parent for any account code will used for transactions.
type is a single character representation of account code type I: Income E: Expenditure L: Liability A: Asset Account code for all I start with 1 Account code for all E start with 2 Account code for all L start with 3 Account code for all A start with 4
classification is internal to the system. This tells whether the code is Major ,Minor,Subminor or detailed. Major code classification value is 1 Minor code is 2 Subminor code is 3 Detailed code is 4. Only classification 4 and is activeforposting=true will be used in transactions. Reports can be generated at any level.
functionRequired field specifies while transacting with this accountcode is the function is mandatory or not . For any account code this field is set to true then all transactions expect a fun=ction code to be passed along with account code
budgetCheckRequired field specifies whether budgeting check required for this account code. Apart from global Budgetcheck configuration this is where glcode wise budget check decision is made.
major code of the ChartOfAccount
is sub ledger of the ChartOfAccount
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
ChartOfAccount retrieved Successfully
Invalid Input
Create new chartofaccounts
Unique id for a tenant.
Contract class for web request. Array of ChartOfAccount items are used in case of create or update
ChartOfAccount created Successfully
Invalid Input
Update any of the chartofaccounts
Unique id for a tenant.
Contract class for web request. Array of ChartOfAccount items are used in case of create or update
ChartOfAccount updated Successfully
Invalid Input
chartofaccountdetails
Unique id for a tenant.
comma seperated list of Ids
chart of account of the ChartOfAccountDetail
account detail type of the ChartOfAccountDetail
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
ChartOfAccountDetail retrieved Successfully
Invalid Input
Create new chartofaccountdetails
Unique id for a tenant.
Contract class for web request. Array of ChartOfAccountDetail items are used in case of create or update
ChartOfAccountDetail created Successfully
Invalid Input
Update any of the chartofaccountdetails
Unique id for a tenant.
Contract class for web request. Array of ChartOfAccountDetail items are used in case of create or update
ChartOfAccountDetail updated Successfully
Invalid Input
budgetgroups
Unique id for a tenant.
comma seperated list of Ids
name of the BudgetGroup
description of the BudgetGroup
major code of the BudgetGroup
max code of the BudgetGroup
min code of the BudgetGroup
Whether BudgetGroup is Active or not. If the value is TRUE, then BudgetGroup is active,If the value is FALSE then BudgetGroup is inactive,Default value is TRUE
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
BudgetGroup retrieved Successfully
Invalid Input
Create new budgetgroups
Unique id for a tenant.
Contract class for web request. Array of BudgetGroup items are used in case of create or update
BudgetGroup created Successfully
Invalid Input
Update any of the budgetgroups
Unique id for a tenant.
Contract class for web request. Array of BudgetGroup items are used in case of create or update
BudgetGroup updated Successfully
Invalid Input
financialstatuses
Unique id for a tenant.
comma seperated list of Ids
module type of the FinancialStatus
code of the FinancialStatus
name of the FinancialStatus
description of the FinancialStatus
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
FinancialStatus retrieved Successfully
Invalid Input
Create new financialstatuses
Unique id for a tenant.
Contract class for web request. Array of FinancialStatus items are used in case of create or update
FinancialStatus created Successfully
Invalid Input
Update any of the financialstatuses
Unique id for a tenant.
Contract class for web request. Array of FinancialStatus items are used in case of create or update
FinancialStatus updated Successfully
Invalid Input
financialconfigurations
Unique id for a tenant.
comma seperated list of Ids
name of the FinancialConfiguration
description of the FinancialConfiguration
module of the FinancialConfiguration
pageSize
offset
This takes any field from the Object seperated by comma and asc,desc keywords.
example name asc,code desc or name,code or name,code desc
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
unique API ID
API version - for HTTP based request this will be same as used in path
time in epoch
API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc
Device ID from which the API is called
API key (API key provided to the caller in case of server to server communication)
Unique request message id from the caller
UserId of the user calling
//session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token
FinancialConfiguration retrieved Successfully
Invalid Input
Create new financialconfigurations
Unique id for a tenant.
Contract class for web request. Array of FinancialConfiguration items are used in case of create or update
FinancialConfiguration created Successfully
Invalid Input
Update any of the financialconfigurations
Unique id for a tenant.
Contract class for web request. Array of FinancialConfiguration items are used in case of create or update
FinancialConfiguration updated Successfully
Invalid Input
Last updated
Was this helpful?