#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/system-design-interview-prep/interview-framework-methodology/api-design-in-interviews

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░██████████████████████████████████████████████████████████████████████████████████████████████████████████████████

#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/system-design-interview-prep/interview-framework-methodology/api-design-in-interviews

Repovive

API Design in Interviews - Interview Framework & Methodology | System Design Interview Prep | Repovive

Repovive.

System Design Interview Prep22 sections · 691 units23h total

Open in Course

API Design in Interviews

Defining interfaces

Define your APIs after high-level design:

REST example:

POST /tweets
  body: { text, media_ids }
  returns: { tweet_id, created_at }

GET /timeline?user_id=X&cursor=Y
  returns: { tweets[], next_cursor }

Key decisions to explain:

Pagination strategy (cursor vs offset)
Authentication (API key, OAuth token)
Rate limiting headers
Versioning (/v1/tweets)

You don't need complete OpenAPI specs. Show $2$ - $3$ key endpoints. Demonstrate you understand REST conventions and pagination.