ConnexPay Sale Event History API

The SaleEventHistory API from ConnexPay — 1 operation(s) for saleeventhistory.

Operations 1

POST /api/v1/SaleEventHistory/Resend Sales Event History #

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/connexpay-saleeventhistory-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

connexpay-saleeventhistory-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: sales-api Sale Event History API
  version: '1.0'
servers:
- url: https://sandboxsalesapi.connexpay.com
security:
- sec0: []
tags:
- name: SaleEventHistory
paths:
  /api/v1/SaleEventHistory/Resend:
    post:
      summary: Sales Event History
      description: Call this endpoint to retrieve Credit Card or ACH Sales Events
      operationId: sales-event-history
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                SourceGuid:
                  type: string
                  description: The unique Sales GUID for a particular sale.
                MerchantGuid:
                  type: string
                  description: Include your Merchant Guid instead of the Sale Guid if you want to see all events for a given date range (you must also include the date range to include)
                FromDateTime:
                  type: string
                  description: Beginning date range
                  format: date
                ToDateTime:
                  type: string
                  description: Ending date range
                  format: date
      responses:
        '200':
          description: '200'
          content:
            application/json:
              examples:
                Request body with Sale Guid:
                  value: '{

                        "SourceGuid": "A3EEC280-CB18-48D3-8C95-EA9A29B66429",

                    }'
        '400':
          description: '400'
          content:
            application/json:
              examples:
                Result:
                  value: '{}'
              schema:
                type: object
                properties: {}
      deprecated: false
      tags:
      - SaleEventHistory
components:
  securitySchemes:
    sec0:
      type: oauth2
      flows: {}
x-readme:
  headers: []
  explorer-enabled: false
  proxy-enabled: false
x-readme-fauxas: true