CRiskCo's API is organized around REST. Accounts have test mode and live mode API keys. There is no "switch" for changing between modes, use the appropriate key to perform a live or test transaction. Requests made with test mode credentials incur no cost. JSON is returned by all API responses, including errors. Be sure to subscribe to CRiskCo's API mailing list at api@criskco.com, to receive information on new additions and changes to CRiskCo's API libraries.

This document outlines the CRiskCo programmatic interface (API) for Credit providers who use CRiskCo@Approve or CRiskCo@Gov platform to onboard applicants and do on-going monitoring. Using the API, the credit providers can access financial data (including accounting information), analytics, and CRiskCo Credit reports. CRiskCo's API libraries are documented in different documents. Each document provides a set of API calls per topic or set of data elements. Be sure to explore CRiskCo's libraries to get a full picture of CRiskCo's available data.

Jargon

For ease of understanding, the following jargon will be used throughout the document:

  1. Credit Provider - refers to the entity/app that is calling the API.
  2. Applicant - refers to the business applicant who applies for credit from the Credit Provider. This is normally a business that is signed up with the Credit Provider and applies for credit as a loan, Insurance, Grant or line of credit.
  3. Customer - refers to a business entity that is the customer of the Applicant. A Customer may be an Applicant too in a different session.

At a glance

The flow to receive an applicant credit and financial information from the API:

  1. Applicant applies online for credit and is referred to the dedicated white label landing page URL provided by CRiskCo. Applicant will go through the application process, with the last step is choosing an accounting system and authorize CRiskCo access through the accounting system API.
  2. CRiskCo backend will load the Applicant's accounting information from the accounting system and prepare a full credit report and summarize the financial information to be transmitted over the API.
  3. Once this process completes, Applicant will be redirected to the resumeUrl (provided by the Credit Provider upon registration) with an parameter that will be used to reference Applicant in future API calls as described in this document.
  4. Credit Provider will use the to make calls to the CRiskCo API.

Get your API Keys

Developer Registration

To start developing, register with CRiskCo to receive access to your own Sandbox. Register HERE to immediately get your credentials.

After your register, you will be provided access to development API tokens and can start making calls to the API.

Tokens Provided:

  1. apiId - Unique ID assigned for each Credit Provider by CRiskCo.
  2. apiKey - Unique token used to identify the Credit Provider during API calls.

Authentication

Request Format

Requests must include the following headers:

  1. apiId
  2. apiKey
  3. Content-Type: application/JSON

If request parameters are required in a request, the parameters must be sent in the request body and in JSON format, according to the endpoint definition.

All API responses are in JSON format.

GET GetApplicants
https://service.criskco.com/apiservice.svc/get-applicants

The endpoint will return the list of applicants which are registered and authorized the Credit Provider to receive access to their credit and financial information.

The applicantId is used to identify a particular applicant when query the CRiskCo API.

Two examples are provided:
1. List of all applicants
2. Query by taxId parameter

Onboarding Status

Below is an description of the onboarding statuses

Onboarding StatusDescription
AvailableThe applicant has connected to CRiskCo and the data has been processed
ProcessingThe applicant has connected to CRiskCo, but the data is currently being processed
NotConnectedThe applicant has not connected with CRiskCo

HEADERS

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Content-Type
application/json

None

PARAMS

refApplicantId

Optional: Identifier as provided by the Credit Provider when referring the Applicant

taxId

Optional: State tax id or other formal identification id

onboardingStatus

Optional: Upon 'true', the onboarding status will be included in the API Response. Default: 'false'

fullResponse
None

Optional: Upon 'true', the full dataset of this company will be returned. Default: 'false'

Example Request
                                                
GET https://service.criskco.com/apiservice.svc/get-applicants?onboardingStatus=true
                                            
Example Response
200 - OK
                                                
GET https://service.criskco.com/apiservice.svc/get-applicants?taxId=ABC123456&fullResponse=true&onboardingStatus=true
                                            
Example Response
200 - OK
                                                
GET https://service.criskco.com/apiservice.svc/get-applicants?taxId=
                                            
Example Response
None - None
GET SAT - RFC Validation
https://service.criskco.com/apiservice.svc/ValidateRFC?rfc=GAPXXXXXXXXX&name=GAP&postal=12345

Use the SAT - RFC Validation endpoint to validate a company as registered at the Mexican Fiscal Authority (SAT).

It can be validated by two options:

  1. RFC only
  2. RFC +Name of the company +Postal Code of the company as registered.

