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

The Main API from Oper Credits — 30 operation(s) for main.

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

This API exposes 83 operations across 30 paths, and defines 29 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

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

83 operations 30 paths 29 schemas 13 DELETE28 GET14 PATCH14 POST14 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 Main API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwtAuth).

Paths & Operations 83

Across 30 paths, the API surfaces 83 operations — 13 DELETE, 28 GET, 14 PATCH, 14 POST, 14 PUT. Each is listed below with its method, path, parameters, and response codes.

Main 83
GET
/api/main/addresses/
api_main_addresses_list → 200
POST
/api/main/addresses/
api_main_addresses_create body → 201
DELETE
/api/main/addresses/{id}/
api_main_addresses_destroy 1 param → 204
GET
/api/main/addresses/{id}/
api_main_addresses_retrieve 1 param → 200
PATCH
/api/main/addresses/{id}/
api_main_addresses_partial_update 1 param body → 200
PUT
/api/main/addresses/{id}/
api_main_addresses_update 1 param body → 200
GET
/api/main/application-users/
api_main_application_users_list → 200
POST
/api/main/application-users/
api_main_application_users_create body → 201
DELETE
/api/main/application-users/{id}/
api_main_application_users_destroy 1 param → 204
GET
/api/main/application-users/{id}/
api_main_application_users_retrieve 1 param → 200
PATCH
/api/main/application-users/{id}/
api_main_application_users_partial_update 1 param body → 200
PUT
/api/main/application-users/{id}/
api_main_application_users_update 1 param body → 200
POST
/api/main/bank-branches/
api_main_bank_branches_create body → 201
PATCH
/api/main/bank-branches/{id}/
api_main_bank_branches_partial_update 1 param body → 200
PUT
/api/main/bank-branches/{id}/
api_main_bank_branches_update 1 param body → 200
GET
/api/main/base-users/
api_main_base_users_list → 200
POST
/api/main/base-users/
api_main_base_users_create body → 201
DELETE
/api/main/base-users/{id}/
api_main_base_users_destroy 1 param → 204
GET
/api/main/base-users/{id}/
api_main_base_users_retrieve 1 param → 200
PATCH
/api/main/base-users/{id}/
api_main_base_users_partial_update 1 param body → 200
PUT
/api/main/base-users/{id}/
api_main_base_users_update 1 param body → 200
GET
/api/main/client-users/
api_main_client_users_list → 200
POST
/api/main/client-users/
api_main_client_users_create body → 201
DELETE
/api/main/client-users/{id}/
api_main_client_users_destroy 1 param → 204
GET
/api/main/client-users/{id}/
api_main_client_users_retrieve 1 param → 200
PATCH
/api/main/client-users/{id}/
api_main_client_users_partial_update 1 param body → 200
PUT
/api/main/client-users/{id}/
api_main_client_users_update 1 param body → 200
GET
/api/main/content-types/
api_main_content_types_list → 200
GET
/api/main/content-types/{id}/
api_main_content_types_retrieve 1 param → 200
GET
/api/main/emails/
api_main_emails_list → 200
POST
/api/main/emails/
api_main_emails_create body → 201
DELETE
/api/main/emails/{id}/
api_main_emails_destroy 1 param → 204
GET
/api/main/emails/{id}/
api_main_emails_retrieve 1 param → 200
PATCH
/api/main/emails/{id}/
api_main_emails_partial_update 1 param body → 200
PUT
/api/main/emails/{id}/
api_main_emails_update 1 param body → 200
GET
/api/main/groups/
api_main_groups_list → 200
POST
/api/main/groups/
api_main_groups_create body → 201
DELETE
/api/main/groups/{id}/
api_main_groups_destroy 1 param → 204
GET
/api/main/groups/{id}/
api_main_groups_retrieve 1 param → 200
PATCH
/api/main/groups/{id}/
api_main_groups_partial_update 1 param body → 200
PUT
/api/main/groups/{id}/
api_main_groups_update 1 param body → 200
GET
/api/main/permissions/
api_main_permissions_list → 200
POST
/api/main/permissions/
api_main_permissions_create body → 201
DELETE
/api/main/permissions/{id}/
api_main_permissions_destroy 1 param → 204
GET
/api/main/permissions/{id}/
api_main_permissions_retrieve 1 param → 200
PATCH
/api/main/permissions/{id}/
api_main_permissions_partial_update 1 param body → 200
PUT
/api/main/permissions/{id}/
api_main_permissions_update 1 param body → 200
GET
/api/main/phones/
api_main_phones_list → 200
POST
/api/main/phones/
api_main_phones_create body → 201
DELETE
/api/main/phones/{id}/
api_main_phones_destroy 1 param → 204
GET
/api/main/phones/{id}/
api_main_phones_retrieve 1 param → 200
PATCH
/api/main/phones/{id}/
api_main_phones_partial_update 1 param body → 200
PUT
/api/main/phones/{id}/
api_main_phones_update 1 param body → 200
GET
/api/main/profile-addresses/
api_main_profile_addresses_list → 200
POST
/api/main/profile-addresses/
api_main_profile_addresses_create body → 201
DELETE
/api/main/profile-addresses/{id}/
api_main_profile_addresses_destroy 1 param → 204
GET
/api/main/profile-addresses/{id}/
api_main_profile_addresses_retrieve 1 param → 200
PATCH
/api/main/profile-addresses/{id}/
api_main_profile_addresses_partial_update 1 param body → 200
PUT
/api/main/profile-addresses/{id}/
api_main_profile_addresses_update 1 param body → 200
GET
/api/main/profile-emails/
api_main_profile_emails_list → 200
POST
/api/main/profile-emails/
api_main_profile_emails_create body → 201
DELETE
/api/main/profile-emails/{id}/
api_main_profile_emails_destroy 1 param → 204
GET
/api/main/profile-emails/{id}/
api_main_profile_emails_retrieve 1 param → 200
PATCH
/api/main/profile-emails/{id}/
api_main_profile_emails_partial_update 1 param body → 200
PUT
/api/main/profile-emails/{id}/
api_main_profile_emails_update 1 param body → 200
GET
/api/main/profile-phones/
api_main_profile_phones_list → 200
POST
/api/main/profile-phones/
api_main_profile_phones_create body → 201
DELETE
/api/main/profile-phones/{id}/
api_main_profile_phones_destroy 1 param → 204
GET
/api/main/profile-phones/{id}/
api_main_profile_phones_retrieve 1 param → 200
PATCH
/api/main/profile-phones/{id}/
api_main_profile_phones_partial_update 1 param body → 200
PUT
/api/main/profile-phones/{id}/
api_main_profile_phones_update 1 param body → 200
GET
/api/main/user-credit-providers/
api_main_user_credit_providers_list → 200
POST
/api/main/user-credit-providers/
api_main_user_credit_providers_create body → 201
DELETE
/api/main/user-credit-providers/{id}/
api_main_user_credit_providers_destroy 1 param → 204
GET
/api/main/user-credit-providers/{id}/
api_main_user_credit_providers_retrieve 1 param → 200
PATCH
/api/main/user-credit-providers/{id}/
api_main_user_credit_providers_partial_update 1 param body → 200
PUT
/api/main/user-credit-providers/{id}/
api_main_user_credit_providers_update 1 param body → 200
GET
/api/main/user-profiles/
api_main_user_profiles_list 1 param → 200
POST
/api/main/user-profiles/
api_main_user_profiles_create body → 201
DELETE
/api/main/user-profiles/{id}/
api_main_user_profiles_destroy 1 param → 204
GET
/api/main/user-profiles/{id}/
api_main_user_profiles_retrieve 1 param → 200
PATCH
/api/main/user-profiles/{id}/
api_main_user_profiles_partial_update 1 param body → 200
PUT
/api/main/user-profiles/{id}/
api_main_user_profiles_update 1 param body → 200

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are ApplicationUserCrud (22 properties), PatchedApplicationUserCrud (22 properties), PatchedClientUserCrud (21 properties), PatchedBaseUserCrud (21 properties). Each schema is shown below with its type and property counts.

