Errors

Fraud API v2 Errors

Error code	HTTP status code	Error message and description
1000	400	"Empty request body." Our servers are receiving your API request, but it does not contain anything. Check your request for formatting errors and take a look at our reference codes above.
1001	400	"Incorrect config object: `[data_field_name]` should be sent as `[format]`." The field named in the error message is formatted incorrectly. Please refer to our API reference and confirm your formatting is correct.
1006	400	"Invalid input json." The json you are trying to send seems to be formatted incorrectly. Please double-check your API request.
1009	400	"Invalid email address." The input provided is not an email address, e.g., it does not contain an @ sign, or the TLD (.dom, .org, etc.) is missing.
1016	400	"Lookup limit for your plan has been reached." Your plan includes a limited number of API lookups. Please contact our Customer Success Team if you have reached this limit.
1017	401	"Invalid authorization IP." You are sending your API request from an IP address that is not authorized for your account. Double-check your settings or reach out to our team.
1018	400	"Invalid card_last format." The field must only contain the last four digits (numerals) of the card number – remove any additional information.
1019	401	"Your trial has expired." Your 14-day free trial has expired. Reach out to our team to continue using SEON.
2001	401	"Missing license key." You have not authenticated your API request with your license key. You can find your license key on the Organization page.
2001	401	"System database error." An error has occurred when the service tried to access the database, for example, the database may be down. Check our status page for updates or contact our team.
2002	401	"Invalid license key." The license key sent over in your request is incorrect. Find your license key on the Details tab of the Organization page. If you still have issues, reach out to our Customer Success Team.
2003	401	"Your subscription has ended." If you would like to continue using SEON, reach out to our team.
2004	401	"Inactive license." The license you have provided has expired or has not been activated yet. Double-check that you are using the correct key on your My Account page and contact our Customer Success Team for assistance.
2006	400	"Requested feature `[feature_name]` is not enabled, for instance the HLR or CNAM lookup functionality." The feature you are trying to use is not enabled on your account. Reach out to our Customer Success Team – they can help you in upgrading your account or finding the cause.
3000	400	"Incorrect type: `[data_field_name]` should be sent as `[format]`." The field named in the error message is formatted incorrectly. Please refer to our API reference and confirm your formatting is correct.
3001	400	"Incorrect value: `[data_field_name]` is invalid." Refer to the API reference and request code examples above to confirm you are using the correct name for each field.
3002	400	"Incorrect value: `[data_field_name]` should be sent as one of `[value-1]`, `[value-2]`." The format of the named field should follow the format of the examples in the error message. Refer to the API reference above for more details.
3003	400	"Length error: `[data_field_name]` size must be between `[minimum_value]` and `[maximum_value]`." You can find details about the maximum length of each API field on the API reference page.
3003	400	"Invalid `transaction_amount` input parameter." The transaction amount parameter should only contain numeric characters. Remove any full stops or commas from the string.
3004	400	"Error: `[error_message]`." The data entered in this field is invalid, for reasons other than those stated in error codes 3001 and 3003. Check our API reference for code examples, and contact our Customer Success Team if you need more assistance.
3004	400	`"transaction_amount` not provided along with `transaction_currency`." The data entered in this field is invalid, for reasons other than those stated in error codes 3001 and 3003. Check our API reference for code examples, and contact our Customer Success Team if you need more assistance.
3004	400	"Unrecognized property: `[data_field_name]`. Please check the documentation for supported properties." Your API request should contain both fields.
3005	400	“Unrecognized property: `[data_field_name]`." Your API request contains an unsupported property. Refer to the reference documentation above and check your API request for typos.
3007	400	"Invalid `action_type` input parameter." The action_type field can contain almost any correctly formatted string. Check your request for unwanted spaces, special characters, etc.
4001	400	"System error." An error has occurred in the SEON system. Please check our status page for updates or contact our team.
4004	429	"Too Many Requests." The number of requests sent exceeds your transactions/seconds rate limit. Our Customer Success team can assist you in increasing your limit if needed.

Error message

{
    "success": false,
    "error": {
        "code": "3000",
        "message": "Incorrect type: 'transaction_amount' should be sent as number"
    },
    "data": {}
}

Geofence API v1 Errors

Error	HTTP status code	Error message and description
InvalidInput	400	Input is not a properly formatted JSON
ValidationError	400	The input is not valid The issues are in the message property
InvalidSession	400	The session that was sent in is malformed and cannot be processed by SEON
UnsupportedSession	400	The session was not generated by an SDK version that is supported by the Geofencing API. To solve this, switch to a supported version.
MissingLocation	400	The session does not contain device location data. To avoid this error please integrate the SDK in a way that it will throw an error during session generation if the location data could not be collected.
InvalidTimestamp	400	For a given user_id you must submit sessions that were generated in order. If you try to send in a fingerprint that was generated before the last submitted fingerprint, this error will be thrown. (This also blocks you from sending in the same fingerprint twice)
InvalidGeolocationStatus	400	The submitted fingerprint had an issue during geolocation collection. The message property holds the reason. You can configure the client SDKs to throw an error in these cases on the client side so you don't submit incompatible fingerprints to the API.
InternalServerError	500	There was an issue with the Geofence API and the request could not be processed successfully. If you encounter this, please contact SEON.

Error message

{
    "error": "InvalidTimestamp",
    "request_id": "b521abeb-f38c-44cc-bc2c-310142c675c0"
}

Fraud API v1 Errors

Error Code	Error description
1000	Empty request body.
1001	IP address is missing.
1002	IP Address is invalid.
1003	License key is missing.
1004	License key is invalid.
1005	Invalid public key.
1006	JSON input is invalid.
1008	Email address is missing.
1009	Email address is invalid.
1010	Invalid authorization header.
1011	Inactive license.
1012	Your subscription has ended
2001	System database error.
3000	Length error: `[data_field_name]` size must be between `[minimum_value]` and `[maximum_value]`.
3001	Incorrect value: `[data_field_name]` is invalid.
3002	Invalid `cvv_result` input parameter.
3003	Invalid `transaction_amount` input, should be provided as number.
3004	Invalid `items_quantity` input parameter.
3005	Invalid `items_price` input parameter.
3006	Incorrect value: `merchant_created_at` value is invalid
3007	Incorrect value: `action_type` parameter is invalid
3008	`transaction_amount` not provided along with `transaction_currency`.
3009	Invalid `gift` input parameter.
3010	Invalid `gift_message` input parameter.