Tackle Metering API
The Metering API from Tackle — 2 operation(s) for metering.
Tackle Metering API is one of 25 APIs that Tackle publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Metering. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.
This API exposes 5 operations across 2 paths, and defines 46 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api.tackle.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Tackle Metering 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 callbacksHeaderApiKeyAuthCallback— 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 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.
Schemas 46
The contract defines 46 schemas that model the data the API accepts and returns. The most detailed are UsageRecord (15 properties), GcpUsageRecordRequestByProductAndCustomer (8 properties), AzureUsageRecordRequestByProductAndCustomer (7 properties), AwsUsageRecordRequestByProductAndCustomer (7 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Tackle 12
Other APIs Tackle publishes across the network.
This is an independent, third-party profile of Tackle Metering 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.