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

upGrad Partner Service API

Channel-partner operations API for upGrad's referral and franchise network: partner onboarding and KYC document upload/verification, prospect (lead) capture and status transitions, store and team-member hierarchy management, commission rules, and partner invoice / credit-note reporting. 54 operations across 46 paths, secured by an AUTH-TOKEN API key header. The springdoc-generated OpenAPI is served anonymously at https://partner.upgrad.com/api-docs while every operation itself requires credentials.

This API exposes 54 operations across 46 paths, organized into 15 resource areas, and defines 45 schemas. It is described by OpenAPI 3.0.1, at version 1.

Requests are made against a single base URL, https://partner.upgrad.com.

54 operations 46 paths 45 schemas 3 DELETE26 GET16 POST9 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1
Base URL
https://partner.upgrad.com
Authentication
API Key
License
Resource Areas
15

Authentication & Security 1

upGrad Partner Service API declares 1 security scheme for authenticating requests. An API key is passed in the header as AUTH-TOKEN (AUTH-TOKEN). By default, every request must be authenticated.

Paths & Operations 54

Across 46 paths, the API surfaces 54 operations — 3 DELETE, 26 GET, 16 POST, 9 PUT. They span 15 resource areas, including partner-controller, prospect-controller, status-controller, partner-invoice-credit-note-controller, team-member-controller, store-controller, commission-rule-controller, login-list-upload-controller, and 7 more. Each is listed below with its method, path, parameters, and response codes.

partner-controller 7
PUT
/vpc-only/user/{userId}/vendorCode
updateVendorCode 2 params → 500400409405503404403429
PUT
/user/{userId}/address-status
updateAddressStatus 2 params → 500400409405503404403429
PUT
/update-rm-id
updateRmId body → 500400409405503404403429
GET
/user/{userId}/partner-detail
getPartnerInfo 1 param → 500400409405503404403429
POST
/user/{userId}/partner-detail
savePartnerDetails 1 param body → 500400409405503404403429
GET
/sap/ug-partners
getUgPartners → 500400409405503404403429
GET
/partner-list
getPartners 5 params → 500400409405503404403429
prospect-controller 4
PUT
/vpc-only/prospect/{leadId}/{lsqEmail}
updateProspect 2 params → 500400409405503404403429
GET
/prospect
getProspects 2 params → 500400409405503404403429
POST
/prospect
saveProspect body → 500400409405503404403429
GET
/prospect/{prospectId}/lead/{leadId}
getProspect 2 params → 500400409405503404403429
status-controller 3
PUT
/user/{userId}/partner/stage/{type}
updatePartnerStage 2 params body → 500400409405503404403429
POST
/save-status
saveStatusData body → 500400409405503404403429
GET
/partner-status
fetchLabelsByStatusTypes 3 params → 500400409405503404403429
partner-invoice-credit-note-controller 6
PUT
/update-partner-invoice-credit-note
updatePartnerInvoiceCreditDetails 2 params → 500400409405503404403429
POST
/invoice/{userId}/document
uploadInvoiceDocument 4 params body → 500400409405503404403429
GET
/partner-invoice-credit-note-report
getPartnerInvoiceCreditNoteReport 10 params → 500400409405503404403429
GET
/invoice-status-flow
getInvoiceStatusFlow 1 param → 500400409405503404403429
GET
/invoice-document-url/{dmsUploadId}
getInvoiceDocumentUrl 1 param → 500400409405503404403429
GET
/invoice-credit-note-dashboard
getPartnerInvoiceCreditNoteDashboard 1 param → 500400409405503404403429
team-member-controller 8
GET
/team-member/{teamMemberId}
getTeamMemberDetail 1 param → 500400409405503404403429
PUT
/team-member/{teamMemberId}
partialUpdateTeamMember 1 param body → 500400409405503404403429
GET
/team-member
getTeamMembers 2 params → 500400409405503404403429
POST
/team-member
saveTeamMember 1 param body → 500400409405503404403429
POST
/team-member/business-owner/{userId}
createBusinessOwnerAsMember 2 params → 500400409405503404403429
GET
/team-member/{userId}/manager/{teamMemberId}
getTeamMembersByManger 2 params → 500400409405503404403429
GET
/team-member/{teamMemberId}/hierarchy
getTeamHierarchy 1 param → 500400409405503404403429
GET
/team-member/{teamMemberId}/count
getMemberAndProspectAndStoreCount 2 params → 500400409405503404403429
store-controller 5
GET
/store/{storeId}
getStoreDetail 3 params → 500400409405503404403429
PUT
/store/{storeId}
updateStoreDetail 1 param body → 500400409405503404403429
DELETE
/store/{storeId}
deleteStoreDetail 1 param → 500400409405503404403429
GET
/store
getStoreList 3 params → 500400409405503404403429
POST
/store
saveStoreDetail 1 param body → 500400409405503404403429
commission-rule-controller 4
GET
/commission-rule
getCommissionRules 2 params → 500400409405503404403429
PUT
/commission-rule
updateCommissionRule body → 500400409405503404403429
POST
/commission-rule
saveCommissionRule body → 500400409405503404403429
GET
/commission-rule/{commissionId}
getCommissionDetail 1 param → 500400409405503404403429
login-list-upload-controller 1
POST
/vpc-only/login-list
saveLoginListUploadDetails 1 param → 500400409405503404403429
partner-document-controller 4
POST
/user/{userId}/verify/document
verifyDocument 1 param body → 500400409405503404403429
POST
/user/{userId}/partner/document
uploadPartnerDocument 5 params → 500400409405503404403429
GET
/user/{userId}/partner/documents
getPartnerDocuments 1 param → 500400409405503404403429
DELETE
/user/{userId}/partner/co-partner/{partnerCoOwnerId}
deleteCoOwner 2 params → 500400409405503404403429
login-list-controller 2
POST
/upload-csv-details
uploadCsvDetails → 500400409405503404403429
GET
/hit-scheduler-process-credit-note-and-invoice-data
getLoginListData → 500400409405503404403429
program-key-cache-controller 3
POST
/program-key-cache/update
updateProgramKeyCache → 500400409405503404403429
GET
/program-key-cache
getProgramKey 1 param → 500400409405503404403429
DELETE
/program-key-cache
deleteProgramKey 1 param → 500400409405503404403429
form-config-controller 3
POST
/form-config/delete-form
deleteFormConfigStep body → 500400409405503404403429
POST
/form-config/add
addFormConfig body → 500400409405503404403429
GET
/form-config/{partner}
fetchAllFormConfigByPartner 2 params → 500400409405503404403429
business-type-controller 2
POST
/business-type/add
addFormConfig_1 body → 500400409405503404403429
GET
/business-type
fetchAll → 500400409405503404403429
master-data-controller 1
GET
/partner/master-data/{type}
getMasterData 1 param → 500400409405503404403429
learner-invoice-credit-note-controller 1
GET
/learner-inv-cn-details
getPartnerInvoiceCreditNoteReport_1 3 params → 500400409405503404403429

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are LearnerInvoiceCreditNoteDto (29 properties), PartnerInvoiceCreditNoteReportDto (25 properties), PartnerDto (25 properties), ProspectDto (20 properties). Each schema is shown below with its type and property counts.