The response will return if the request is successful or not, 3 optional boolean values and the response message from SAT (as you can see below in the example):

  1. Success - Is the request is successful or not
  2. ValidRFC - The RFC is valid or not
  3. ValidName (if requested) - The Company Name is valid or not
  4. ValidPostal (if requested) - The Postal Code is valid or not
  5. message - The exact message from SAT

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Accept-Encoding
gzip, deflate

None

PARAMS

rfc
GAPXXXXXXXXX

None

name
GAP

None

postal
12345

None

Example Request
                                                
GET https://service.criskco.com/apiservice.svc/ValidateRFC?rfc=GAPXXXXXXXXX
                                            
Example Response
200 - OK
Example Request
                                                
GET https://service.criskco.com/apiservice.svc/ValidateRFC?rfc=GAPXXXXXXXXX&name=GAP&postal=12345
                                            
Example Response
200 - OK
POST SAT - RFC Validation Bulk
https://service.criskco.com/apiservice.svc/ValidateRFCBulk

Use the SAT - RFC Validation Bulk endpoint to validate bulk of RFC's up to 5,000 in a single call for companies registered at the Mexican Fiscal Authority (SAT).

It can be validated by two options:

  1. RFC only
  2. RFC +Name of the company +Postal Code of the company as registered.

RFC Only - The file in the body of the request will include in the first column (without header) the RFC, each one in a different row.

For example:

ABCYYYYYYYYYY


RFC +Name of the company +Postal Code - The file in the body of the request will include in the first column (without header) the RFC, Name and Postal code, seperated by '|' each one in a different row.

For example:

ABCYYYYYYYYYY|ABC|98765

The response will return if the request is successful or not, 3 optional boolean values and the response message from SAT (as you can see below in the example):

  1. Success - Is the request is successful or not
  2. ValidRFC - The RFC is valid or not
  3. ValidName (if requested) - The Company Name is valid or not
  4. ValidPostal (if requested) - The Postal Code is valid or not
  5. message - The exact message from SAT

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Accept-Encoding
gzip, deflate

None

form
=@"mTP-wnOLB/Example_RFC.csv"

None

Example Request
                                                
GET https://service.criskco.com/apiservice.svc/ValidateRFCBulk
                                            
Example Response
200 - OK
Example Request
                                                
GET https://service.criskco.com/apiservice.svc/ValidateRFCBulk
                                            
Example Response
200 - OK
POST Onboarding SAT Integration
https://service.criskco.com/apiservice.svc/OnboardingSatIntegration

Use the SAT Integration endpoint to onboard a company and retrieve data from the Mexican Fiscal Authority (SAT).

This will allow you to access invoices, payments and tax returns from the SAT.

Body Paramaters

FieldRequiredDescription
IsAgreeTermsYesHas the company accepted CRiskCo’s terms
DateAgreeTermsYesDate terms agreed
VersionAgreeTermsYesVersion of Terms
EmailYesThe Company’s email
UserYesCompany’s RFC
PasswordYesCompany’s CIEC
RefApplicantIdOptionalAn optional identifier that allows you to track

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Accept-Encoding
gzip, deflate

None

BODY raw

Example Request
Example Response
200 - OK
                                                    
{
    "ErrorCode": null,
    "Message": "Success! Information Received",
    "Success": true
}
                                                
Example Response
200 - OK
                                                    
{
    "ErrorCode": null,
    "Message": "The RFC GAPXXXXXXXX or ciec was not valid",
    "Success": false
}
                                                
POST Monitoring Company
https://service.criskco.com/apiservice.svc/RequestMonitoring

Use the Monitoring Company endpoint to monitor a company and retrieve again the data from the Mexican Fiscal Authority (SAT).

This will allow you to update all of the invoices, payments and tax returns from the SAT .

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Accept-Encoding
gzip, deflate

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693",
    "Source": "API"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/RequestMonitoring
{
	"applicantId": "1000143693",
    "Source": "API"
}
                                            
Example Response
200 - OK
                                                    
{
    "applicantId": "1004319766",
    "refApplicantId": null,
    "responseDetails": null,
    "success": true
}
                                                
POST Applicants Info
https://service.criskco.com/apiservice.svc/applicantinfo

The endpoint will return the Applicant’s business information and business financial information.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Accept-Encoding
gzip, deflate

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/applicantinfo
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Customers
https://service.criskco.com/apiservice.svc/customers

The endpoint will return the Applicant’s business customers information and customers financial information.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Accept-Encoding
gzip

