How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Slash Expense Report API

The Expense Report API from Slash — 7 operation(s) for expense report.

Slash Expense Report API is one of 26 APIs that Slash publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Expense Report. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 9 operations across 7 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against a single base URL, https://api.slash.com.

9 operations 7 paths 33 schemas 3 GET2 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://api.slash.com
Authentication
API Key, API Key, HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 4

Slash Expense Report API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (api_key). An API key is passed in the header as X-API-Key (partner_api_key). It accepts HTTP bearer tokens (bearer). It accepts HTTP basic authentication (developer_application). By default, every request must be authenticated.

  • api_key — API key authentication for public API requests. Keys come in two flavors: - Legal-entity-scoped keys are pinned to a single legal entity. Minted via the dashbo…
  • partner_api_key — Partner-program API key authentication. Keys are minted in the partner dashboard (Developers → API Keys), are scoped to a single partner program, and are prefi…

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 3 GET, 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Expense Report 9
GET
/expense-report
List expense reports for your legal entity. Supports pagination, filtering by status and submitter, and sorting.
6 params → 200401403429500
POST
/expense-report
Submit a new expense report for reimbursement.
1 param body → 200401403429500
GET
/expense-report/{expenseReportId}
Get a single expense report by ID.
1 param → 200401403429500
PATCH
/expense-report/{expenseReportId}
Update an existing expense report. Can only update reports with status pendingreview. Set status to cancelled to cancel the report.
1 param body → 200401403429500
POST
/expense-report/{expenseReportId}/approve
Approve an expense report and initiate payout.
1 param body → 200401403429500
POST
/expense-report/{expenseReportId}/reject
Reject an expense report.
1 param body → 200401403429500
POST
/expense-report/receipt
Upload a receipt image for an expense report. The receipt will be parsed using AI to extract amount, date, and merchant information. Accepts PNG, JPEG, WebP, and PDF formats.
1 param body → 200401403429500
PATCH
/expense-report/bulk-action
Perform bulk actions on expense reports.
1 param body → 200401403429500
GET
/expense-report/reimbursement-sources
Get connected bank accounts for a user that can be used as reimbursement payout destinations. Pass the userId query parameter to specify which user's bank accounts to retrieve.
2 params → 200401403429500

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are slashfi.models.entity.Document.IDocumentModel.yaml (17 properties), slashfi.models.entity.ExpenseReport.ExpenseReport.yaml (16 properties), slashfi.models.entity.IUserBankAccountModel.yaml (16 properties), slashfi.models.entity.Merchant.MerchantV2.yaml (11 properties). Each schema is shown below with its type and property counts.

slashfi.models.entity.ExpenseReport.ExpenseReportMerchant.yaml
The merchant associated with an expense report (either a merchantV2 or customMerchant)
slashfi.models.entity.ExpenseReport.ExpenseReport.yaml
object
An expense report submitted by an employee for reimbursement (matches database schema)
16 properties 10 required
slashfi.models.entity.CustomMerchant.CustomMerchant.yaml
object
Custom merchant schema
5 properties 5 required
Error
object
5 properties 4 required
slashfi.models.id.CustomMerchant.CustomMerchantId.yaml
string
Represent a Custom Merchant ID in the format of "custommerchant102jifoij01"
slashfi.models.entity.ExpenseReport.ParsedReceiptDate.yaml
object
Extracted date information from a receipt
3 properties 1 required
slashfi.models.entity.ExpenseReport.ParsedReceiptMerchant.yaml
object
Extracted merchant information from a receipt
5 properties 1 required
Pagination.PaginationResponse
object
Response sent when requesting a list of data
2 properties
slashfi.models.id.ExpenseReport.ExpenseReportId.yaml
string
Represents an ExpenseReport ID in the format of "expensereport102jifoij01"
slashfi.models.entity.ExpenseReport.PublicTransactionSummary.yaml
object
A minimal transaction summary for public API responses
4 properties 4 required
slashfi.models.entity.ExpenseReport.PublicUserSummary.yaml
object
A minimal user identity for public API responses (id and name only)
2 properties 2 required
slashfi.models.entity.ExpenseReport.ExpenseReportStatus.yaml
string
The status of an expense report
slashfi.models.enums.Document.DocumentType.yaml
string
slashfi.models.entity.IUserBankAccountModel.yaml
object
16 properties 8 required
slashfi.models.id.User.yaml
string
Represent a User ID in the format of "u102jifoij01"
slashfi.models.enums.UserBankAccountStatus.yaml
string
slashfi.models.id.ExpenseReport.ExpenseReportReviewId.yaml
string
Represents an ExpenseReportReview ID in the format of "expensereportreview102jifoij01"
slashfi.models.entity.ExpenseReport.ParsedReceiptConfidence.yaml
string
Confidence level for an extracted field: - high: Clearly visible and unambiguous - medium: Readable but may have minor issues (blur, partial visibility) - low:…
slashfi.models.entity.ExpenseReport.ParsedReceiptAmount.yaml
object
Extracted amount information from a receipt
4 properties 1 required
slashfi.models.entity.IMoneyModel.yaml
object
2 properties 2 required
slashfi.models.entity.ExpenseReport.PublicExpenseReportWithMetadata.yaml
object
An expense report with enriched metadata, stripped for public API consumption
slashfi.models.entity.ExpenseReport.ReimbursementSource.yaml
A user bank account enriched with institution logo for reimbursement flows
slashfi.models.entity.ExpenseReport.ParsedReceipt.yaml
object
AI-extracted data from a receipt image or PDF
3 properties 3 required
slashfi.models.enums.Document.DocumentSource.yaml
string
slashfi.models.entity.ExpenseReport.PublicReimbursementSource.yaml
object
A minimal bank account summary for public API responses
5 properties 3 required
slashfi.models.entity.Document.DocumentStatus.yaml
string
slashfi.models.id.MerchantV2Id.yaml
string
Represent a Merchant V2 ID in the format of "merchantv2102jifoij01"
slashfi.models.entity.Document.IDocumentModel.yaml
object
17 properties 11 required
slashfi.models.entity.ExpenseReport.ExpenseReportReview.yaml
object
Review decision for an expense report
7 properties 6 required
slashfi.models.entity.IMetadataModel.yaml
object
1 property 1 required
slashfi.models.id.UserBankAccount.yaml
string
Represent a UserBankAccount ID in the format of "ub102jifoij01"
slashfi.models.id.LegalEntityId.yaml
string
Represent a Legal Entity ID in the format of "le102jifoij01"
slashfi.models.entity.Merchant.MerchantV2.yaml
object
11 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

slash-expense-report-api-openapi.yml Raw ↑

Other APIs Slash publishes across the network.

Slash Account API
Slash Agent Requests API
Slash Analytics API
Slash Card API
Slash Card Group API
Slash Card Product API
Slash Contact API
Slash Crypto API
Slash Customer API
Slash Developer Account API
Slash Developer Application API
Slash Fdx API
Where this information came from

This is an independent, third-party profile of Slash Expense Report API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.