PatchedUserProfileAuto
object
11 properties
PatchedUser2CreditProviderAuto
object
4 properties
PermissionAuto
object
4 properties 4 required
Profile2PhoneAuto
object
5 properties 4 required
PatchedAddressAuto
object
16 properties
PatchedPhoneAuto
object
3 properties
PatchedGroupAuto
object
3 properties
PatchedProfile2EmailAuto
object
4 properties
ClientUserCrud
object
21 properties 5 required
PatchedBankBranchAuto
object
4 properties
BankBranchAuto
object
4 properties 2 required
AddressAuto
object
16 properties 7 required
UserProfileAuto
object
11 properties 2 required
EmailAuto
object
2 properties 2 required
User2CreditProviderAuto
object
4 properties 3 required
PatchedClientUserCrud
object
21 properties
ContentTypeAuto
object
3 properties 3 required
GroupAuto
object
3 properties 2 required
PatchedApplicationUserCrud
object
22 properties
PatchedBaseUserCrud
object
21 properties
PhoneAuto
object
3 properties 3 required
PatchedProfile2AddressAuto
object
4 properties
PatchedEmailAuto
object
2 properties
Profile2EmailAuto
object
4 properties 4 required
BaseUserCrud
object
21 properties 5 required
PatchedProfile2PhoneAuto
object
5 properties
PatchedPermissionAuto
object
4 properties
Profile2AddressAuto
object
4 properties 4 required
ApplicationUserCrud
object
22 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oper-credits-main-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 Commissions API
Oper Credits Communication History API
Where this information came from

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