Fusion RESTful APIs use HTTPS to serve API requests and acknowledge them with appropriate status codes. Each API is supplemented with syntax, description, and examples, helping you build your banking product seamlessly.
Standard HTTP verbs/methods are used to make requests to Fusion server.
- POST method: used to both create and update a resource
- GET method: used to retreive resource details
- PUT method: used to update resource details
- PATCH method:
- DELETE method: used to delete a resource
All Fusion API requests and responses are in the JSON data format. Hence, it is mandatory to specify the header parameter-
application/json when making requests.
APIs on Fusion are versioned using URI path versioning—API version is included in the endpoint URI in the format vX, where X is the version number. APIs are up-versioned when a breaking change is made, like change in the response data format for one or more requests.
Fusion APIs are idempotent. Making repeated requests will not change the result beyond the first try. This prevents duplication and also allows you to safely retry a request in case of failure. Fusion platform supports unique idempotent key for each API request.
All POST API calls support idempotency; and GET and DELETE calls are idempotent by definition.
Fusion uses OAuth with bearer tokens to authenticate and authorize API requests. Fusion uses the tokens to identify the calling application/user and also verifies if they have the necessary permission to make the request. Tokens are provided to you on request and carry an expiration. To use your token, assign it to X-Zeta-AuthToken parameter in the authorization header when making requests. All API requests must be made over HTTPS; requests over HTTP and without authentication token will fail.
Service Uptime Dashboard publishes status information of Zeta’s customer services. The status page consists of three sections:
Uptime Showcase: For every individual service, a color-coded bar displays the daily status and overall uptime percentage over a 90-day period. You can also view historical service availability segregated month-wise.
System Metrics: Daily, weekly and monthly performance report of individual service based on response time.
Past Incidents: Incidents reported over a 15-day period are listed in this section. You can also view history of reported incidents segregated month-wise.
You can subscribe to status updates via email, SMS, or Atom/RSS feeds to receive notifications regarding incidents reported for various services.
In the current release, Zeta Support will help you with Fusion uptime service reports.