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 Metering API

The Metering API from Tackle.io — 2 operation(s) for metering.

Tackle.io Metering 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 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 49 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.

5 operations 2 paths 49 schemas 1 DELETE2 GET1 POST1 PUT

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 Metering 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 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.

Metering 5
POST
/v1/metering/usage-records
Create Usage Records
v1-create-metering-usage-records body → 200400401404
PUT
/v1/metering/usage-records
Create or Update Usage Records
v1-create-update-metering-usage-records body → 200400401404409
GET
/v1/metering/usage-records
List Usage Records
v1-list-metering-usage-records 13 params → 200401
GET
/v1/metering/usage-records/{usage_record_id}
Get a Usage Record
v1-get-metering-usage-record 1 param → 200400401404
DELETE
/v1/metering/usage-records/{usage_record_id}
Delete a Usage Record
v1-delete-metering-usage-record 1 param → 200400401404

Schemas 49

The contract defines 49 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.

AwsCustomerId
string
AWS Account Reference ID
NextPageToken
string
A page token to fetch the next page of results using the associated "page" query parameter
AwsMeteringProductId
string
AWS Product Code
AwsUsageRecordRequestBySubscription
object
6 properties 4 required
GcpDimension
object
3 properties 2 required
AzureUsageRecordRequestByProductAndCustomer
object
7 properties 5 required
TimestampNotNull
string
ISO format timestamp with UTC offset
Spec_prod_Error
object
4 properties 3 required
UsageRecordTest
stringnull
Specifies if the Usage Record is a test. When NOT null, the record is a test and is not sent to the marketplace
AzureCloud
string
Azure Cloud
TimestampZeroUtcOffsetOptional
stringnull
Optional ISO format timestamp with zero UTC offset
UsageRecordDelete
object
Delete Usage Record Response
1 property
UsageRecordReason
string
Explanation of Status
UsageRecordMetadata
object
Usage Record Metadata
1 property
UsageRecordResponse
object
Usage Record Response
2 properties
CustomerId
RedHatCustomerId
string
Red Hat Customer Id
AwsCloud
string
AWS Cloud
GcpUsageRecordRequestBySubscription
object
7 properties 4 required
GcpCloud
string
GCP Cloud
GcpUsageRecordRequestByProductAndCustomer
object
8 properties 6 required
ProductId
Cloud Marketplace issued ID for a product
Uuid
string
UUID
TimestampZeroUtcOffset
string
ISO format timestamp with zero UTC offset
UsageRecordStatus
string
Status of usage record
SubscriptionId
stringnull
Subscription Id
UsageRecordListResponse
object
Get All Usage Records Response
2 properties
UsageRecord
object
Metering Usage Record
15 properties
GcpCustomerId
string
GCP External Account ID
RedHatProductId
string
Red Hat Product Id
AwsUsageRecordRequest
AzureCustomerId
string
Azure Subscription ID
AzureUsageRecordRequestBySubscription
object
6 properties 4 required
UsageRecordLink
string
Url for one or more metering usage records
AwsMeteringCustomerId
string
AWS Customer Reference ID or AWS Account Number
Timestamp
stringnull
ISO format timestamp with UTC offset
AwsProductId
string
AWS Product Code
AwsUsageRecordRequestByProductAndCustomer
object
7 properties 5 required
GcpUsageRecordRequest
Clouds
A string identifying a cloud marketplace
AzureProductId
string
Azure Offer ID
RedHatCloud
string
Red Hat Cloud
AzureUsageRecordRequest
AzureDimension
object
Product Dimension
2 properties 2 required
AwsMeteringSubscriptionId
stringnull
Agreement ID, License ID or License ARN
UsageRecordsMetadata
object
Usage Record Metadata
2 properties
Error
object
4 properties 3 required
GcpProductId
string
GCP Solution ID
AwsDimension
object
Product Dimension
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tackleio-metering-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 Invoices API
Tackle.io Marketplace API
Tackle.io Notifications API
Tackle.io Opportunities API
Where this information came from

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