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

Remote Expenses API

Employee expense reimbursements

Remote Expenses API is one of 40 APIs that Remote publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Expenses. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 4 JSON Schemas.

This API exposes 7 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2026-05-22.

Requests are made against 2 base URLs: https://gateway.remote.com/v1, https://gateway.remote-sandbox.com/v1.

7 operations 4 paths 5 schemas 1 DELETE2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-05-22
Base URL
https://gateway.remote.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Remote Expenses API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 7

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

Expenses 7

Employee expense reimbursements

GET
/expenses
List Expenses
listExpenses 2 params → 200
POST
/expenses
Create An Expense
createExpense body → 201
GET
/expenses/{expense_id}
Show An Expense
showExpense 1 param → 200
PATCH
/expenses/{expense_id}
Update An Expense
updateExpense 1 param body → 200
DELETE
/expenses/{expense_id}
Delete An Expense
deleteExpense 1 param → 204
POST
/expenses/{expense_id}/approve
Approve An Expense
approveExpense 1 param → 200
POST
/expenses/{expense_id}/decline
Decline An Expense
declineExpense 1 param body → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Expense (9 properties), ExpenseCreateRequest (7 properties), ExpenseEnvelope (1 property), ExpenseList (1 property). Each schema is shown below with its type and property counts.

ExpenseStatus
string
ExpenseCreateRequest
object
7 properties 5 required
ExpenseList
object
1 property
ExpenseEnvelope
object
1 property
Expense
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

remote-com-expenses-api-openapi.yml Raw ↑

Other APIs Remote publishes across the network.

Remote Webhooks
Remote Benefit Offers API
Remote Benefit Renewals API
Remote Billing Documents API
Remote Companies API
Remote Company Currencies API
Remote Company Managers API
Remote Company Structure API
Remote Compliance API
Remote Contract Amendments API
Remote Contract Documents API
Remote Contract Eligibility API
Where this information came from

This is an independent, third-party profile of Remote Expenses 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.