None

Content-Encoding
gzip

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/customers
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Customer AR Transactions - Invoices
https://service.criskco.com/apiservice.svc/ar-transactions/invoices

The endpoint will return the Applicant’s business customer Invoices.

An Invoice represents a sales form where the customer pays for a product or service later.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Content-Encoding
gzip

None

Accept-Encoding
gzip

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/ar-transactions/invoices?fromDate=2020-01-01&toDate=2020-12-01
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Customer AR Transactions - Payments
https://service.criskco.com/apiservice.svc/ar-transactions/payments

The endpoint will return the Applicant’s business customer Payments.

A Payment object records a payment. The payment can be applied for a particular customer against multiple Invoices. It can also be created without any Invoice, by just specifying an amount.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Content-Encoding
gzip

None

Accept-Encoding
gzip

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/ar-transactions/payments?fromDate=2020-01-01&toDate=2020-12-01
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Customer AR Transactions - Credit Memo
https://service.criskco.com/apiservice.svc/ar-transactions/creditmemos

The endpoint will return the Applicant’s business customer Credit Memos.

A financial transaction representing a refund or credit of payment.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Content-Encoding
gzip

None

Accept-Encoding
gzip

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/ar-transactions/creditmemos?fromDate=2019-01-01&toDate=2020-12-01
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Customers Grouping
https://service.criskco.com/apiservice.svc/grouping/customers

The Customers Grouping Endpoint allows you to retreieve all the applicant’s customer information in a single call to the API. This will return with Invoice, Payments and Credit Memos.

HEADERS

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Content-Type
application/json

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/grouping/customers?fromDate=2020-01-01&toDate=2020-02-01
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Suppliers
https://service.criskco.com/apiservice.svc/suppliers

The endpoint will return the Applicant’s business suppliers’ information and financial information.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/suppliers
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Supplier AP Transactions - Supplier Invoices
https://service.criskco.com/apiservice.svc/ap-transactions/invoices

The endpoint will return the Applicant’s business supplier Invoices.

Supplier Invoices are accounts payable transactions representing a request-for-payment from a supplier for goods/service.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
	
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/ap-transactions/invoices?fromDate=&toDate=
{
	"applicantId": "1000143693"
	
}
                                            
Example Response
200 - OK
POST Supplier AP Transactions - Supplier Payments
https://service.criskco.com/apiservice.svc/ap-transactions/payments

The endpoint will return the Applicant’s business supplier Payments.

A Supplier Payment object records a payment. The payment can be applied for a particular supplier against multiple Invoices. It can also be created without any Invoice, by just specifying an amount.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
	
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/ap-transactions/payments?fromDate=&toDate=
{
	"applicantId": "1000143693"
	
}
                                            
Example Response
200 - OK
POST Supplier AP Transactions - Supplier Credit Memo
https://service.criskco.com/apiservice.svc/ap-transactions/creditmemos

The endpoint will return the Applicant’s business supplier Credit Memos.

A financial transaction representing a refund or credit of payment with a supplier.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
	
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/ap-transactions/creditmemos?fromDate=&toDate=
{
	"applicantId": "1000143693"
	
}
                                            
Example Response
200 - OK
                                                    
{
    "applicantId": "1000143693",
    "refApplicantId": null,
    "supplierId": null,
    "creditmemos": []
}
                                                
POST Supplier AP Transactions - Expenses
https://service.criskco.com/apiservice.svc/ap-transactions/expenses

The endpoint will return the Applicant’s business supplier Expenses.

A financial transaction that represents a company expense that is not invoiced.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
	
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/ap-transactions/expenses?fromDate=&toDate=
{
	"applicantId": "1000143693"
	
}
                                            
Example Response
200 - OK
POST Suppliers Grouping
https://service.criskco.com/apiservice.svc/grouping/suppliers

The Suppliers Grouping Endpoint allows you to retreieve all the applicant’s supplier information in a single call to the API. This will return with Invoice, Payments and Credit Memos.

HEADERS

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

Content-Type
application/json

None

PARAMS

fromDate

Optional: ISO 8601 datestamp indicating the start date to filter against

toDate

Optional: ISO 8601 datestamp indicating the end date to filter against

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/grouping/suppliers?fromDate=2019-01-01&toDate=2020-04-01
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Financial Report - Row Data - Balance Sheet
https://service.criskco.com/apiservice.svc/financialreports/rowdata/balancesheet

