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

Tackle.io Invoices API

The Invoices API from Tackle.io — 1 operation(s) for invoices.

Tackle.io Invoices API is one of 28 APIs that Tackle.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Invoices. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 1 operation across 1 path, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://contracts.tackle.io.

1 operations 1 paths 16 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.tackle.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Tackle.io Invoices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (tackleJwt). By default, every request must be authenticated.

  • tackleJwt — Tackle-issued JWT (interactive user or MTM token).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Invoices 1
GET
/v1/invoices
List Invoices
v1-get-invoices 3 params → 200400401422

Schemas 16

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

InvoicesResponse
object
2 properties 2 required
Metadata
object
Metadata for a given request
1 property 1 required
Address
object
4 properties
Money
object
2 properties 2 required
AwsCloud
string
AWS Cloud
GcpCloud
string
GCP Cloud
Customer
object
2 properties
InvoiceId
string
422Reports
object
3 properties 3 required
ReportingProduct
object
3 properties 2 required
AwsProductId
string
AWS Product Code
Transaction
object
4 properties 4 required
NetAmount
Amount to be disbursed by cloud provider after any marketplace fees have been assessed
Invoice
object
7 properties 7 required
Error
object
4 properties 3 required
GcpProductId
string
GCP Solution ID

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tackleio-invoices-api-openapi.yml Raw ↑

Other APIs Tackle.io publishes across the network.

Tackle.io Authentication API
Tackle.io Contracts API
Tackle.io Currencies API
Tackle.io Customers API
Tackle.io Disbursements API
Tackle.io Entitlements API
Tackle.io Groups API
Tackle.io Invitations API
Tackle.io Marketplace API
Tackle.io Metering API
Tackle.io Notifications API
Tackle.io Opportunities API
Where this information came from

This is an independent, third-party profile of Tackle.io Invoices 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.