ConnexPay Purchase Event History API

The PurchaseEventHistory API from ConnexPay — 1 operation(s) for purchaseeventhistory.

Business capability
Webhook & Event Subscription Management BC-4270.80

Operations 1

POST /api/v1/PurchaseEventHistory/Resend Purchase Event History (Replay Webhooks) #

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-purchaseeventhistory-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-purchaseeventhistory-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: purchases-api Purchase Event History API
  version: '1.0'
servers:
- url: https://sandboxpurchasesapi.connexpay.com
security:
- sec0: []
tags:
- name: PurchaseEventHistory
paths:
  /api/v1/PurchaseEventHistory/Resend:
    post:
      summary: Purchase Event History (Replay Webhooks)
      description: Call this endpoint to receive VCC, Lodged Card, Physical Card or ACH purchase events either by unique Guid or for a specified date range. If you subscribe to webhooks and are concerned you may be missing events, this endpoint can retrieve past events.
      operationId: purchase-event-history
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                SourceGuid:
                  type: string
                  description: The unique card guid associated with a particular purchase.  This would be the original card guid returned on your virtual card, lodged card, physical card or ACH issue call.
                MerchantGuid:
                  type: string
                  description: Include your Merchant Guid instead of the Source Guid if you want to see all events for a given date range (you must also include the date range parameters)
                EventGuid:
                  type: string
                  description: Transaction ID as displayed in Bridge
                FromDateTime:
                  type: string
                  description: From date
                  format: date
                ToDateTime:
                  type: string
                  description: To date
                  format: date
      responses:
        '200':
          description: '200'
          content:
            application/json:
              examples:
                Request by SourceGuid:
                  value: '"Your request has been received and will be processed"'
              schema:
                type: string
                example: Your request has been received and will be processed
        '400':
          description: '400'
          content:
            application/json:
              examples:
                Result:
                  value: '{}'
              schema:
                type: object
                properties: {}
      deprecated: false
      tags:
      - PurchaseEventHistory
components:
  securitySchemes:
    sec0:
      type: http
      scheme: basic
x-readme:
  headers:
  - key: Authorization
    value: Basic <JWT>
  explorer-enabled: false
  proxy-enabled: true
x-readme-fauxas: true