Salesforce · JSON Structure

Salesforce Transaction Journals Simulation Request Structure

Type: object Properties: 2 Required: 2

Fortune 500Artificial IntelligenceAnalyticsCloudCommerceCRMCustomer ServiceEnterpriseMarketingPlatformSales

TransactionJournalsSimulationRequest is a JSON Structure definition published by Salesforce, describing 2 properties, of which 2 are required. It conforms to the https://json-structure.org/draft/2020-12/schema meta-schema.

Properties

transactionJournals runSetting

Meta-schema: https://json-structure.org/draft/2020-12/schema

JSON Structure

{
  "type": "object",
  "name": "TransactionJournalsSimulationRequest",
  "properties": {
    "transactionJournals": {
      "type": "array",
      "description": "",
      "items": {
        "type": "object",
        "properties": {
          "CurrencyIsoCode": {
            "type": "string"
          },
          "ActivityDate": {
            "type": "string"
          },
          "JournalDate": {
            "type": "string"
          },
          "Brand": {
            "type": "string"
          },
          "Establishment": {
            "type": "string"
          },
          "ExternalTransactionNumber": {
            "type": "string"
          },
          "JournalTypeId": {
            "type": "string"
          },
          "LoyaltyProgramId": {
            "type": "string"
          },
          "MemberId": {
            "type": "string"
          },
          "TransactionAmount": {
            "type": "string"
          },
          "TransactionLocation": {
            "type": "string"
          },
          "VoucherCode": {
            "type": "string"
          },
          "Origin": {
            "type": "string"
          },
          "Distance": {
            "type": "string"
          },
          "Destination": {
            "type": "string"
          },
          "FlightNumber": {
            "type": "string"
          },
          "Status": {
            "type": "string"
          }
        },
        "required": [
          "CurrencyIsoCode",
          "ActivityDate",
          "JournalDate",
          "Brand",
          "Establishment",
          "ExternalTransactionNumber",
          "JournalTypeId",
          "LoyaltyProgramId",
          "MemberId",
          "TransactionAmount",
          "TransactionLocation",
          "VoucherCode",
          "Origin",
          "Distance",
          "Destination",
          "FlightNumber",
          "Status"
        ]
      }
    },
    "runSetting": {
      "type": "object",
      "properties": {
        "isSimulation": {
          "type": "boolean"
        }
      },
      "required": [
        "isSimulation"
      ]
    }
  },
  "required": [
    "transactionJournals",
    "runSetting"
  ],
  "$schema": "https://json-structure.org/draft/2020-12/schema"
}

Work with this as data

Every JSON Structure 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 json structure

4 MCP tools reach this

find_json_structuresBrowse and filter every JSON Structure 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 Structure

curl "https://apis.io/api/v1/json-structures/salesforce-transaction-journals-simulation-request-structure"

All json structure

curl "https://apis.io/api/v1/json-structures?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.

GitHub Google LinkedIn

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