API Documentation

Professional Profile Endpoint

Structured profile data for tools that need identity, contact paths, projects, experience, skills, and API discovery metadata in one response.

Usage Example

curl https://suleman.me/api/profile

Response Schema

meta

API version, generated timestamp, source, and cache policy.

identity

Name, professional title, location, and positioning summary.

contact

Email, website, GitHub, LinkedIn, and resume links.

projects

Machine-readable project and case-study entries.

experience

Company, role, period, URL, and evidence-backed highlights.

skills

Featured skills and grouped skill categories.

api

Endpoint discovery metadata and OpenAPI link.

Example Response

{
  "identity": {
    "name": "Suleman Tariq",
    "title": "Senior Software Engineer and Tech Lead"
  },
  "contact": {
    "email": "suleman1220@gmail.com",
    "resume": "https://suleman.me/Resume.pdf"
  },
  "api": {
    "openapi": "https://suleman.me/api/openapi.json"
  }
}

Project Case Studies With Filtering

Portfolio projects and case-study slices with stack, role, outcomes, source links, and normalized domain tags.

Query Parameters

domain

Optional normalized project domain. Available values are listed below.

Usage Example

curl https://suleman.me/api/projects
curl https://suleman.me/api/projects?domain=ai

Response Schema

query.domain

The normalized domain filter used for this response, or null.

filters.domains

All supported domain values for client-side filter UIs.

data[].name

Project or case-study slice name.

data[].role

Role and core stack used on the project.

data[].outcome

Concise business or technical outcome for quick review.

data[].domains

Normalized tags such as ai, api, payments, or leadership.

data[].source

Source case-study link backing the project entry.

Example Response

{
  "query": { "domain": "ai" },
  "filters": {
    "domains": ["ai", "api", "payments", "realtime"]
  },
  "data": [
    {
      "name": "Token Metrics MCP Server",
      "domains": ["ai", "api", "crypto", "infra"],
      "outcome": "Built a production MCP server exposing 20+ crypto analytics tools to AI clients."
    }
  ]
}

Grouped Skills Endpoint

Skill groups aligned to the portfolio homepage, including featured technologies for quick human and ATS parsing.

Usage Example

curl https://suleman.me/api/skills

Response Schema

data.featured

Short list of highest-signal technologies.

data.groups[].name

Skill group name, such as Core or Backend and Infra.

data.groups[].items[]

Skill names and optional canonical documentation URLs.

Example Response

{
  "data": {
    "featured": ["TypeScript", "Next.js", "React", "Node.js"],
    "groups": [
      {
        "name": "Core",
        "items": [{ "name": "TypeScript", "url": "https://www.typescriptlang.org" }]
      }
    ]
  }
}

Role Fit Evidence Endpoint

A role-fit summary backed by concrete project and experience evidence instead of an arbitrary score.

Usage Example

curl https://suleman.me/api/hireability

Response Schema

data.targetRoles

Best-fit senior engineering and tech lead role types.

data.strongestFits

Work environments and problem areas with strongest evidence.

data.impactMetrics

Quantified impact signals from the portfolio.

data.signals[]

Named hiring signals with summaries, evidence, and source links.

data.availability

Location, contact links, and professional contact note.

Example Response

{
  "data": {
    "targetRoles": ["Tech Lead", "Senior Full-Stack Engineer"],
    "impactMetrics": ["70% faster navigation across 100K+ monthly sessions"],
    "signals": [
      {
        "name": "AI and agent-facing API systems",
        "evidence": ["Built a production MCP server exposing 20+ crypto analytics tools to AI clients."]
      }
    ]
  }
}

OpenAPI Schema Endpoint

OpenAPI 3.1 document for tools that want to discover and call the public portfolio API from a standard contract.

Usage Example

curl https://suleman.me/api/openapi.json

Response Schema

openapi

OpenAPI version string. This API currently uses 3.1.0.

info

API title, version, and description.

servers

Production base URL for the portfolio API.

paths

Callable endpoint definitions and query parameters.

components.schemas

Reusable response schemas for public API responses.

Example Response

{
  "openapi": "3.1.0",
  "info": {
    "title": "Suleman Tariq Portfolio API",
    "version": "1.0.0"
  },
  "paths": {
    "/api/profile": { "get": { "operationId": "getProfile" } }
  }
}