Reputation · Authentication Profile

Reputation Authentication

Authentication

Reputation secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

Reputation ManagementOnline ReviewsBusiness ListingsSurveysSocial ListeningCompetitive IntelligenceCustomer ExperienceLocal SEO
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

ApiKeyAuth apiKey
· in: header (X-API-KEY)

Source

Authentication Profile

Raw ↑
generated: '2026-08-13'
method: searched
source: openapi/_original/reputation-api-openapi.yml
docs: https://apidocs.reputation.com/
summary:
  types:
  - apiKey
  api_key_in:
  - header
  oauth2_flows: []
  applies_to_operations: 67
  applies_to_operations_total: 67
schemes:
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: X-API-KEY
  description: >-
    API key for authentication, applied globally to all 67 published operations. Issued only by a
    Reputation customer success manager — there is no self-serve key issuance, no key-management
    endpoint, and no documented rotation or expiry policy.
  sources:
  - openapi/_original/reputation-api-openapi.yml
companion_headers:
- name: X-TENANT-ID
  required_when: >-
    The API key is an Agency key. An Agency key manages resources across multiple client tenants,
    and each request must name the target tenant so actions are scoped correctly.
  omission_behaviour: >-
    Returns HTTP 404 "Missing Tenant Id" — not 401 or 400. Clients must special-case this.
  source: https://apidocs.reputation.com/
key_lifecycle:
  issuance: Contact your Reputation customer success manager.
  self_serve: false
  rotation_endpoint: null
  expiry_documented: false
  scopes: null
  scope_note: >-
    The API has no OAuth2 surface and therefore no scopes. Permission is carried entirely by the
    key; a key either is or is not "permitted the operation" (HTTP 403). No scopes/ artifact is
    emitted because there is nothing to enumerate.
transport:
  tls_required: true
  cipher_policy_published: true
  cipher_policy_source: https://apidocs.reputation.com/
oauth_lookalike:
  operation: get_credentials_oauth
  path: /v3/credentials/oauth
  note: >-
    GET /v3/credentials/oauth reports the OAuth connection status of third-party review and social
    sources connected to the account. It is NOT an OAuth flow for the Reputation API itself and must
    not be read as one.
regions:
- {region: US, host: 'https://api.reputation.com', docs: 'https://apidocs.reputation.com/'}
- {region: EU, host: 'https://api-eu.reputation.com', docs: 'https://apidocs-eu.reputation.com/'}
region_note: A key issued in one data region is not valid in the other; US and EU are separated.
example:
  curl: |
    curl -H "Content-Type: application/json" \
         -H "X-API-KEY: $ACCESS_TOKEN" \
         -H "X-TENANT-ID: $TENANT_ID" \
         "https://api.reputation.com/v3/locations"
  source: https://apidocs.reputation.com/

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/reputation-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 email required.

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