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

TaxJar Transactions - Orders API

Order transaction management

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

This API exposes 2 JSON Schema definitions.

Tagged areas include Transactions - Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

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

Requests are made against 2 base URLs: https://api.taxjar.com/v2, https://api.sandbox.taxjar.com/v2.

5 operations 2 paths 5 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.taxjar.com/v2/
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

TaxJar Transactions - Orders API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Use your TaxJar API token. Format: "Bearer [token]" or "Token token=[token]"

Paths & Operations 5

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

Transactions - Orders 5

Order transaction management

GET
/transactions/orders
List order transactions
listOrders 4 params → 200401
POST
/transactions/orders
Create an order transaction
createOrder body → 201400401422
GET
/transactions/orders/{transaction_id}
Show an order transaction
showOrder 2 params → 200401404
PUT
/transactions/orders/{transaction_id}
Update an order transaction
updateOrder 1 param body → 200400401404
DELETE
/transactions/orders/{transaction_id}
Delete an order transaction
deleteOrder 2 params → 200401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Order (19 properties), OrderRequest (19 properties), LineItem (8 properties), LineItemRequest (8 properties). Each schema is shown below with its type and property counts.

LineItemRequest
object
8 properties
OrderRequest
object
19 properties 8 required
Error
object
3 properties
Order
object
19 properties
LineItem
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

taxjar-transactions-orders-api-openapi.yml Raw ↑

Other APIs TaxJar publishes across the network.

TaxJar Categories API
TaxJar Customers API
TaxJar Nexus API
TaxJar Rates API
TaxJar Summary Rates API
TaxJar Taxes API
TaxJar Transactions - Refunds API
TaxJar Validations API
Where this information came from

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