Azupay Billing and Transaction Reports API

Fetch transaction, billing and other reports.

Operations 2

GET /report Get Reports #
GET /report/download Get Report download Url #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/azupay-billing-and-transaction-reports-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

azupay-billing-and-transaction-reports-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Azupay Reports & Balance Billing and Transaction Reports API
  description: API Reference
  version: v1
  contact:
    email: contactus@azupay.com.au
servers:
- url: https://api-uat.azupay.com.au/v1
  description: UAT environment
- url: https://api.azupay.com.au/v1
  description: Production environment
tags:
- name: Billing and Transaction Reports
  description: 'Fetch transaction, billing and other reports.

    '
paths:
  /report:
    get:
      operationId: getReport
      security:
      - SecretKey: []
      tags:
      - Billing and Transaction Reports
      summary: Get Reports
      description: "Provides a list of reports that can be passed onto GET /report/download API endpoint. You can supply \n`month + timezone` query parameters OR you can supply `fromDate + toDate`. The former provides you a list of all \nreports automatically generated by azupay whilst the latter provides you with a report for the date range \nspecified.\n\nBecause `fromDate` and `toDate` contain special HTML entities (i.e. `:` and `+`), they must be encoded.\nExample: `2022-06-02T12:11:00.999+0530` must be supplied as `2022-06-02T12%3A11%3A00.999%2B0530`\n"
      parameters:
      - description: 'Your clientId

          '
        in: query
        name: clientId
        required: true
        schema:
          type: string
      - description: 'The year and month

          '
        in: query
        name: month
        required: false
        schema:
          type: string
          pattern: ^\d{4}-\d{2}$
          example: 2020-01
      - description: 'The fromDate in ISO8601 and encoded.


          e.g. `2022-06-02T12%3A11%3A00.999%2B0530` instead of `2022-06-02T12:11:00.999+0530`

          '
        in: query
        name: fromDate
        required: false
        schema:
          type: string
      - description: 'The toDate in ISO8601 and encoded.


          e.g. `2022-07-02T12%3A11%3A00.999%2B0530` instead of `2022-07-02T12:11:00.999+0530`

          '
        in: query
        name: toDate
        required: false
        schema:
          type: string
      - description: 'The timezone to apply on date/time stamps. Currently only `Australia/Sydney` supported.

          '
        in: query
        name: timezone
        required: false
        schema:
          type: string
          enum:
          - Australia/Sydney
      responses:
        '200':
          description: The list of reports available for the specified clientId and month
          content:
            application/json:
              schema:
                allOf:
                - $ref: '#/components/schemas/ReportListModel'
        '403':
          description: Not authorised to return reports for given clientId
          content:
            application/json:
              schema:
                allOf:
                - $ref: '#/components/schemas/ErrorModel'
        '404':
          description: No reports were found for given clientId and month values
          content:
            application/json:
              schema:
                allOf:
                - $ref: '#/components/schemas/ErrorModel'
  /report/download:
    get:
      operationId: downloadReport
      tags:
      - Billing and Transaction Reports
      summary: Get Report download Url
      description: Gets a time limited link to download the specified report
      parameters:
      - description: 'Your clientId

          '
        in: query
        name: clientId
        required: true
        schema:
          type: string
      - description: 'The reportId returned from the call to `/report` operation

          '
        in: query
        name: reportId
        required: true
        schema:
          type: string
      responses:
        '200':
          description: The report link object
          content:
            application/json:
              schema:
                allOf:
                - $ref: '#/components/schemas/ReportLinkModel'
        '403':
          description: Not authorised to retrieve a link for the specified report
          content:
            application/json:
              schema:
                allOf:
                - $ref: '#/components/schemas/ErrorModel'
        '404':
          description: The specified reportId was not found
          content:
            application/json:
              schema:
                allOf:
                - $ref: '#/components/schemas/ErrorModel'
      security:
      - SecretKey: []
components:
  schemas:
    ReportLinkModel:
      type: object
      properties:
        reportUrl:
          type: string
      required:
      - reportUrl
    fromDateWithTZO:
      type: string
      pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}[+\-]\d{2}:\d{2}$
      description: The report date in ISO date/time string format with timezone offset
      example: '2020-01-01T00:00:00.004+11:00'
    toDateWithTZO:
      type: string
      pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}[+\-]\d{2}:\d{2}$
      description: The report date in ISO date/time string format with timezone offset
      example: '2020-01-01T00:00:00.004+11:00'
    ReportListModel:
      type: object
      properties:
        month:
          type: string
          pattern: ^\d{4}-\d{2}$
          example: 2020-01
        reports:
          type: array
          items:
            type: object
            properties:
              reportId:
                type: string
              type:
                type: string
                enum:
                - MT940
                - Transaction Report
                - Billing Report
              fromDate:
                $ref: '#/components/schemas/fromDateWithTZO'
              toDate:
                $ref: '#/components/schemas/toDateWithTZO'
              clientId:
                type: string
              moreResultsPossible:
                type: boolean
                description: "Optional field. Only applicable if `startDate` and `endDate` are supplied.\n\n**true** if the provided range (`startDate` - `endDate`) resulted in report's result-set that \nexceed the allowed maximum records (10,000)\n\nWhen it is true, our recommendation is to narrow the range (`startDate` - `endDate`) and retry\n"
            required:
            - reportId
            - type
            - fromDate
            - toDate
            - clientId
    ErrorModel:
      type: object
      additionalProperties: false
      required:
      - message
      properties:
        message:
          type: string
        details:
          type: object
          additionalProperties: false
          properties:
            failureCode:
              type: string
            failureReason:
              type: string
          required:
          - failureCode
          - failureReason
  securitySchemes:
    SecretKey:
      description: 'The secret key is used to access restricted functions and should be stored

        securely in your system. It is required for operations which may result in

        additional charges to you as a merchant. Please protect the key by storing

        it encrypted granting access only to a limited set of users and applications

        requiring its use.

        '
      in: header
      name: Authorization
      type: apiKey
    DistributableKey:
      description: 'The distributable key has limited access and may be exposed publicly to

        your payers.

        '
      in: header
      name: Authorization
      type: apiKey