Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tackle Invoices API

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

Tackle Invoices API is one of 25 APIs that Tackle 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.0.3, at version 1.0.0.

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

1 operations 1 paths 16 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.tackle.io
Authentication
HTTP Bearer, HTTP Basic, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 4

Tackle Invoices API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). It accepts HTTP basic authentication (BasicAuthCallback). An API key is passed in the header as subscription-key (HeaderApiKeyAuthCallback). It supports OAuth 2.0 (Oauth2AuthCallback) using the clientCredentials flow.

  • BearerAuth — The Tackle API requires a JWT for authentication. You can get this by [getting your API credentials](https://developers.tackle.io/docs/how-to-get-an-m2m-client…
  • BasicAuthCallback — Use basic for [basic HTTP authentication](https://en.wikipedia.org/wiki/Basicaccessauthentication); this is only used for callbacks
  • HeaderApiKeyAuthCallback — Use headerapikey to specify a custom HTTP request header for authentication. Requests from Tackle will use the specified HTTP header for outbound requests to y…
  • Oauth2AuthCallback — This auth-type is for oauth2 client credentials flow. We will use the clientid and clientsecret to call the tokenurl to get an access token; this is only used…

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), Transaction (4 properties), Error (4 properties). Each schema is shown below with its type and property counts.

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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tackle-invoices-api-openapi.yml Raw ↑

Other APIs Tackle publishes across the network.

Tackle Authentication API
Tackle Contracts API
Tackle Currencies API
Tackle Disbursements API
Tackle Entitlements API
Tackle Groups API
Tackle Invitations API
Tackle Marketplace API
Tackle Metering API
Tackle Notifications API
Tackle Opportunities API
Tackle Partners API