ErrorContext
object
3 properties
UpdatePartnerStageRequestDto
object
5 properties
UpdateRmIdDto
object
2 properties
StoreDto
object
13 properties
CommissionRuleDto
object
15 properties
CommissionRuleSlabDto
object
5 properties
LoginListUploadDto
object
5 properties
DocumentVerifyRequest
object
3 properties
DMSUploadResponse
object
1 property
CoPartnerDto
object
4 properties
DocumentDto
object
8 properties
DocumentResponse
object
3 properties
PartnerBaseDto
object
16 properties 3 required
TeamMemberDto
object
19 properties
MemberDto
object
16 properties
TeamMemberResponseDto
object
19 properties
StatusDto
object
3 properties
ProspectDto
object
20 properties
UserDto
object
9 properties
DeleteFormConfigRequest
object
2 properties
AddFormConfigRequest
object
5 properties
AddBusinessTypeRequest
object
3 properties
PartnerDto
object
25 properties 3 required
PartnerStageDto
object
7 properties
PartnerStatusSummary
object
4 properties
Pageable
object
3 properties
Predicate
object
PageResponseTeamMemberResponseDto
object
2 properties
PageResponseTeamMemberDto
object
2 properties
StoreFilterDto
object
7 properties
PageResponseResponseStoreDto
object
2 properties
ResponseStoreDto
object
15 properties
PageResponsePartnerDto
object
2 properties
ProspectFilterDto
object
15 properties
PageResponseProspectDto
object
2 properties
PageResponsePartnerInvoiceCreditNoteReportDto
object
2 properties
PartnerInvoiceCreditNoteReportDto
object
25 properties
LearnerInvoiceCreditNoteDto
object
29 properties
PageResponseLearnerInvoiceCreditNoteDto
object
2 properties
InvoiceStatusFlowDto
object
4 properties
UserUploadedEventTempUrlDto
object
1 property
PartnerInvoiceCreditNoteDashboardDto
object
3 properties
FetchFormConfigResponse
object
5 properties
PageResponseCommissionRuleDto
object
2 properties
FetchBusinessTypeResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

upgrad-partner-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of upGrad Partner Service 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.