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

Oper Credits Commissions API

The Commissions API from Oper Credits — 8 operation(s) for commissions.

Oper Credits Commissions API is one of 52 APIs that Oper Credits publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 10 operations across 8 paths, and defines 13 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against the base URL https://developers.opercredits.com/.

10 operations 8 paths 13 schemas 5 GET2 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://developers.opercredits.com/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Oper Credits Commissions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwtAuth).

Paths & Operations 10

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

Commissions 10
GET
/api/commissions/documents/{year}/{month}/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_documents_retrieve 2 params → 200
GET
/api/commissions/files/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_files_list → 200
POST
/api/commissions/files/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_files_create body → 201
POST
/api/commissions/files/{commission_file_id}/recoveries/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_files_recoveries_create 1 param body → 201
GET
/api/commissions/objects/{year}/{month}/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_objects_list 2 params → 200
GET
/api/commissions/payment-files/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_payment_files_list → 200
PATCH
/api/commissions/payment-files/{id}/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_payment_files_partial_update 1 param body → 200
PUT
/api/commissions/payment-files/{id}/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_payment_files_update 1 param body → 200
GET
/api/commissions/payment-files/{id}/download/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_payment_files_download_retrieve 1 param → 200
PATCH
/api/commissions/payment-files/{id}/regenerate/
A ViewSet mixin that parametrizes DRF methods over roles
api_commissions_payment_files_regenerate_partial_update 1 param body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are CommissionStatementDocument (17 properties), CommissionFile (10 properties), DocumentType (10 properties), PaymentFile (6 properties). Each schema is shown below with its type and property counts.

CommissionFileStatus
object
Can be managed at /resources/commission-file-status
3 properties 3 required
DocumentStatus
object
Can be managed at /resources/document-status
3 properties 3 required
CommissionType
object
Can be managed at /resources/commission-type
3 properties 3 required
CommissionStatementDocument
object
17 properties 10 required
RecoveryStatus
object
Can be managed at /resources/recovery-status
3 properties 3 required
Recovery
object
5 properties 2 required
ReducedProductItem
object
Baseclass for Reduced serializers. Will validate whether the objects exists, and returns the instance in tointernalvalue Subclasses must implement Meta with at…
3 properties 3 required
ReducedCommissionFile
object
Baseclass for Reduced serializers. Will validate whether the objects exists, and returns the instance in tointernalvalue Subclasses must implement Meta with at…
1 property 1 required
PatchedPaymentFile
object
6 properties
Commission
object
5 properties 5 required
CommissionFile
object
10 properties 9 required
PaymentFile
object
6 properties 5 required
DocumentType
object
Can be managed at /resources/document-type
10 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oper-credits-commissions-api-openapi.yml Raw ↑

Other APIs Oper Credits publishes across the network.

Oper Credits Agent Documents API
Oper Credits Appointment Booking Websites API
Oper Credits Approvals API
Oper Credits Bank Release Policy API
Oper Credits Base Products API
Oper Credits Calculate API
Oper Credits Check Invite Token API
Oper Credits Check Reset Password API
Oper Credits Client Users API
Oper Credits Clients API
Oper Credits Communication History API
Oper Credits Connective API
Where this information came from

This is an independent, third-party profile of Oper Credits Commissions 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.