Vendasta

Vendasta change_spend API

The Change Spend APIs allow interact with change spend requests, like resolving them by approving or rejecting

Documentation GitHub OpenAPI

Operations 1

POST /change_spend/resolve Resolve a Change Spend Request - by approving or rejecting

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/vendasta/refs/heads/main/openapi/vendasta-change-spend-api-openapi.yml

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/vendasta-change-spend-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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  version: '1.0'
  title: Vendasta Marketplace API V1 Endpoints account Change Spend API
  description: The Account APIs allow you to perform actions against a single account that your application has been added to.
servers:
- url: https://developers.vendasta.com/api/v1
  description: Production Server
- url: https://developers-demo.vendasta.com/api/v1
  description: Demo Server
security:
- BearerAuth: []
tags:
- name: change_spend
  description: The Change Spend APIs allow interact with change spend requests, like resolving them by approving or rejecting
paths:
  /change_spend/resolve:
    parameters: []
    post:
      tags:
      - change_spend
      responses:
        '200':
          description: Accepted
        '400':
          description: Bad request - invalid parameters in the body of the request
        '401':
          description: Invalid authentication
        '403':
          description: Permission denied
        '500':
          description: Internal server error
      summary: Resolve a Change Spend Request - by approving or rejecting
      requestBody:
        content:
          application/json:
            schema:
              type: object
              required:
              - activation_id
              - account_id
              - approved
              - change_request_id
              properties:
                activation_id:
                  type: string
                  description: A unique ID that can be used to identify a specific activation record related to the change spend.
                account_id:
                  type: string
                  description: A unique ID that can be used to identify an account.
                item_id:
                  type: string
                  description: Field for specifying the add-on ID if the change request is for an add-on.
                approved:
                  type: boolean
                  description: A boolean value representing whether the change spend has been approved or rejected.
                change_request_id:
                  type: string
                  description: A unique ID that can be used to identify the change spend.
                rejection_reason:
                  type: string
                  description: If approved is false, you must give a reason for rejecting the change spend.
        required: true
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer