FuseMetrix — Internal

9 endpoints. Server: https://api.tunnelflight.com/api

Each endpoint below includes parameters, an example payload, a copyable curl command, and a link to the originating .bru source on GitHub.

List User

GET /external/fuse-metrix/op

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


null

Responses

2XX — Successful response

Try it


curl --request GET \  --url 'https://api.tunnelflight.com/api/external/fuse-metrix/op'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'

View source on GitHub →

Create User

POST /external/fuse-metrix/op

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


{
  "email": "vivekthumar@gmail.com"
}

Responses

2XX — Successful response

Try it


curl --request POST \  --url 'https://api.tunnelflight.com/api/external/fuse-metrix/op'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'  \
  --header 'content-type: application/json'  \
  --data '{"email":"vivekthumar@gmail.com"}'

View source on GitHub →

Edit User

PUT /external/fuse-metrix/op

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


{
  "email": "vivekthumar@gmail.com2",
  "id": 7
}

Responses

2XX — Successful response

Try it


curl --request PUT \  --url 'https://api.tunnelflight.com/api/external/fuse-metrix/op'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'  \
  --header 'content-type: application/json'  \
  --data '{"email":"vivekthumar@gmail.com2","id":7}'

View source on GitHub →

Get One

GET /external/fuse-metrix/op/{id}

Path parameters

Name	Type	Required	Description
`id`	string	yes	Example: `7`

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


null

Responses

2XX — Successful response

Try it


curl --request GET \  --url 'https://api.tunnelflight.com/api/external/fuse-metrix/op/{id}'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'

View source on GitHub →

Delete User

DELETE /external/fuse-metrix/op/{id}

Path parameters

Name	Type	Required	Description
`id`	string	yes	Example: `7`

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


null

Responses

2XX — Successful response

Try it


curl --request DELETE \  --url 'https://api.tunnelflight.com/api/external/fuse-metrix/op/{id}'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'

View source on GitHub →

Get Bookings list

POST /admin/reports/external/fuse-metrix/bookings

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


{
  "limit": 10,
  "offset": 0
}

Responses

2XX — Successful response

Try it


curl --request POST \  --url 'https://api.tunnelflight.com/api/admin/reports/external/fuse-metrix/bookings'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'  \
  --header 'content-type: application/json'  \
  --data '{"limit":10,"offset":0}'

View source on GitHub →

Get History list

POST /admin/reports/external/fuse-metrix/history

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


{
  "limit": 10,
  "offset": 0
}

Responses

2XX — Successful response

Try it


curl --request POST \  --url 'https://api.tunnelflight.com/api/admin/reports/external/fuse-metrix/history'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'  \
  --header 'content-type: application/json'  \
  --data '{"limit":10,"offset":0}'

View source on GitHub →

POST /auth/login

Login Endpoint

The /auth/login endpoint is used to authenticate users by validating their credentials. Upon successful authentication, it returns a token and other relevant information.

Request

Method

POST

URL

{{host}}/auth/login

Request Body

The request body must be in JSON format and contain the following parameters:

username (string): The username of the user attempting to log in.
password (string): The password associated with the username.

Example Request Body


{
  "username": "your_username",
  "password": "your_password"
}

Response

Status Code

200 OK: Indicates that the login was successful.

Response Body

The response is returned in JSON format and contains the following fields:

status (boolean): Indicates whether the login attempt was successful.
token (string): The authentication token to be used for subsequent requests.
confirmationPending (integer): Indicates if there is any pending confirmation for the user.
message (string): A message providing additional information about the login attempt.
member_id (integer): The unique identifier for the logged-in user.

Example Response Body


{
  "status": true,
  "token": "your_token",
  "confirmationPending": 0,
  "message": "",
  "member_id": 0
}

Notes

Ensure that the username and password are correct to avoid authentication failures.
The token returned in the response should be stored securely and used in the Authorization header for subsequent API requests.
If the login fails, the response will still return a JSON object, but the status will be false and may include an error message.

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.

Request body

Request body example (default)


{
  "username": "",
  "password": ""
}

Responses

2XX — Successful response

Try it


curl --request POST \  --url 'https://api.tunnelflight.com/api/auth/login'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'content-type: application/json'  \
  --data '{"username":"","password":""}'

View source on GitHub →

Token Generate

POST /external/fuse-metrix/op/generate-token

Generate Token Endpoint

This endpoint is used to generate a token for a member based on their credentials. It requires a POST request to the specified URL.

Request Parameters

The request body must be sent in JSON format and includes the following parameters:

member_id (integer): The unique identifier for the member. This is required to identify the member for whom the token is being generated.
member_pin (string): The PIN associated with the member. This is used for authentication purposes.

Request Example


{
  "member_id": 40,
  "member_pin": "12345"
}

Expected Response

Upon a successful request, the API responds with a JSON object containing the following fields:

status (boolean): Indicates the success or failure of the token generation process.
message (string): A message providing additional information about the request status. This may be empty if there are no issues.
token (string): The generated token that can be used for subsequent authenticated requests.

Response Example


{
  "status": true,
  "message": "",
  "token": "your_generated_token_here"
}

Notes

Ensure that the member_id and member_pin are valid and correctly formatted to avoid authentication errors.
The generated token should be stored securely and used in future requests that require authentication.

Headers

Name	Type	Required	Description
`Authorization`	string	yes	Bearer token. Required for every request.
`client-id`	string	yes	Client identifier issued by IBA. Required for every request.
`token`	string	no

Request body

Request body example (default)


{
  "member_id": 60649,
  "purchase_id": 123456789,
  "purchase_date": 1758785400,
  "flight_date": 1758713400,
  "minutes_booked": 5,
  "product_id": 5,
  "tunnel_id": 225,
  "checkin_time": 1758782700,
  "registration_id": 0
}

Responses

2XX — Successful response

Try it


curl --request POST \  --url 'https://api.tunnelflight.com/api/external/fuse-metrix/op/generate-token'  \
  --header 'Authorization: Bearer <token>'  \
  --header 'client-id: <client-id>'  \
  --header 'token: <token>'  \
  --header 'content-type: application/json'  \
  --data '{"member_id":60649,"purchase_id":123456789,"purchase_date":1758785400,"flight_date":1758713400,"minutes_booked":5,"product_id":5,"tunnel_id":225,"checkin_time":1758782700,"registration_id":0}'

View source on GitHub →