How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

GatiFlow Usage API

The usage operation of the GatiFlow Intelligence API — recent calls made with the API key used on the request (limit up to 500), so a scheduled job can audit its own traffic without a second log.

GatiFlow Usage API is one of 4 APIs that GatiFlow publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Usage. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and 1 JSON Schema.

This API exposes 1 operation across 1 path, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.3.0.

Requests are made against a single base URL, https://api.gatiflow.io.

1 operations 1 paths 6 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.3.0
Base URL
https://api.gatiflow.io
Authentication
API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

GatiFlow Usage API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyAuth). It accepts HTTP bearer tokens (JWT) (SessionBearer).

  • ApiKeyAuth — API key (prefix gf) created in Dashboard → API Keys.
  • SessionBearer — Web session token issued to the browser at sign-in. It is not part of the public API and cannot be created from an API key; an API key sent to an operation tha…

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Usage 1
GET
/api/v1/usage
List recent calls made with this API key
get_my_usage_api_v1_usage_get 2 params → 200401402403422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ValidationIssue (6 properties), ErrorDetail (5 properties), UsageEvent (3 properties), UsageLog (3 properties). Each schema is shown below with its type and property counts.

ErrorDetail
object
What went wrong, and the id to quote when asking about it.
5 properties 5 required
ErrorMetadata
object
3 properties 3 required
ErrorResponse
object
Every refusal the API returns, whatever its status.
3 properties 3 required
UsageLog
object
The request log of the API key used on the call, newest first.
3 properties 3 required
UsageEvent
object
3 properties 3 required
ValidationIssue
object
One problem with the request, as a 422 lists it in error.details.
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gatiflow-usage-api-openapi.yml Raw ↑

Other APIs GatiFlow publishes across the network.

GatiFlow Intelligence API
GatiFlow Public API
GatiFlow Webhooks API
Where this information came from

This is an independent, third-party profile of GatiFlow Usage API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.