Merge · Schema

ExpenseReportRequest

# The ExpenseReport Object ### Description The `ExpenseReport` object represents a collection of expenses submitted for review and reimbursement. It includes details about the submitter, status, amounts, and associated metadata. ### Usage Example Fetch from the `GET ExpenseReport` endpoint to view details of expense reports and their line items.

IntegrationPlatformUnified-APIAgent HandlerLLM Gateway

Properties

Name Type Description
report_date stringnull The date of the expense report.
report_identifier stringnull Human-readable expense report identifier.
employee stringnull Identifier for the employee who submitted or is associated with the expense report
status object Overall status of the expense report. One of DRAFT, SUBMITTED, APPROVED, REJECTED
total_amount numbernull Total amount of the expense report
currency object Currency code for the expense report. The currency code in ISO 4217 format.
description stringnull A brief description or purpose for the expense report
accounting_period stringnull The accounting period the report was posted in
company stringnull The subsidiary that the expense report is created in
tracking_categories array The related tracking categories associated with the expense report
integration_params objectnull
linked_account_params objectnull
remote_fields array
View JSON Schema on GitHub

JSON Schema

merge-expensereportrequest-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "#/components/schemas/ExpenseReportRequest",
  "title": "ExpenseReportRequest",
  "type": "object",
  "properties": {
    "report_date": {
      "type": [
        "string",
        "null"
      ],
      "format": "date-time",
      "description": "The date of the expense report."
    },
    "report_identifier": {
      "type": [
        "string",
        "null"
      ],
      "description": "Human-readable expense report identifier."
    },
    "employee": {
      "type": [
        "string",
        "null"
      ],
      "format": "uuid",
      "description": "Identifier for the employee who submitted or is associated with the expense report"
    },
    "status": {
      "oneOf": [
        {
          "$ref": "#/components/schemas/ExpenseReportStatusEnum"
        },
        {
          "type": "null"
        }
      ],
      "description": "Overall status of the expense report. One of DRAFT, SUBMITTED, APPROVED, REJECTED"
    },
    "total_amount": {
      "type": [
        "number",
        "null"
      ],
      "format": "double",
      "description": "Total amount of the expense report"
    },
    "currency": {
      "oneOf": [
        {
          "$ref": "#/components/schemas/TransactionCurrencyEnum"
        },
        {
          "type": "null"
        }
      ],
      "description": "Currency code for the expense report. The currency code in ISO 4217 format."
    },
    "description": {
      "type": [
        "string",
        "null"
      ],
      "description": "A brief description or purpose for the expense report"
    },
    "accounting_period": {
      "type": [
        "string",
        "null"
      ],
      "format": "uuid",
      "description": "The accounting period the report was posted in"
    },
    "company": {
      "type": [
        "string",
        "null"
      ],
      "format": "uuid",
      "description": "The subsidiary that the expense report is created in"
    },
    "tracking_categories": {
      "type": "array",
      "items": {
        "type": "string",
        "format": "uuid"
      },
      "description": "The related tracking categories associated with the expense report"
    },
    "integration_params": {
      "type": [
        "object",
        "null"
      ],
      "additionalProperties": {
        "description": "Any type"
      }
    },
    "linked_account_params": {
      "type": [
        "object",
        "null"
      ],
      "additionalProperties": {
        "description": "Any type"
      }
    },
    "remote_fields": {
      "type": "array",
      "items": {
        "$ref": "#/components/schemas/RemoteFieldRequest"
      }
    }
  },
  "required": [
    "tracking_categories"
  ],
  "description": "# The ExpenseReport Object\n### Description\nThe `ExpenseReport` object represents a collection of expenses submitted for review and reimbursement.\nIt includes details about the submitter, status, amounts, and associated metadata.\n\n### Usage Example\nFetch from the `GET ExpenseReport` endpoint to view details of expense reports and their line items."
}

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/merge-expensereportrequest"
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.