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

Score domains and search scored accounts.

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

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

This API exposes 2 operations across 2 paths, and defines 12 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.

2 operations 2 paths 12 schemas 2 POST

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 Scores 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 2

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

Scores 2

Score domains and search scored accounts.

POST
/api/scores
Score domains
scoreDomains body → 200400401403500
POST
/api/scores/search
Search scored domains
searchScoredDomains body → 200400401403500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are SearchScoredDomainsRequest (11 properties), Demographics (7 properties), PaginationMetadata (6 properties), ScoredDomain (6 properties). Each schema is shown below with its type and property counts.

PaginationMetadata
object
6 properties
SearchError
object
1 property 1 required
Demographics
object
Firmographic enrichment for a domain.
7 properties
ScoreResult
object
4 properties 3 required
CloudMarketplace
string
A cloud marketplace filter value.
BuyerSignalType
string
Identifies which cloud marketplace signal to score.
PaginatedScoredDomainsResponse
object
2 properties 2 required
ScoreDomainsRequest
object
2 properties 2 required
ScoredDomain
object
6 properties 1 required
SearchScoredDomainsRequest
object
Filter and pagination parameters for scored-domain search.
11 properties
MessageError
object
1 property 1 required
ScoreBin
string
The display value for a propensity score.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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