Error Codes for Person API
Gainsight NXT
Error Codes
This article shows the list of error codes that you may receive in the error response to Person API. Error descriptions, their reasons, and HTTP status codes are added in support to the Error codes. For detailed information, refer People API Documentation.
If you receive an error response as invalid value passed for the specific data type, refer Supported Data Types to learn more on the supported formats for each data type.
Following is the list of Error codes:
| Error Code | Error Message | Reason | HTTP Status Code |
|---|---|---|---|
| GSOBJ_PEOPLE1001 | People entities do not exist | Entities that People are associated to do not exist | 400 |
| GSOBJ_VQP1001 | Query params are null or empty | Email value is empty or null in “Get Person By Email” API | 400 |
| GSOBJ_VDTBOOL1001 | Invalid boolean value | Data type validation | 400 |
| GSOBJ_VDTNUM1001 | Invalid number value | Data type validation | 400 |
| GSOBJ_VDTNUM1002 | Number is out of range | Data type validation | 400 |
| GSOBJ_VDTBSTR1001 | Invalid string value | Data type validation | 400 |
| GSOBJ_VDTDATIME1001 | Invalid datetime value | Data type validation | 400 |
| GSOBJ_VDTCURREN1001 | Invalid currency value | Data type validation | 400 |
| GSOBJ_VDTCURREN1002 | Invalid representation of comma as thousand separator | Data type validation | 400 |
| GSOBJ_VDTEMAIL1001 | Invalid email value | Data type validation | 400 |
| GSOBJ_VDTGSID1001 | Invalid gsid value | Data type validation | 400 |
| GSOBJ_VDTPERCENT1001 | Invalid percentage value | Data type validation | 400 |
| GSOBJ_VDTSFDCID1001 | SFDCID must be alphanumeric 15 or 18 characters | Data type validation | 400 |
| GSOBJ_VDTPKLST1001 | Dropdownlist category not found | Data type validation | 400 |
| GSOBJ_VDTPKLST1002 | Dropdownlist item not found | Data type validation | 400 |
| GSOBJ_VDTURL1001 | Invalid URL value | Data type validation | 400 |
| GSOBJ_VCRUDR1001 | Row Info cannot be null | When passed record is null or empty | 400 |
| GSOBJ_VCRUDR1002 | Fields do not exist in object | When fields do not exist in object | 400 |
| GSOBJ_VCRUDR1003 | Field Info cannot be null or empty | A column is null or empty like " : ". Key and Value are missing in the request body. | 400 |
| GSOBJ_VCRUDR1005 | Field Info Key cannot be null or empty | Field Name is null or empty in key-value pair | 400 |
| GSOBJ_VCRUDR1006 | Field Info value cannot be null | Value is null or empty in key-value pair | 400 |
| GSOBJ_VCRUDR1007 | Key field does not exist in object | Field defined as key field does not exist in object | 400 |
| GSOBJ_VCRUDR1008 | RowsIdentifiers cannot be null or empty | If GSID is null or empty in update record use case | 400 |
| GSOBJ_VCR1002 | Data contains gsid | When data contains “GSID” system field which is always auto-populated. This value should not be passed in the Request body. | 400 |
| GSOBJ_VCR1003 | Data contains “Created Date” system field | When data contains “Created Date” system field which is always auto-populated. This value should not be passed in the Request body. | 400 |
| GSOBJ_VCR1004 | Data contains “Modified Date” system field | When data contains “Modified Date” system field which is always auto-populated. This value should not be passed in the Request body. | 400 |
| GSOBJ_VCR1005 | Required field has no data | Required field cannot be null or empty | 400 |
| GSOBJ_VCR1006 | Data contains calculated measure | Calculated fields are always auto-populated and cannot be updated directly | 400 |
| GSOBJ_VCR1009 | Non Editable fields exists in FieldInfos | System fields exist in data. System fields and values should not be passed in the request body | 400 |
| GSOBJ_VDTFDL1001 | Invalid rows identifier | “GSID” is the only field which can be used as an identifier. | 400 |
| GSOBJ_VDTFDL1002 | Field info key or value is null | This error appears when key or value is missing in the Key-Value pair. | 400 |
| GSOBJ_FCIRK001 | Record can not be null or empty | Null or empty record cannot be inserted | 400 |
| GSOBJ_FCIRK002 | Resolution fields data does not exist in the given record | Fields defined as resolution key fields do not exist in the data | 400 |
| GSOBJ_RLS002 | ResolveLookupRequest invalid target object | Invalid target object set in import lookup configuration | 400 |
| GSOBJ_RLS004 | ResolveLookupRequest invalid target lookup mapping | Invalid target lookup mapping (lookup fields) set in import lookup configuration | 400 |
| GSOBJ_RLS006 | ResolveLookupRequest invalid target search criteria | Invalid target search criteria in the import lookup configuration | 400 |
| GSOBJ_RLS008 | ResolveLookupRequest source collectionMaster not found | Invalid source object set in import lookup configuration. When the given lookup object name is incorrect/does not exist | 400 |
| GSOBJ_VCUSTOM1005 | Unsupported data type in the request | Attempted to ingest into a field which is not supported for ingestion. | 400 |
| GSOBJ_VCUSTOM1006 | Key is null or empty | Field Name is null or empty in the key-value pair. | 400 |
| GSOBJ_PEOPLE1001 | People entities do not exist | Entities that People are associated to do not exist | 400 |
| GSOBJ_VCRUDR1001 | Row Info cannot be null | Request/Data Validation Error | 200 |
| GSOBJ_VCUSTOM1009 | Resolution keys are null or empty in the request | Request/Data Validation Error | 200 |
GSOBJ_VRMR001 |
Resolution Metadata Collection Master doesn't exist for objectname | Request/Data Validation Error | 200 |
| GSOBJ_RLS006 | ResolveLookupRequest invalid target search criteria | Request/Data Validation Error | 200 |
| GSOBJ_RLS005 | ResolveLookupRequest invalid source lookup mapping | Request/Data Validation Error | 200 |
GSOBJ_RLS013 |
ResolveLookupRequest standard field group type field can have lookup field has Gsid only | Request/Data Validation Error |
200 |
| GSOBJ_RLS004 | ResolveLookupRequest invalid target lookup mapping | Request/Data Validation Error | 200 |
| GSOBJ_OTHERS003 | Data store not supported | Request/Data Validation Error | 200 |