Rite Aid · Schema

Rite Aid EDI Transaction

An EDI transaction record for Rite Aid vendor integration using ANSI X12 standards

EDIFortune 500HealthPharmacyPrescriptionsRetail

Properties

Name Type Description
transactionSetId string ANSI X12 transaction set identifier
transactionName string Human-readable transaction name
version string ANSI X12 version
sender object Sender identification
receiver object Receiver identification
controlNumber string Interchange control number
date string Transaction date
time string Transaction time (HHMM)
status string Transaction processing status
View JSON Schema on GitHub

JSON Schema

rite-aid-edi-transaction-schema.json Raw ↑
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://github.com/api-evangelist/rite-aid/blob/main/json-schema/rite-aid-edi-transaction-schema.json",
  "title": "Rite Aid EDI Transaction",
  "description": "An EDI transaction record for Rite Aid vendor integration using ANSI X12 standards",
  "type": "object",
  "properties": {
    "transactionSetId": {
      "type": "string",
      "description": "ANSI X12 transaction set identifier",
      "enum": ["810", "820", "832", "846", "850", "855", "856", "860", "865", "997"]
    },
    "transactionName": {
      "type": "string",
      "description": "Human-readable transaction name",
      "examples": [
        "Invoice",
        "Payment Order",
        "Price/Sales Catalog",
        "Inventory Inquiry/Advice",
        "Purchase Order",
        "Purchase Order Acknowledgment",
        "Ship Notice/Manifest",
        "Purchase Order Change Request",
        "Purchase Order Change Acknowledgment",
        "Functional Acknowledgment"
      ]
    },
    "version": {
      "type": "string",
      "description": "ANSI X12 version",
      "enum": ["4010", "5010"]
    },
    "sender": {
      "type": "object",
      "description": "Sender identification",
      "properties": {
        "id": {
          "type": "string",
          "description": "EDI sender ID"
        },
        "qualifier": {
          "type": "string",
          "description": "ID qualifier"
        },
        "name": {
          "type": "string"
        }
      },
      "required": ["id", "qualifier"]
    },
    "receiver": {
      "type": "object",
      "description": "Receiver identification",
      "properties": {
        "id": {
          "type": "string",
          "description": "EDI receiver ID (Rite Aid's ID)"
        },
        "qualifier": {
          "type": "string"
        },
        "name": {
          "type": "string"
        }
      },
      "required": ["id", "qualifier"]
    },
    "controlNumber": {
      "type": "string",
      "description": "Interchange control number"
    },
    "date": {
      "type": "string",
      "format": "date",
      "description": "Transaction date"
    },
    "time": {
      "type": "string",
      "description": "Transaction time (HHMM)"
    },
    "status": {
      "type": "string",
      "description": "Transaction processing status",
      "enum": ["Pending", "Sent", "Acknowledged", "Accepted", "Rejected", "Error"]
    }
  },
  "required": ["transactionSetId", "version", "sender", "receiver", "controlNumber", "date"]
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • 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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/rite-aid-edi-transaction"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

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

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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