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

Create, read, update, and list co-sell opportunities — the partner-originated (Outbound / Partner Referral) and AWS-originated (Inbound/ AWS Referral) deals tracked in AWS Partner Central. Includes theopportunity history endpoint for inspecting cloud-side request andresponse detail.

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

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

This API exposes 5 operations across 3 paths, and defines 20 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.

5 operations 3 paths 20 schemas 3 GET2 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 Opportunities 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 5

Across 3 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Opportunities 5

Create, read, update, and list co-sell opportunities — the partner- originated (Outbound / Partner Referral) and AWS-originated (Inbound / AWS Referral) deals tracked in AWS Partn…

GET
/api/opportunities
List co-sell opportunities
listOpportunities 17 params → 200400401500
POST
/api/opportunities
Create a co-sell opportunity
createOpportunity 1 param body → 202400401409500
GET
/api/opportunities/{opportunity_id}
Get a co-sell opportunity
getOpportunity 1 param → 200401404500
POST
/api/opportunities/{opportunity_id}
Update a co-sell opportunity
updateOpportunity 2 params body → 202400401404409423500
GET
/api/opportunities/{opportunity_id}/events
List opportunity events
listOpportunityEvents 2 params → 200401500

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are ListOpportunitiesResponseItem (19 properties), OpportunityMetadata (19 properties), Opportunity (12 properties), Project (12 properties). Each schema is shown below with its type and property counts.

OpportunityInput
object
1 property
ListOpportunitiesResponse
object
5 properties
ListOpportunitiesResponseItem
object
19 properties
Error
object
Error envelope returned for typed error responses. Some 4xx and 5xx responses (such as direct Unauthorized and Internal Server Error responses) may instead ret…
1 property
Account
object
7 properties
DataMapper
object
1 property
AwsOpportunityTeam
object
4 properties
Customer
object
2 properties
Project
object
12 properties
Address
object
5 properties
Opportunity
object
12 properties
OpportunityMetadata
object
19 properties 4 required
OpportunityResponse
object
9 properties
SoftwareRevenue
object
4 properties
LifeCycle
object
8 properties
ListOpportunityEvents
object
8 properties 3 required
Contacts
array
Marketing
object
5 properties
Insights
object
AWS-derived insights about the opportunity, populated by AWS Partner Central when available.
2 properties
CreateOpportunityInput
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tackle-opportunities-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 Invoices API
Tackle Marketplace API
Tackle Metering API
Tackle Notifications API
Tackle Partners API
Where this information came from

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