CarServ · Authentication Profile

Carserv Authentication

Authentication

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

CompanyAutomotiveAuto RepairShop ManagementVehicle InspectionField ServiceSoftware-as-a-ServiceJSON:APIDefunct
Methods: http Schemes: 1 OAuth flows: API key in: body

Security Schemes

bearerAuth http
scheme: bearer · in: header ()

Source

Authentication Profile

carserv-authentication.yml Raw ↑
generated: '2026-07-20'
method: derived
source: >-
  https://github.com/CarServ/public_api_client —
  lib/carserv/public_api/client/authenticator.rb,
  lib/carserv/public_api/client/config.rb,
  lib/carserv/public_api/client/resources/base.rb
notes: >-
  Derived from the first-party Ruby client, not from an OpenAPI definition —
  CarServ never published a machine-readable spec and the developer site is gone.
  The model is a two-legged key/secret token exchange that returns a JWT, which is
  then sent as a bearer token on every JSON:API request. Not OAuth 2.0: there is no
  authorization endpoint, no scopes, no refresh token and no grant_type parameter,
  so no scopes/ artifact is produced.
summary:
  types:
  - http
  bearer_format: JWT
  api_key_in:
  - body
  oauth2_flows: []
  scopes_supported: false
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  in: header
  header: Authorization
  value_format: 'Bearer <jwt>'
  applied_to: all Public API resource requests
  sources:
  - https://github.com/CarServ/public_api_client
token_exchange:
  method: POST
  path: /public/api/v2/access_token.json
  request_content_type: application/json
  request_body_fields:
  - name: key
    description: CarServ API key issued to the integrating account
  - name: secret
    description: CarServ API secret paired with the key
  response_field: jwt
  description: >-
    Credentials are exchanged for a JWT which the client caches (the reference
    client caches it in Redis under access_token_<api_key>) and replays as a
    bearer token.
token_lifecycle:
  caching: client-side, keyed on the API key
  refresh_trigger: >-
    A 401 Not Authorized on any resource request causes the client to request a
    new access token and retry once before surfacing the error.
  expiry_published: false
credentials:
  issuance: private — issued by CarServ to integrating accounts; no public self-serve signup
  rotation_policy_published: false
status: discontinued
status_note: >-
  The authentication host is no longer resolvable; carserv.com is a parked domain.
  This profile documents the historical contract as shipped in the client library.

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/carserv-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.