Returns the Balance Sheet as it appears in the clients ERP or accounting software.

In the body you can specify the financalYear as follows:
Current, FinancialYearEnd, PreviousFinancialYearEnd, SecondPreviousFinancialYearEnd, ThirdPreviousFinancialYearEnd.

If the financalYear parameter is blank, the current year will be returned by default.

Each report is an ordered collection of rows and cells. Rows can be of various types (e.g. section, row and summary row elements). Cells can contain values and attributes with nested values.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693",
	"financialYear": ""
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/financialreports/rowdata/balancesheet
{
	"applicantId": "1000143693",
	"financialYear": ""
}
                                            
Example Response
200 - OK
POST Financial Report - Row Data - Profit and Loss
https://service.criskco.com/apiservice.svc/financialreports/rowdata/profitandloss

Returns the Profit and Loss as it appears in the clients ERP or accounting software.

In the body you can specify the financalYear as follows:
Current, FinancialYearEnd, PreviousFinancialYearEnd, SecondPreviousFinancialYearEnd, ThirdPreviousFinancialYearEnd.

If the financalYear parameter is blank, the current year will be returned by default.

Each report is an ordered collection of rows and cells. Rows can be of various types (e.g. section, row and summary row elements). Cells can contain values and attributes with nested values.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693",
	"financialYear": "Current"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/financialreports/rowdata/profitandloss
{
	"applicantId": "1000143693",
	"financialYear": "Current"
}
                                            
Example Response
200 - OK
POST Financial Report - Row Data - Bank Statement
https://service.criskco.com/apiservice.svc/financialreports/rowdata/bankstatement

Bank Statement as it appears in the clients ERP or accounting software.

Each report is an ordered collection of rows and cells. Rows can be of various types (e.g. section, row and summary row elements). Cells can contain values and attributes with nested values.

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/financialreports/rowdata/bankstatement
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
                                                    
{
    "applicantId": "1000143693",
    "refApplicantId": null,
    "reports": []
}
                                                
POST Financial Report - Standard - Balance Sheet
https://service.criskco.com/apiservice.svc/financialreports/standard/balancesheet

Returns the Balance Sheet standardised by CRiskCo.

In the body you can specify the financalYear as follows:
Current, FinancialYearEnd, PreviousFinancialYearEnd, SecondPreviousFinancialYearEnd, ThirdPreviousFinancialYearEnd.

If the financalYear parameter is blank, the current year will be returned by default.

Each report is a collection of rows and cells. Rows can be of various types (e.g. section, row and summary row elements). Cells can contain values and attributes with nested values.

Below is a detailed list of the types and codes used by the CRiskCo API
classificationaccountTypesubAccountTypeDescription
AssetsCurrentAssetCurrentAssetcash and other assets that are expected to be converted to cash within a year
AssetsCurrentAssetBankCurrent balance in the banks accounts
AssetsCurrentAssetInventoryRepresent the inventory value
AssetsCurrentAssetAccountReceivablesAccounts receivable is the balance of money due to a firm for goods or services delivered or used but not yet paid for by customers.
AssetsNonCurrentAssetNonCurrentAssetLong-term investments for which the full value will not be realized within the accounting year.
AssetsNonCurrentAssetDeprecationAmortizationDepreciation and Amortization value.
EquityEquityEquityCompany equity value
EquityEquityOpenBalanceEquityCompany equity value in the date previous to the report period
EquityEquityAccumulatedAdjustmentaccumulated adjustments account, A special account is used to track undistributed earnings of an S corporation that have been taxed to shareholders previously.
EquityEquityCurrentEarningsThe Current Year Earnings account value is calculated automatically as sales and other business transactions that impact income and expense accounts, are recorded. Its balance equals income minus cost of sales and expenses.
EquityEquityRetainedEarningsRetained earnings are the profits that a company has earned to date, less any dividends or other distributions paid to investors.
EquityEquityNetIncomeNet income is an entity’s income minus cost of goods sold, expenses and taxes for an accounting period.
LiabilityCurrentliabilitiesCurrentLiabilitiesCurrent Liabilities, amounts due to be paid to creditors within twelve months
LiabilityCurrentliabilitiesAccountPayableAccounts payable (AP) is money owed by a business to its suppliers shown as a liability on a company’s balance sheet.
LiabilityCurrentliabilitiesCreditCardsCredit Cards accounts.
LiabilityNonCurrentLiabilitiesNonCurrentLiabilitiesUsually refer to long term liabilities (more than 12 months).

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693",
    "financialYear": ""
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/financialreports/standard/balancesheet
{
	"applicantId": "1000143693",
    "financialYear": ""
}
                                            
