# Overview

FIP Module will host set of ReBIT API that the AA will call from their Backend. Those APIs are defined here <https://api.rebit.org.in/spec/fip> you will have to implement 2.0.0 version or 2.1.0 for Insurance FIPs

Your FIP module will further call your CBS to discover accounts and fetch data.

**Central Registry FIP Entity Onboarding**

You can follow the steps here [create-fiu-entity](https://docs.saafe.in/central-registry/create-fiu-entity "mention") to create an FIP entity as well. Just select FIP instead of FIU

### **(CR) Central Registry APIs**

Ref- [central-registry-apis](https://docs.saafe.in/central-registry/central-registry-apis "mention")

Central Registry host a list of APIs that you can use

1\.      Token Generation API

2\.      AA List

When you are making API call to the AA you need to pass the token generated in the CR to be sent in the header as fip\_api\_key

### **Detached JWS Signature**

All API response that you are sending needs to have the x-jws-signature refer - [jws-signature](https://docs.saafe.in/fiu-module/jws-signature "mention")

### End-to-end encryption of Data Request

Ref - <https://github.com/Sahamati/rahasya>

Note: The 2.0.0 ReBIT version requires you to support both curve25519 and X25519 curve of ECDH