Tagove · Authentication Profile

Tagove Authentication

Authentication

Tagove secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyCustomer-SupportLive ChatConversationalCo-BrowsingChatbotsWebhookCustomer CommunicationHelp Desk

Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in: header

Security Schemes

ApiKeyBearer apiKey

· in: header (Authorization)

OAuth2 oauth2

· flows: authorizationCode

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://developer.acquire.io/rest-apis/authorization
docs: https://developer.acquire.io/rest-apis/authorization
note: >-
  Tagove now operates as Acquire.io (acquire.io); this profile documents the
  Acquire developer platform that succeeded Tagove. No machine-readable OpenAPI
  is published, so this profile is captured from the developer documentation.
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
schemes:
- name: ApiKeyBearer
  type: apiKey
  in: header
  parameter: Authorization
  format: 'Bearer {API_KEY}'
  description: >-
    All REST requests require an API_KEY passed as an HTTP Bearer token in the
    Authorization header (`Authorization: Bearer {API_KEY}`). Keys are created
    and revoked under Settings > For Developers > API Key with per-token
    permissions; keys are shown once and cannot be re-displayed. All requests
    must be over HTTPS.
  sources:
  - https://developer.acquire.io/rest-apis/authorization
- name: OAuth2
  type: oauth2
  description: >-
    OAuth is required for publicly-available apps that access other Acquire
    accounts' data on behalf of users. First-party scripts that access an
    account's own data use an Access Token instead. Asking users for their
    Access Token in place of OAuth is against the Acquire terms of service.
  flows:
  - flow: authorizationCode
  sources:
  - https://developer.acquire.io/master/rest-apis/oauth/authorization

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/tagove-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.