Procedures for providers (data, knowledge rules, tools and services) are still under development, but we do welcome enquiries ([email protected]).

Most food, nutrition or health-related web-service can be made available to users via Quisper®.
If you would like to connect to Quisper, click here for QSP provider API guidelines (PDF version 5, 01.10.2018).

Providers should read the QSP provider API guidelines (version 5, 01.10.2018), which explain:

  • Structure
  • Documentation
  • Security
  • Performance

Quisper® provides access to APIs from different providers (data, knowledge, tools or services). To facilitate access by users, providers should follow the guidelines provided. Ideally, multiple webservices should be harmonised for structure (syntactic) and content (semantic). Quisper will not seek semantic harmonisation.

Read more about structure

Read more about documentation

Read more about security

Read more about performance

Key words, such as "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in these guidelines are to be interpreted as described in RFC 2119.

Request | New webservice

Click here for the new webservice request form, if you want to connect to Quisper®

For an example of a completed webservice request form, click here

For an example of a technical description, click here

What happens next?

The new webservice form will be reviewed by Quisper and our representative will contact you to discuss either:

  1. Why we are not able to connect the service (e.g. does not comply with our policies or technical issues)
  2. Progressing the request and linking your resource to Quisper

Once your resource has been connected, the description will be added Quisper, informing potential users.