SimpliFi
HomeContact Us
HomeContact Us
  1. Auth
  • Introduction
  • SimpliFi Architecture
  • Webhooks
  • Auth
    • Login to generate JWT token
      POST
  • Card Program
    • Create Card Program
      POST
    • Get Card Program
      GET
    • Change Card Program Status
      PATCH
    • Link Funding Source to Card Program
      POST
    • Get Balance of Funding Source
      GET
    • Transfer funds from one Card Program to other
      POST
    • Raise Funding Document Upload
      POST
    • Raise Funding
      POST
    • Funding Source Statement
      GET
  • Funding Source
    • Create Rule Group on Funding Account
      POST
    • Update Rule Group on Funding Account
      PUT
    • Delete Rule Group on Funding Account
      DELETE
    • Get Rule Groups on Funding Account
      GET
    • Appply Rule Group on Funding Account
      POST
    • Remove Rule Group on Funding Account
      DELETE
  • Card
    • List all Cards
      GET
    • Create a Card
      POST
    • Get Card Details
      GET
    • Retrieve Balance on the Card
      GET
    • Activate a Card
      POST
    • Manage Card Status
      POST
    • Load a Card
      POST
    • Unload a Card
      POST
    • Renewal of the Card
      POST
    • Request a Physical Card
      POST
    • Get Card Statement
      GET
    • Apply rule group on card
      POST
    • Remove rule group on card
      DELETE
  • User
    • List all Users
    • Create a User
    • Upload Document
    • Retrieve a User
    • Update a User
    • Delete a User
  • Transaction
    • List All Transactions
  • Fee
    • Add fee configuration
    • Fetch fee config
    • Change the status of fee config
    • Add Fee event against card uuid in queue
    • Apply fee against card uuid present in queue
  • Webhook
    • Get all events
    • Create a webhook
    • Update a Webhook
    • Delete a Webhook
    • Updates the status of Webhook
  1. Auth

Login to generate JWT token

POST
https://{{env}}-lb.simplifipay.com/v1/auth/login/{companyName}
The Login endpoint allows you to login to the SimpliFi platform using the provided
credentials. If you don't have the credentials already, you can request them through
this link. The endpoint returns an access token to be
used in making further API calls. Following are the properties of this endpoint.
Request Request Example
Shell
JavaScript
Java
Swift
curl --location -g --request POST 'https://uat-lb.simplifipay.com/v1/auth/login/' \
--header 'requestUuid;' \
--data-urlencode 'client_id=' \
--data-urlencode 'client_secret=' \
--data-urlencode 'grant_type='
Response Response Example
{
    "access_token": "string",
    "expires_in": "string",
    "token_type": "string"
}

Request

Path Params
companyName
string 
required
This is an internal identifier of your company in the SimpliFi platform. We will
generate the company name for you and share it. If you don't have it already,
you can request it through this link.
Header Params
requestUuid
string 
required
A unique id is required to be passed as part of the header whenever a SimpliFi API is called from your
system. This would help us in debugging in case of a discrepancy in the expected behavior of the API.
Example:
00d366f2-a6e9-4714-b172-02c4e58c29d8
Body Params application/x-www-form-urlencoded
client_id
string 
required
The values of this enumeration identify your channel for calling the endpoint.
Example: If you want to generate the access token to call subsequent APIs from
your back-end system then use the value simplifi-api-client. Allowed values
are: simplifi-ios-client, simplifi-android-client, and simplifi-api-client.
client_secret
string 
required
This is a secret identification pattern assigned to you by the SimpliFi platform.
For each allowed value of “client_id” there is a respective client secret value
shared with you before the start of the integration. Pass the respective value here.
If you don't have it already, you can request it through this link.
grant_type
string 
required
You need to pass this value to log in through the Client Secret shared by SimpliFi.
Allowed value is client_credentials. If you don't already have these credentials,
you can request them through this link.

Responses

🟢200OK
application/json
On successful operation JWT token is returned
Body
access_token
string 
required
This is the system-generated access token to be used for subsequent calls of the
same session. It is to be sent as an authorization header along with the
system-generated token type.
expires_in
string 
optional
This is the expiry date/time that defines the validity of the access token.
Note (one needs to re-login before this expiration time).
token_type
string 
optional
This field contains the token type which is coupled with access token to form
an authorization header. Accepted value is bearer.
Modified at 2025-06-27 12:44:57
Previous
Auth
Next
Card Program
Built with