generated: '2026-08-12'
method: searched
source: https://support.demandscience.com/hc/en-us
docs: https://support.demandscience.com/hc/en-us/sections/38485678357267-API-Documentation
note: >-
  Derived from the public DemandScience Help Center, not from an OpenAPI — Terminus
  publishes no machine-readable specification. The API reference lives on a Redocly
  developer portal at developer.terminus.com where every path 302s to /redocly-login,
  so the security schemes below are what the public help center documents plus what
  the live API host returns to an anonymous caller.
  UPDATED 2026-08-12: the help center's "API Documentation" section publishes the
  full auth contract for a third API — the Verify API — including the exact header
  name. That is the only Terminus / DemandScience API whose header name is public.
summary:
  types: [apiKey]
  api_key_in: [header]
  oauth2_flows: []
  issuance: support-ticket
  sso: [saml2, oidc, microsoft, google]
  named_headers: [x-api-key]
schemes:
- name: VerifyApiKey
  type: apiKey
  in: header
  parameter_name: x-api-key
  api: Verify API
  description: >-
    The Verify API (formerly Lastbounce, sold as Intelligent Verification)
    authenticates with an account API key sent in the `x-api-key` request header, on
    every documented call — POST /api/singleEmail/validate,
    POST /api/batch/validation, POST /api/batch/{jobId}/status and
    GET /api/file/download/{jobId}. The key both authenticates the request and binds
    it to the account's credit balance: "For every email verification, a credit is
    consumed from your account. If you lack sufficient credits, the API call will be
    unsuccessful." The same key is used across all three published environments
    (dev-api / sqa-api / api .lastbounce.com) — there is no test-vs-live key prefix.
    Anonymous calls are rejected at the AWS API Gateway edge with HTTP 403
    {"message":"Forbidden"}.
  key_prefix: null
  rotation: not documented
  scopes: none
  sources:
  - https://support.demandscience.com/hc/en-us/articles/47521026202771-Verify-API
  - https://support.demandscience.com/hc/en-us/articles/38485762247059-Verify-Single-and-Batch-Uploads
- name: PlatformApiKey
  type: apiKey
  in: header
  description: >-
    Terminus ABM Platform API access is requested through a DemandScience support
    ticket; the key is issued by a CSM or Onboarding Specialist rather than
    self-served from a developer console. Anonymous requests to
    https://api.terminusplatform.com/ return HTTP 401 with the plain-text body
    "Authentication Invalid" on every path probed.
  sources: [https://support.demandscience.com/hc/en-us/articles/360051822454-Employee-Automation-API-for-Email-Experiences]
- name: WebExperiencesApiKey
  type: apiKey
  in: header
  description: >-
    Web Experiences (terminus.bound360.com) connects to the DemandScience data and
    advertising audiences using an API key "provided by your CSM or Onboarding
    Specialist", entered on the Connections page of the web personalization interface.
  sources: [https://support.demandscience.com/hc/en-us/articles/360045192013-Connecting-Your-Web-Experiences-API-Key]
user_authentication:
  description: >-
    Human sign-in to the platform (app.demandscienceplatform.com) supports Microsoft
    and Google SSO out of the box, plus SAML 2.0 for third-party identity providers
    (both SP-initiated and IdP-initiated), and OpenID Connect as an alternative input
    set. SAML/OIDC enablement is coordinated by an Account Manager or CSM and may
    carry additional cost.
  standards: [saml2, oidc]
  requires_from_customer:
    saml2: [idp-sso-url, idp-issuer-uri, x509-certificate, attribute-mappings, saml-metadata-xml]
    oidc: [issuer, authorization-endpoint, token-endpoint, jwks-uri, userinfo-endpoint]
  docs: https://support.demandscience.com/hc/en-us/articles/360059215833-Logging-Into-the-DemandScience-Platform-Using-SAML-2-0
x-evidence:
- {url: 'https://api.lastbounce.com/api/singleEmail/validate', http_status: 403, method: POST, body: '{"message":"Forbidden"}', fetched: '2026-08-12'}
- {url: 'https://api.lastbounce.com/', http_status: 403, body: '{"message":"Missing Authentication Token"}', note: 'AWS API Gateway us-east-2 edge rejection', fetched: '2026-08-12'}
- {url: 'https://support.demandscience.com/api/v2/help_center/en-us/sections/38485678357267/articles.json', http_status: 200, note: 'API Documentation section, 6 articles', fetched: '2026-08-12'}
- {url: 'https://api.terminusplatform.com/openapi.json', http_status: 401, body: Authentication Invalid, fetched: '2026-08-05'}
- {url: 'https://api.terminusplatform.com/v1', http_status: 401, body: Authentication Invalid, fetched: '2026-08-05'}
- {url: 'https://developer.terminus.com/', http_status: 302, redirect: /redocly-login, fetched: '2026-08-05'}
- {url: 'https://support.demandscience.com/api/v2/help_center/en-us/articles/360045192013.json', http_status: 200, fetched: '2026-08-05'}