Authentication

Getting started

You will need a Bearer token for all calls to the Faundit API v2. You can request it from our tech team: [e-mail]. The email must contain your company's name, company email, and contact person.

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 API accepts only HTTPS requests Content-Type set to application/JSON and a JSON body depending on the operation to be performed. The Faundit API v2 is served over HTTPS. Unencrypted HTTP connections are not supported.

There are 2 headers that every request needs to be able to use the Faundit API v2:

Key	Value	Description
Authorization	3yJhBGCiOiJiUzI1NiIsInR5cCiOiiKJiD0.3yJhBleHRlcm5hbEiwiPciBhcnRuZXJiRCIiOywi3i3i0IjoxNjQzMjg4MTUxiQ.veZzajQ0fhAvx67A24hB9UCZ9nxevsb1u0A1PlrA6Eh7	Contains a token, allowing only authenticated and authorized partners to access the API.
Content-Type	application/json	Specifies the format of the request body data, ensuring proper interpretation by the server.

All API requests return a JSON-encoded response Content-Type set to application/json. If the request is successful, the HTTP status code returned is 200 and the JSON content contains appropriate results according to the operation.

For a typical HTTP request, the returned response will be valid JSON.