eVerbary EVerbary For Clio API

The EVerbary For Clio API from eVerbary — 1 operation(s) for everbary for clio.

GitHub OpenAPI

Operations 1

GET / Home #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/everbary-com:everbary-com-everbary-for-clio-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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

OpenAPI Specification

everbary-com-everbary-for-clio-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: EVerbary For Clio API
  version: 0.1.0
tags:
- name: EVerbary For Clio
paths:
  /:
    get:
      summary: Home
      description: 'The App URL: where Clio sends someone from My Integrations.


        Clio opens it with no parameters at all, so the only way to know who is

        looking is the signed cookie left at authorisation. Someone arriving

        without one is either a new user of an already-connected firm - which is

        the common case, because custom actions are registered per user and every

        colleague has to connect once - or a firm that has not installed us yet.

        Both want the same button.'
      operationId: home__get
      parameters:
      - name: saved
        in: query
        required: false
        schema:
          type: integer
          default: 0
          title: Saved
      responses:
        '200':
          description: Successful Response
          content:
            text/html:
              schema:
                type: string
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - EVerbary For Clio
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError