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

Puzzle Transactions API

The Transactions API from Puzzle — 3 operation(s) for transactions.

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

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

This API exposes 6 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://staging.southparkdata.com/rest/v0, https://staging.southparkdata.com.

6 operations 4 paths 2 schemas 3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.puzzle.io/rest/v0
Authentication
OAuth 2.0, API Key
Resource Areas
1

Authentication & Security 2

Puzzle Transactions API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 4 scopes. An API key is passed in the header as Authorization (apiKey).

  • oauth2 — OAuth 2.0 with scoped access (for example read:company, read:transactions, read:report). Partner credentials are issued after the Puzzle partner technical revi…
  • apiKey — API key authentication via the Authorization header, as described in the Puzzle developer docs.

Paths & Operations 6

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

Transactions 6
GET
/company/{id}/transactions
Get Transactions
getTransactions 10 params → 200
POST
/company/{id}/transactions
Create Transactions
createTransactions 1 param body → 200
GET
/company/{id}/transactions/{transactionId}
Get Transaction
getTransaction 2 params → 200
PATCH
/company/{id}/transactions/{transactionId}
Update Transaction
updateTransaction 2 params body → 200
POST
/company/{id}/transactions/{transactionId}/document
Create Document
createTransactionDocument 2 params body → 200
GET
/rest/v0/company/{id}/transactions
List transactions
listTransactions 5 params → 200401404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Transaction (8 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Transaction
object
8 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

puzzle-transactions-api-openapi.yml Raw ↑

Other APIs Puzzle publishes across the network.

Puzzle Accounts API
Puzzle Attachments API
Puzzle Bills API
Puzzle Company API
Puzzle Customers API
Puzzle Departments API
Puzzle Documents API
Puzzle Invoices API
Puzzle JournalEntries API
Puzzle JournalEntry API
Puzzle Locations API
Puzzle Metrics API
Where this information came from

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