Skip to main content
The Resource Server is your application’s data API — responsible for exposing customer data after a user has given consent. Fiskil handles authorization, token issuance, and consent orchestration. During the consent process and once a user has approved access, Fiskil calls your Resource Server with a JWT. Your job is to validate that token and return the right data.

​
How It Works

The diagram below illustrates the complete Resource Server integration flow:

​
Example Data Endpoint

At least one endpoint that exposes real data is required to test and go live. The API must start with /customer/{customerId} so we fetch data for the customer who has granted the consent.

​
GET /customer/{customerId}/accounts/{id}/balances

Returns the account balance. Example response: 
{
  "account_id": "acc_001",
  "available": 1200.50,
  "current": 1250.75,
  "currency": "AUD"
}
You can return mock data during the initial testing phase.

​
Next Steps