Telecom API standards and governance
API Standardization and TMF Conformance Automation for MTN Group
I worked on MTN Group's API TMF standardization programme through HestiaForge, supporting API assessment, TM Forum Open API mapping, compliance validation, and automation that made the work structured and inspectable.
- Role
- Software Engineer — API Analysis, Mapping, and TMF Compliance Validation
- Period
- 2026
API assessment workflow
From source landscape to reviewable conformance evidence
API repositories
Source extraction
OpenAPI enrichment
TMF standards mapping
Context
HestiaForge programme supporting MTN Group
Role
Software Engineer — API Analysis, Mapping, and TMF Compliance Validation
Product type
Telecom API standards and governance
Core capability
TM Forum Open APIs
Product context
Making a large API landscape assessable
A large API landscape spans repositories, service layers, implementation patterns, and operating contexts. The programme needed a repeatable way to catalogue existing APIs, compare them with TM Forum standards, expose gaps, and make conformance analysis useful to engineering and governance teams.
Attribution anchor
What I was responsible for
I contributed inside a focused delivery squad, working across API analysis, standards mapping, code and repository inspection, structured extraction, OpenAPI enrichment, and product views used to review catalogue and conformance information.
Selected scope
Selected contributions
- 01
Supported API catalogue building, TM Forum Open API mapping, gap analysis, and compliance-validation workflows.
- 02
Built and improved Java/Spring source extractors and repository-scanning automation.
- 03
Helped connect aggregator APIs to downstream system dependencies through inspectable service graphs.
- 04
Worked on OpenAPI 3 enrichment, type and schema resolution, discriminator handling, and registry/explorer concepts.
- 05
Contributed to catalogue, scoring, CI/CD visibility, role-based access, and governance dashboard workflows.
Evidence, not reconstruction
System view
A simplified view of verified responsibilities and system relationships. It does not reproduce a private or historical interface.
API assessment workflow
From source landscape to reviewable conformance evidence
A public-safe view of the engineering sequence, with programme-specific data removed.
API repositories
Java/Spring implementations and available API artifacts.
Input
Source extraction
Repository scanning, code inspection, endpoint discovery, and structured output.
Process
OpenAPI enrichment
OAS 3, type and schema resolution, and discriminator handling.
Process
TMF standards mapping
Catalogue alignment, gap analysis, evidence, and reviewer context.
Process
Dependencies and catalogue
Inspectable downstream relationships and catalogue views.
System
Governance review
Scoring and evidence remain available for human assessment.
Output
Verified relationships
- API repositoriesSource extraction
- Source extractionOpenAPI enrichment
- OpenAPI enrichmentTMF standards mapping
- TMF standards mappingDependencies and catalogue
- Dependencies and catalogueGovernance review
Engineering judgment
Selected technical decisions
Decision 01
Combined source analysis with OpenAPI artifacts so assessment could reflect implementation details rather than documentation alone.
Decision 02
Used Python automation around Java/Spring inspection to turn repetitive discovery work into a reusable pipeline.
Decision 03
Kept standards mapping, evidence, scoring, and governance views connected while preserving a human review step.
Technology context
- TM Forum Open APIs
- OpenAPI / OAS 3.0
- Java / Spring analysis
- Python automation
- Repository scanning
- Schema resolution
- Dependency graphs
- API catalogues
- Governance workflows
- RBAC
Delivered capability
“A more structured, repeatable, and inspectable approach to API discovery, mapping, and conformance analysis—not a claim that an entire API estate became conformant or certified.”
API discovery · OpenAPI automation · Standards governance