Errors
We updated our API endpoints and updated authentication requirements. This update introduces new functionalities, updated naming, route paths, parameters, and body.
Previous Names:
Example 1: Members have been renamed to Locations.
Example 2: The identifier faundit_memberID is locationID now.
Removed Requirements:
Example 3: Thefaundit_memberID is no longer required on the headers. Instead, it would be expected in some endpoints as part of the body, under the property name locationID.
If you integrated with our API before this update, everything will continue to function as expected. You can also use your old faundit_memberID as the new locationID.
Please contact us if you encounter any unexpected issues.
The Faundit API v2 utilizes standard HTTP error and status codes to convey different types of errors:
200 OK: The request was successfully executed.
400 Bad Request: The request is unacceptable, often due to a missing required parameter.
401 Unauthorized: No valid access token was provided; the token is either missing or expired.
403 Forbidden: The access token lacks the necessary permissions to fulfil the request.
404 Not Found: The requested resource does not exist.
409 Conflict: The request couldn't be completed due to a conflict with the current state of the resource.
500 Internal Server Error: An unexpected error occurred on our server. Such errors typically indicate a bug on our side, and we promptly log and address them. If issues persist, please contact us directly at tech@faundit.com.
Last updated