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

The Me API from Oper — 8 operation(s) for me.

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

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

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

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

14 operations 8 paths 16 schemas 1 DELETE5 GET2 PATCH4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

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

Paths & Operations 14

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

Me 14
GET
/api/me/
api_me_retrieve → 200
PATCH
/api/me/
api_me_partial_update body → 200
PUT
/api/me/
api_me_update body → 200
POST
/api/me/activate/
This View will request a OTP for a user. If no authy account exists yet, it will also create an Authy account
api_me_activate_create body → 201
GET
/api/me/credit-providers/
api_me_credit_providers_list → 200
POST
/api/me/credit-providers/
api_me_credit_providers_create body → 201
DELETE
/api/me/credit-providers/{id}/
api_me_credit_providers_destroy 1 param → 204
GET
/api/me/credit-providers/{id}/
api_me_credit_providers_retrieve 1 param → 200
PATCH
/api/me/credit-providers/{id}/
api_me_credit_providers_partial_update 1 param body → 200
PUT
/api/me/credit-providers/{id}/
api_me_credit_providers_update 1 param body → 200
POST
/api/me/enrichment-retry/
api_me_enrichment_retry_create → 200
GET
/api/me/enrichment-status/
api_me_enrichment_status_retrieve → 200
GET
/api/me/permissions/
api_me_permissions_list → 200
POST
/api/me/verify/
This View will request a OTP for a user. If no authy account exists yet, it will also create an Authy account
api_me_verify_create body → 201

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are PatchedUserSelf (23 properties), UserSelf (23 properties), ReducedCreditProvider (9 properties), MinimalBroker (6 properties). Each schema is shown below with its type and property counts.

User2CreditProvider
object
3 properties 2 required
PhoneCountryCode
object
Can be managed at /resources/phone-country-code
4 properties 4 required
EnrichmentStatus
object
Can be managed at /resources/enrichment-status
3 properties 3 required
UserRole
object
Can be managed at /resources/user-role
3 properties 3 required
Permission
object
2 properties 2 required
PatchedUser2CreditProvider
object
3 properties
UserSelf
object
Serializer to update the user himself
23 properties 20 required
VerifyUser
object
Serializer to verify a user and provide permissions
2 properties 2 required
CompanyType
object
Can be managed at /resources/company-types
3 properties 3 required
ActivateUser
object
Serializer to create a verified user. This will return a request for a OTP
2 properties 2 required
ReducedCreditProvider
object
To be used for a short summary of the CreditProvider
9 properties 9 required
ContactType
object
Can be managed at /resources/contact-type
3 properties 3 required
Language
object
Can be managed at /resources/language
3 properties 3 required
PatchedUserSelf
object
Serializer to update the user himself
23 properties
Profile2Phone
object
4 properties 1 required
MinimalBroker
object
Broker minimal representation
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oper-me-api-openapi.yml Raw ↑

Other APIs Oper publishes across the network.

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

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