Local Logic · Authentication Profile

Local Logic Authentication

Authentication

Local Logic secures its APIs with clientCredentials across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyLocation IntelligenceReal EstateGeospatialNeighborhoodsDemographicsPoints of InterestProptechClimate RiskLocation Scores
Methods: clientCredentials Schemes: 1 OAuth flows: API key in: header

Security Schemes

ClientCredentials apiKey
· in: header ()

Source

Authentication Profile

local-logic-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://docs.locallogic.co/
docs: https://docs.locallogic.co/
summary:
  types:
  - clientCredentials
  api_key_in:
  - header
  notes: >-
    Local Logic API access requires a client ID and secret, issued after booking a
    demo. Credentials are exchanged for/passed on API requests to the AWS-API-Gateway-fronted
    host api.locallogic.co. No public OpenAPI specification is published, so scheme
    details below are captured from the developer documentation rather than derived
    from a spec.
schemes:
- name: ClientCredentials
  type: apiKey
  description: A client ID and secret pair, obtained by booking a demo, authorizes requests
    to the Local Logic API.
  in: header
  sources:
  - https://docs.locallogic.co/
host: https://api.locallogic.co
gateway: aws-api-gateway