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 Clients API

The Clients API from Oper Credits — 2 operation(s) for clients.

Oper Credits Clients 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 Clients. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 2 paths, and defines 39 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

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

6 operations 2 paths 39 schemas 1 DELETE2 GET1 PATCH1 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 Clients API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwtAuth).

Paths & Operations 6

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

Clients 6
GET
/api/clients/
Mixin that routes to the loan request and verifies if the requestor has access to the requested resource To use the Role View Mixin, you must define either queryset or overwrite getbasequeryset
api_clients_list 3 params → 200
POST
/api/clients/
Mixin that routes to the loan request and verifies if the requestor has access to the requested resource To use the Role View Mixin, you must define either queryset or overwrite getbasequeryset
api_clients_create body → 201
DELETE
/api/clients/{id}/
Mixin that routes to the loan request and verifies if the requestor has access to the requested resource To use the Role View Mixin, you must define either queryset or overwrite getbasequeryset
api_clients_destroy 1 param → 204
GET
/api/clients/{id}/
Mixin that routes to the loan request and verifies if the requestor has access to the requested resource To use the Role View Mixin, you must define either queryset or overwrite getbasequeryset
api_clients_retrieve 1 param → 200
PATCH
/api/clients/{id}/
Mixin that routes to the loan request and verifies if the requestor has access to the requested resource To use the Role View Mixin, you must define either queryset or overwrite getbasequeryset
api_clients_partial_update 1 param body → 200
PUT
/api/clients/{id}/
Mixin that routes to the loan request and verifies if the requestor has access to the requested resource To use the Role View Mixin, you must define either queryset or overwrite getbasequeryset
api_clients_update 1 param body → 200

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are ClientRegistryProfile (103 properties), PatchedClientRegistryProfile (103 properties), Profile2Address (16 properties), NestedClientProfile (10 properties). Each schema is shown below with its type and property counts.

LegalStatusType
object
Can be managed at /resources/legal-status-type
3 properties 3 required
PersonalizedInformation
object
Can be managed at /resources/personalized-information
3 properties 3 required
ReducedClientProfile
object
Client profile reduced representation
3 properties 3 required
SocialInsuranceStartDate
object
Can be managed at /resources/social-insurance-start-date
3 properties 3 required
CustomerSegment
object
Can be managed at /resources/customer-segment
3 properties 3 required
EducationType
object
Can be managed at /resources/education
3 properties 3 required
UserRole
object
Can be managed at /resources/user-role
3 properties 3 required
LenderOnboardingStatus
object
Can be managed at /resources/lender-onboarding-status
3 properties 3 required
ReducedCreditProvider
object
To be used for a short summary of the CreditProvider
9 properties 9 required
ResidencePermit
object
Can be managed at /resources/residence-permit
3 properties 3 required
ReducedBaseUser
object
User reduced representation
5 properties 5 required
EmploymentType
object
Can be managed at /resources/employment-type
3 properties 3 required
Relationship
object
Can be managed at /resources/relationship
3 properties 3 required
ReducedBroker
object
Baseclass for Reduced serializers. Will validate whether the objects exists, and returns the instance in tointernalvalue Subclasses must implement Meta with at…
8 properties 8 required
IdDocumentType
object
Can be managed at /resources/id-document-type
3 properties 3 required
Sex
object
Can be managed at /resources/sex
3 properties 3 required
PaginatedNestedClientProfileList
object
4 properties 2 required
ContactType
object
Can be managed at /resources/contact-type
3 properties 3 required
PhoneCountryCode
object
Can be managed at /resources/phone-country-code
4 properties 4 required
CivilStatus
object
Can be managed at /resources/civil-status
3 properties 3 required
StreetType
object
Can be managed at /resources/street-type
3 properties 3 required
Profile2Email
object
2 properties 1 required
PatchedClientRegistryProfile
object
103 properties
Client
object
3 properties
Client2Client
object
6 properties 4 required
Sector
object
Can be managed at /resources/sector
3 properties 3 required
TaxType
object
Can be managed at /resources/tax-type
3 properties 3 required
LegitimisationType
object
Can be managed at /resources/legitimisation-type
3 properties 3 required
Language
object
Can be managed at /resources/language
3 properties 3 required
PoliticallyExposedPersonType
object
Can be managed at /resources/politically-exposed-person-type
3 properties 3 required
ClientTitle
object
Can be managed at /resources/client-title
3 properties 3 required
Country
object
Can be managed at /resources/country
3 properties 3 required
NestedClientProfile
object
10 properties 8 required
LivingStatus
object
Can be managed at /resources/living-status
3 properties 3 required
ACardDetails
object
Can be managed at /resources/a-card-details
3 properties 3 required
Profile2Address
object
16 properties 4 required
CompanyType
object
Can be managed at /resources/company-types
3 properties 3 required
ClientRegistryProfile
object
103 properties 6 required
Profile2Phone
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oper-credits-clients-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 Commissions 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 Clients 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.