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

Operations for Order Registrations

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

Tagged areas include Registrations. 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 23 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.

1 operations 1 paths 23 schemas 1 POST

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, HTTP Basic, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 4

Tackle.io Registrations 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 POST. Each is listed below with its method, path, parameters, and response codes.

Registrations 1

Operations for Order Registrations

POST
/v1/registrations
Register an Order
v1-create-registration body → 200400401403404

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are GcpEntitlement (17 properties), RedHatEntitlement (9 properties), AzureEntitlement (5 properties), AwsEntitlement (4 properties). Each schema is shown below with its type and property counts.

Entitlements
array
A list of Entitlement objects
GcpProductId
string
GCP Solution ID
Error
object
4 properties 3 required
RedHatProductId
string
Red Hat Product Id
GcpEntitlement
object
A purchase entitlement from GCP Marketplace
17 properties 5 required
AwsProductId
string
AWS Product Code
RedHatTermUnit
string
The unit for the term
RedHatSubscriptionType
string
Type of the subscription
AwsEntitlement
object
A purchase entitlement from AWS Marketplace
4 properties 4 required
RedHatEntitlement
object
A purchase entitlement from Red Hat Marketplace
9 properties 9 required
CustomerId
GcpCustomerId
string
GCP External Account ID
RegistrationDetails
object
Registration details of a purchaser that map to defined registration page fields for a given listing. The following fields are required at a minimum: - Company…
3 properties 3 required
Entitlement
object
A purchase entitlement for a given cloud marketplace
AwsCustomerId
string
AWS Account Reference ID
AzureProductId
string
Azure Offer ID
RedHatSubscriptionRenewType
string
Renew Type
RegistrationsRequest
object
3 properties 3 required
RegistrationsResponse
object
1 property 1 required
RedHatCustomerId
string
Red Hat Customer Id
AzureCustomerId
string
Azure Subscription ID
AzureEntitlement
object
A purchase entitlement from Azure Marketplace
5 properties 5 required
ProductId
Cloud Marketplace issued ID for a product

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tackleio-registrations-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 Metering API
Tackle.io Notifications API
Where this information came from

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