Givvable API is accessible via https://data.givvable.com (Data Portal) which provides documentation, latest changes, announcements, and compliance-related tasks. The integrations and consumption of data via API is intended to be used by a qualified software engineer.The API currently supports the REST standard only. We provide various automated documentation formats such as OpenAPI Specification and WADL, which can be used to create POSTMAN collections to aid with implementation. The API utilizes a subscription key that must be passed in the header of each request.

Subscription keys are managed through our Data Portal. By default, you have two keys available for use with your requests.

To access the Data Portal, you must create an account by following these steps:

1. Navigate to https://data.givvable.com
2. Click "Sign Up" in the top right-hand corner
3. Complete your details
4. Accept our Terms of Service & Privacy Policy

With Portal access, you can:

1. Manage your Subscription Keys (https://data.givvable.com/docs/products)
2. Access usage reports
3. View documentation
4. Access compliance documentation (notes & disclaimers)

We recommend rotating keys every 6 to 12 months to reduce the risk of key theft or misuse.

All calls to our API are recorded for monitoring, debugging, billing, and compliance purposes.

Partners with access to premium data are generally charged based on API calls to the following endpoints: getOrganisationByIdentifier or getOrganisationById.

A successful call is one that returns data (response code 200). Each time this data is returned, it will be counted as one successful call for the purposes of billing. If you call the same organisation multiple times you will be charged for each successful call.

If there is no retrievable data on the organisation you are trying to look up, the endpoint will respond with a 404 (not found) status, which is considered an unsuccessful call.

givvable API will start throttling calls if a large quantity of calls is made within a short period of time. If you are getting “Too many requests” response, it is most likely because you are making too many requests per minute on your API key. Please contact us at support@givvable.com if you would like for your request ratio be adjusted.

Givvable is required by credential issuers to ensure that their credentials are not misrepresented or used inappropriately. Therefore, we require any partner who displays credentials from Givvable to clearly display notes and disclaimers.

For full technical documentation on how to obtain and implement notes and disclaimers, please visit https://data.givvable.com/docs/notes-and-disclaimers-guide.

To gain access to premium data, please reach out to sales@givvable.com.

If you are a partner, subject to terms in your Order Formt, you will most likely be charged for successful calls to getOrganisationByIdentifier and getOrganisationById.

Invoices are issued on the last day of every month based on successful calls made during that period. UTC timezone is used for all reporting and billing purposes.

We understand that retrieving large amounts of data has performance implications. Therefore, we allow caching on the consumer side for up to 24 hours. This limitation exists because our data is continuously updated, and caching for longer periods would create a high risk of using stale and potentially inaccurate data.

We understand that retrieving large amounts of data has performance implications. Therefore, we allow caching on the consumer side for up to 24 hours. This limitation exists because our data is continuously updated, and caching for longer periods would create a high risk of using stale and potentially inaccurate data.