Emburse expense-receipts-controller API

Retrieve expense receipt PDF

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/emburse-expense-receipts-controller-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

emburse-expense-receipts-controller-api-openapi.yml Raw ↑
openapi: 3.0.0
info:
  description: Api Documentation
  version: '1.0'
  title: Api Documentation Accounts expense-receipts-controller API
  termsOfService: urn:tos
  contact: {}
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0
servers:
- url: https://service.chromeriver.com
tags:
- name: expense-receipts-controller
  description: Retrieve expense receipt PDF
paths:
  /v1/expense-receipts/{reportId}:
    get:
      tags:
      - expense-receipts-controller
      summary: Retrieve an expense receipt PDF
      description: This web service allows an external application to fetch a receipt PDF.
      operationId: getExpenseReceiptsUsingGET
      parameters:
      - name: customer-id
        in: header
        description: customer-id
        required: true
        schema:
          type: integer
          format: int32
      - name: person-id
        in: header
        description: person-id
        required: true
        schema:
          type: integer
          format: int32
      - name: reportId
        in: path
        description: reportId
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
          content:
            application/pdf:
              schema:
                type: string
                format: byte
      deprecated: false