(Deprecated) Ingest Documents via JSON
This API is deprecated and no more supported due to scaling issues.
Upload a sale or purchase document with JSON payload.
A maximum of 100 invoice line item objects can be ingested in one request.
Request Method
POST
Request URL
Replace the {{BASE_URL}}
with the one mentioned here based on whether you are using sandbox or production.
Request Headers
x-cleartax-auth-token
String
Cannot be empty.
x-cleartax-gstin
String
Cannot be empty
Mandatory. GSTIN of the taxpayer registered on CFC.
Content-Type
String
application/json
Request Path Params
templateType
String
Enum:
sales,
purchase
Type of document. sales - Sales document.
purchase- Purchase document.
Request Query Params
There are no query parameters for this API.
Request Body
userInputArgs
Object
NA
jsonRecords
Array
MaxLength: 100
User Input Arguments Object
templateId
String
NA
groupId
String
NA
Unique ID across the PAN to group a set of documents as a single record on the Clear Import History page.
Default: Autogenerated random ID.
settings
Object
NA
Settings Object
ignoreHsnValidation
Boolean
NA
Optional. Indicates if HSN validation has to be ignored or not.
true - HSN validation error will be ignored.
false - HSN validation error will not be ignored. Default: false
Sample Request
Sales document
Purchase document
Response Status Codes
200
For a successfully processed request (may be a success or validation error).
400
If the request schema is not valid.
401
If the user is not authenticated for the operation.
403
If the user is not authorized for the operation.
500
If there are any unhandled exceptions on Clear side.
Response Schema
gstinStats
Array
NA
jsonRecordErrors
Array
NA
errors
Array
NA
GSTIN Stats Object
gstin
String
NA
Seller GSTIN that these stats belong to.
totalDocumentCount
Number
NA
Total count of documents parsed successfully.
validRows
Number
NA
Total count of valid document line objects.
invalidRows
Number
NA
Total count of invalid document line objects.
JSON Record Error Details Object
recordIndex
Number
NA
Array index of the record in request jsonRecords. The index starts from 0.
recordErrors
Array
NA
externalId
String
NA
External ID that was sent in the request to identify the document, if any. In case an external ID was not sent, this field will not exist.
externalLineItemId
String
NA
External ID that was sent in the request to identify the document line item, if any. In case an external ID was not sent, this field will not exist.
Record Error Details Object
errorId
String
NA
Error ID
columnName
Array
NA
Array of strings representing field keys in the jsonRecords of the request that has an error.
errorMessage
String
NA
User friendly error message.
Non-Validation Error Details Object
errorCode
String
NA
Error code
errorMessage
String
NA
Error message.
errorField
NA
Error field.
errorValues
NA
Error values.
errorResolution
NA
Error resolution.
Sample Response
Success - HTTP Status Code - 200
Validation Error - HTTP Status Code - 200
Non-Validation Error - HTTP Status Code - 401
Non-Validation Error - HTTP Status Code - 500
API Validations
There are more than 200 field validations as well as business validations on the Clear API side. For data validation errors, the validation error message will be sent back in the `jsonRecordErrors` field in the response.
API Constraints
This API needs to be authenticated with a valid user authentication token. If the auth token is not present or is invalid, the API will return HTTP Status Code 401.
If the auth token is valid, but the user does not have the authorization, then the API will return HTTP Status Code 403. The user, whose auth token is used, should have permission to create a document.
Integrating for MaxITC?
If you are integrating with Max ITC, once the documents are uploaded, trigger the reconciliation using the Trigger MaxITC Workflow API.
Last updated