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

Zoca Compensation API

The Compensation API from Zoca — 9 operation(s) for compensation.

Zoca Compensation API is one of 193 APIs that Zoca publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Compensation. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 12 operations across 9 paths. It is described by OpenAPI 3.2.0, at version 3.20.10.

Requests are made against a single base URL, https://api.zoca.ai.

12 operations 9 paths 0 schemas 2 DELETE5 GET3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.20.10
Base URL
https://api.zoca.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Zoca Compensation API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (access-token).

  • access-token — Enter JWT token in the format Bearer

Paths & Operations 12

Across 9 paths, the API surfaces 12 operations — 2 DELETE, 5 GET, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Compensation 12
GET
/compensation/refund-allocation/preview/{saleId}
Preview how a refund splits across sale lines
t_value → 200
GET
/compensation/settings/{locationEntityId}
Get commission calculation settings for a location
t_value → 200
PUT
/compensation/settings/{locationEntityId}
Update commission calculation settings
t_value → 200
GET
/compensation/rules/{memberLocationId}
Get commission rule history for a staff member
t_value → 200
POST
/compensation/rules/{memberLocationId}
Create a new effective-dated commission rule
t_value → 201
GET
/compensation/overrides/{memberLocationId}
Get commission rate overrides
t_value → 200
POST
/compensation/overrides/{memberLocationId}
Add or replace a commission rate override
t_value → 201
DELETE
/compensation/overrides/{overrideId}
End a commission rate override
t_value → 200
PUT
/compensation/pay-config/{memberLocationId}
Update hourly / fixed pay / greater-of settings
t_value → 200
GET
/compensation/adjustments/{memberLocationId}
List manual pay adjustments
t_value → 200
POST
/compensation/adjustments
Record a manual pay adjustment
t_value → 201
DELETE
/compensation/adjustments/{adjustmentId}
Remove a manual pay adjustment
t_value → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoca-compensation-api-openapi.yml Raw ↑

Other APIs Zoca publishes across the network.

Zoca ACM API
Zoca Acuity API
Zoca Addon Groups API
Zoca Addons API
Zoca Aeo Lead Magnet API
Zoca Agents API
Zoca API Keys API
Zoca App API
Zoca App Blocker API
Zoca App Blocker Updates API
Zoca Approvals API
Zoca Auth API
Where this information came from

This is an independent, third-party profile of Zoca Compensation 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.