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

Zally Api Violations API

The Api Violations API from Zally — 2 operation(s) for api violations.

Zally Api Violations API is one of 3 APIs that Zally publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Api Violations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a JSON-LD context, and 2 JSON Schemas.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.3.0.

Requests are made against a single base URL, https://zally.on.inter.net.

2 operations 2 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.3.0
Base URL
https://zally.on.inter.net
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Zally Api Violations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth).

Paths & Operations 2

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

Api Violations 2
POST
/api-violations
Zally API Violations
body → 200400default
GET
/api-violations/{externalId}
Zally Get Previous Generated Validation Result
1 param → 200404default

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Violation (8 properties), ViolationsCount (5 properties), LintingRequest (4 properties), LintingResponse (4 properties). Each schema is shown below with its type and property counts.

RuleType
string
Rule type / severity
ViolationsCount
object
Violation Count
5 properties 5 required
LintingResponse
object
Linting Response
4 properties 2 required
Violation
object
Violation Object
8 properties 4 required
LintingRequest
object
Request containing a swagger definition file. One of the following fields must be provided: apidefinition, apidefinitionstring, or apidefinitionurl.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zally-api-violations-api-openapi.yml Raw ↑

Other APIs Zally publishes across the network.

Zally Review Statistics API
Zally Supported Rules API
Where this information came from

This is an independent, third-party profile of Zally Api Violations 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.