API integration
Olfeo's OEM API is a simple yet powerful way to determine the category of a URL, FQDN or IP and get information about it to make informed business decisions based on this information.
As shown below, you cant get various information regarding an input submitted such as its categorization in our taxonomy, whether it belongs to a SaaS app etc.
Please note that the level of information returned may depend on your subscription level and of course of the input.
 |
API structure overview
Our service is split into two APIs: a business API (categorize) and an ancillary API (authenticate).
Important
To consume the categorize API, you will first need to obtain an authentication token from the authenticate API using the access credentials provided by Olfeo.
Don't have access credentials yet? Contact us to find out more!
The documentation of our APIs is the same, regardless of the integration mode you have chosen of our service: direct calls to our public API or an on-premise integration via our SDK.
REST API vs gRPC?
This API comes in two flavours: REST and gRPC.
Although it was designed and developed first for gRPC and Protocol Buffer, a compatibility layer provides the REST API service. Both versions are served by the same host.
The service is available by default under both protocols, except for possible exceptions explicitly described in the documentation of the endpoint concerned.
In addition, it is possible to use headers following the standard Content Negotiation to provide query parameters or retrieve server responses in format protobuf, instead of the JSON format (default in REST).
The server also provides a standard gRPC reflection service (undocumented) allowing tools like grpcurl to automatically discover the declarations of the different services.