FAQs

Fenris API Frequently Asked Questions (FAQ)

 

General Information

Q1: What is Fenris?
Fenris is an API-driven service tailored for modern insurance companies. It offers a suite of APIs that provide data and scores to inform insurance coverage decisions, evaluate risk, and enhance the experience of applying for, rating, and servicing insurance accounts.
🔗 See: Introduction

 

Q2: How does Fenris improve the insurance application process?
Fenris APIs save research time and minimize errors in fillable forms by returning applicant data with completed form fields. This allows clients to confirm information rather than manually completing forms.
🔗 See: How Fenris Helps

 

Getting Started

Q3: How can I obtain access to Fenris APIs?
To get started, you need to request credentials. You can do this by clicking on the “request credentials” link provided in the documentation.
🔗 See: Getting Started – Credentials

 

Q4: What is the validity period of an access token?
Each access token generated for Fenris APIs is valid for 24 hours. After expiration, you must generate a new token to continue accessing the services.
🔗 See: Authentication Overview

 

Authentication

Q5: What authentication method does Fenris use?
Fenris utilizes OAuth2 authorization with the Client Credentials workflow. You will receive a Client ID and Client Secret, which are used to obtain an access token from the Authorization Server.
🔗See: OAuth2 Authorization

 

Q6: How do I obtain an access token?
To obtain an access token, send a POST request to the Fenris Authorization Server with your Client ID and Client Secret. The server will return a bearer token, which you include in the Authorization header of your API requests.
🔗 See: Getting an Access Token

 

Developer Resources

Q7: Does Fenris provide test data for development purposes?
Yes, Fenris offers a Developer Data Collection consisting of artificial data records. These records can be used to test Fenris services, and responses to these records are consistent to ensure stable integration tests. The data is synthetically generated, contains no personally identifying information (PII), and is not charged to your account.
🔗 See: Developer Data Collection

 

Q8: Is there a Postman collection available for Fenris APIs?
Yes, Fenris hosts a Postman collection that utilizes the Developer Data to make example requests. This can be helpful for testing and working with the APIs.
🔗 See: Postman Collection

 

Making API Requests

Q9: What is the structure of a typical Fenris API request?
Fenris APIs follow RESTful principles. A typical request includes:

  • URL: The endpoint of the specific service.
  • Method: GET or POST, depending on the endpoint.
  • Headers: Including the Authorization header with the bearer token.
  • Body: For POST requests, the body contains the data to be processed.

Additional parameters, such as query or path parameters, may be included as needed.
🔗 See: Making a Request

 

Q10: What is the ‘submission-id’ parameter used for?
The ‘submission-id’ is an optional parameter that can be included in the request header. It is echoed back in the response and can be used to track internal processes or systems associated with the request. To mark a request as a test, prefix the ‘submission-id’ value with ‘test’.
🔗 See: Submission IDs

 

Support

Q11: What should I do if I encounter issues or have questions not covered in the documentation?
If you have questions or encounter issues not addressed in the documentation, you can reach out to the Fenris support team by sending an email to [email protected].
🔗 See: Contact