Example Response
200 - OK
POST Financial Report - Standard - Profit and Loss
https://service.criskco.com/apiservice.svc/financialreports/standard/profitandloss

Returns the Balance Sheet standardised by CRiskCo.

In the body you can specify the financalYear as follows:
Current, FinancialYearEnd, PreviousFinancialYearEnd, SecondPreviousFinancialYearEnd, ThirdPreviousFinancialYearEnd.

If the financalYear parameter is blank, the current year will be returned by default.

Each report is a collection of rows and cells. Rows can be of various types (e.g. section, row and summary row elements). Cells can contain values and attributes with nested values.

Below is a detailed list of the types and codes used by the CRiskCo API
classificationaccountTypesubAccountTypeDescription
RevenueSalesSalesDirect sales of product/service
RevenueSalesDiscountDiscounts Provided
RevenueSalesOtherSalesSales generating revenue not by the main products/services of the company.
RevenueOtherIncomeOtherIncomeUsually refer to income from financial vehicles, as interest, Grants, Dividend etc.
RevenueOtherIncomeGrantsGrants
RevenueOtherIncomeInterestInterest (income or expense)
RevenueOtherIncomeDividendRevenue generated by Dividend
ExpensesCOGSCOGSCost of Goods Sold (COGS)
ExpensesCOGSFreightAndDeliveryFreight and Delivery (income or expense)
ExpensesCOGSOtherCOGSOther COGS
ExpensesExpenseTaxTax Paid
ExpensesExpenseExpenseExpense
ExpensesExpenseBadDebtBad debt
ExpensesExpenseInsuranceInsurance expense
ExpensesExpenseLegalLegal expense
ExpensesExpenseTravelTravel expense
ExpensesOtherExpenseOtherExpenseOther expenses

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/financialreports/standard/profitandloss
{
	"applicantId": "1000143693"
}
                                            
Example Response
200 - OK
POST Financial Report - Documents
https://service.criskco.com/apiservice.svc/Documents

Retrieve an Applicants documents. This includes documents uploaded by the applicant and reports prepared by CRiskCo.
The response includes a unique http file link where the document can be downloaded from.

Catalogue of Documents
report_typeDescription
SAT_FINANCIAL_DECLARATIONAnnual Tax Declarations submitted to SAT
SAT_CONTRIBUYENTEThe Opinion De Contribuyente from SAT
SAT_ANALYTICSSummarized Company Report prepared by CRiskCo
APPLICANT_FILESFiles uploaded by the applicant as part of their onboarding
MONTHLY_GENERATED_REPORTMonthly report prepared by CRsikCo

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693",
    "csvInJson":false
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/Documents
{
	"applicantId": "1000143693",
    "csvInJson":false
}
                                            
Example Response
None - None
POST Applicant Financials Grouping
https://service.criskco.com/apiservice.svc/grouping/applicant-financials

The Financials Grouping Endpoint allows you to retreieve all the applicant’s Financial Statement Data in a single API Call. This will return both the Row Data and the CRiskCo Standardised reports, Documents as well as the analytics and summaries calculated by CRiskCo.

HEADERS

apiId

None

apiKey

None

Content-Type
application/json

None

BODY raw

                                                  
                                                    
{
	"applicantId": ""
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/grouping/applicant-financials

{
	"applicantId": ""
}
                                            
POST Update Status
https://service.criskco.com/apiservice.svc/applicant-status

The API is used to update the application status.
The default ‘status’ value for all new applicants is ‘New’.

Changing the status of an applicant will affect the connection to the applicant’s accounting system and the connection may be disconnected. While disconnected, the applicant’s data available via the API will not be up to date and only the data from the last successful update will be available. Changing the status from a disconnected status to a connected status, will trigger an attempt to re-establish a connection to the accounting system.

Available status options:

New

Denied

CancelByApplicant

UnderEvaluation

Approved

CompanyDefaulted

Completed

HEADERS

Content-Type
application/json

None

apiId
{{client-api-id}}

None

apiKey
{{client-api-key}}

None

BODY raw

                                                  
                                                    
{
	"applicantId": "1000143693",
	"status": "Approved"
}
                                                  
                                              
Example Request
                                                
POST https://service.criskco.com/apiservice.svc/applicant-status

{
	"applicantId": "1000143693",
	"status": "Approved"
}