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

Soldo Expense Review Processes API

The Expense Review Processes API from Soldo — 5 operation(s) for expense review processes.

Soldo Expense Review Processes API is one of 47 APIs that Soldo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Expense Review Processes. 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 8 operations across 5 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 5.56.0.

Requests are made against 2 base URLs: https://api.soldo.com, https://api-demo.soldocloud.net.

8 operations 5 paths 21 schemas 1 DELETE2 GET3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.56.0
Base URL
https://api.soldo.com/business/v2
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Soldo Expense Review Processes API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (standardAuth) using the clientCredentials flow, exposing 44 scopes.

  • standardAuth — This API uses OAuth 2 with the "Client Credentials" grant flow.

Paths & Operations 8

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

Expense Review Processes 8
GET
/business/v2/expense-review/processes
Search Expense Review Processes
expense-review-processes-search 5 params → 200400
POST
/business/v2/expense-review/processes
Add Expense Review Process
expense-review-process-add body → 200400404
POST
/business/v2/expense-review/processes/priority
Change Expense Review Processes Priority
expense-review-process-priority-change body → 204400404
GET
/business/v2/expense-review/processes/{processId}
Get Expense Review Process
expense-review-process-get 1 param → 200404
PUT
/business/v2/expense-review/processes/{processId}
Update Expense Review Process
expense-review-process-update 1 param body → 200400404
DELETE
/business/v2/expense-review/processes/{processId}
Delete Expense Review Process
expense-review-process-delete 1 param → 204404
POST
/business/v2/expense-review/processes/recalculate
Recalculate Expense Review Process
expense-review-process-recalculate body → 204400404
PUT
/business/v2/expense-review/processes/{processId}/status
Update Expense Review Process Status
expense-review-process-status-update 1 param body → 200400404

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are ExpenseReviewProcess (8 properties), ExpenseReviewProcesses (6 properties), ExpenseReviewProcessItems (6 properties), UpdateExpenseReviewProcess (4 properties). Each schema is shown below with its type and property counts.

ExpenseReviewProcessStatusSearch
string
The status of the ExpenseReviewProcess.
ExpenseReviewProcess
object
8 properties 6 required
ExpenseReviewProcessStepStatus
string
ExpenseReviewProcessCondition
object
2 properties 2 required
ExpenseReviewProcesses
object
6 properties
ExpenseReviewProcessComparator
string
ExpenseReviewProcessAutomationRule
object
3 properties 2 required
UpdateExpenseReviewProcess
object
Update ExpenseReviewProcessStatus JSON parameters.
4 properties 4 required
ExpenseReviewProcessStatus
string
CreateExpenseReviewProcess
object
Create ExpenseReviewProcess JSON parameters.
4 properties 4 required
RecalculateExpenseReviewProcess
object
Recalculate ExpenseReviewProcess JSON parameters.
1 property 1 required
UpdateExpenseReviewProcessStatus
object
Update ExpenseReviewProcessStatus JSON parameters.
1 property 1 required
ExpenseReviewProcessItems
object
6 properties
ExpenseReviewProcessReviewerType
string
ExpenseReviewProcessChangeStatus
string
ExpenseReviewProcessAmountCondition
object
2 properties 2 required
ExpenseReviewProcessPriorities
object
2 properties 2 required
ExpenseReviewProcessPriority
object
Change ExpenseReviewProcess priority JSON parameters.
1 property 1 required
ExpenseReviewProcessStep
object
4 properties 2 required
ExpenseReviewProcessReviewerInfo
object
1 property 1 required
ExpenseReviewProcessConditionType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

soldo-expense-review-processes-api-openapi.yml Raw ↑

Other APIs Soldo publishes across the network.

Soldo Accounting Classification API
Soldo Addresses API
Soldo Authentication API
Soldo Auto-Transfer Presets API
Soldo Autotags API
Soldo Business Trips API
Soldo Card Rules API
Soldo Card Rules Presets API
Soldo Cards API
Soldo Company API
Soldo Contacts API
Soldo Documents API
Where this information came from

This is an independent, third-party profile of Soldo Expense Review Processes 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.