API Response Codes

Refer to the below response code glossary to help you troubleshoot any errors.

Glossary

Response Code	Messages	Explanation
200 OK	The request was successful!	N/A
400 Bad Request	Request validation failed on an input.	Check that your inputs are entered correctly.
401 Unauthorized	Participant authentication is required.	N/A
402 Usage Limit	Participant quota has been exhausted.	You've reached a plan limit and will need to upgrade to the next tier.
402 Payment Method Required	You must add a payment method to your account to use the REST API for affiliate programs.	N/A
403 Not Authorized	You are not allowed to perform that action. No valid participant access token provided.	Your API key may be revoked or contain a typo, or you may be trying to interact with another user's program or participant data (which is not allowed).
403 Paid Plan Required	A paid plan is required to use the GrowSurf REST API	N/A
404 Resource Not Found	The requested resource does not exist.	You may be trying to request a resource that does not exist or was deleted.
409 Conflict Duplicate Request	Conflicting duplicate request.	N/A
422 Unprocessable Entity Error	This endpoint is only available for referral programs. Your program is an affiliate program.	You may be trying to call an endpoint that is only valid to referral programs (or vice versa with affiliate programs).
422 Participant Blocked	Participant was detected as a high-risk fraudster and was blocked from joining.	The person may be a high-risk fraudster, and has been blocked from entering the program. Learn more about how GrowSurf's anti-fraud system works. Please check that your program's anti-fraud settings are not set to Strict, or that you do not have the email or IP address blacklisted.
429 Too Many Requests	You have reached a rate limit.	You have sent too many requests in a given time OR You have reached the usage limit in your current plan. See Rate Limits and Max Connections for more details on rate limits.
5XX Internal Server Error	The GrowSurf server is inaccessible or offline -- that's our fault! Check for updates on our status page.	N/A