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 Form Config Controller API

The form-config-controller API from upGrad — 3 operation(s) for form-config-controller.

upGrad Form Config Controller API is one of 18 APIs that upGrad publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include form-config-controller. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 3 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.

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

3 operations 3 paths 4 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

upGrad Form Config Controller 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 3

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

form-config-controller 3
POST
/form-config/delete-form
Delete form config step
deleteFormConfigStep body → 500400409405503404403429
POST
/form-config/add
Add form config
addFormConfig body → 500400409405503404403429
GET
/form-config/{partner}
Fetch all form config by partner
fetchAllFormConfigByPartner 2 params → 500400409405503404403429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are AddFormConfigRequest (5 properties), FetchFormConfigResponse (5 properties), ErrorContext (3 properties), DeleteFormConfigRequest (2 properties). Each schema is shown below with its type and property counts.

FetchFormConfigResponse
object
5 properties
ErrorContext
object
3 properties
DeleteFormConfigRequest
object
2 properties
AddFormConfigRequest
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

upgrad-form-config-controller-api-openapi.yml Raw ↑

Other APIs upGrad publishes across the network.

upGrad Admin Controller API
upGrad Business Type Controller API
upGrad Commission Rule Controller API
upGrad Leader Board Controller API
upGrad Learner Invoice Credit Note Controller API
upGrad Login List Controller API
upGrad Login List Upload Controller API
upGrad Master Data Controller API
upGrad Micro Interaction Notification Controller API
upGrad Partner Controller API
upGrad Partner Document Controller API
upGrad Partner Invoice Credit Note Controller API
Where this information came from

This is an independent, third-party profile of upGrad Form Config Controller 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.