Software Engineering › Key terms › Y12 Secure Software Architecture › Application programming interface (API)
Application programming interface (API)
Term Key terms bank Y12 Secure Software Architecture
Also listed as: API
Definition
A set of rules that lets one program request services or data from another, often over HTTP using JSON. A safe API validates input, authenticates callers, limits data returned and uses HTTPS.
Example: Return only the fields the client needs.
Found in: syllabus, school notes.
Rules letting software components request data or services from each other.
Where it is used in the test
Syllabus area: Y12 Secure Software Architecture.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Short answer: Define, outline or explain it and tie it to the scenario.
- Extended response: Use it as a supporting point linked to the stimulus.
Where it has appeared in the paper
Secure Software Architecture (Part A). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q5 (1 mark): API vulnerabilities Secure Software Architecture (Part A) · 1 mark
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Study links
- Flashcard: Application programming interface (API) in Secure Software Architecture (Year 12) · study that set
- Memorise: Defensive data input handling: validation, sanitisation, error handling
- Key terms bank entry: API
- Notes: Safe APIs to minimise vulnerabilities (Secure Software Architecture (Year 12))
- Notes: Design, develop and implement a safe application programming interface (API) to minimise… (Secure Software Architecture (Year 12))
- Notes: Describe how collaborative work practices between front-end and back-end developers… (Programming for the Web (Year 12))
- Notes: Front-end and back-end collaboration (Programming for the Web (Year 12))
How to use it in an answer
A model sentence
“A set of rules that lets one program request services or data from another, often over HTTP using JSON.” Then apply it: Return only the fields the client needs.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
- Identify: Recognise and name. (2025 HSC Q5 (1 mark): API vulnerabilities)
Technique for the question types
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Extended response: Plan with the command word, give a judgement or explanation supported by named details from the stimulus, use course terms and cover both sides when asked.
Common mistakes
- Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
- Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.
Related terms
Same group in the syllabus: Defensive data input handling · Input validation · Sanitisation · Error handling · Excessive data exposure · Memory management · Session management · Exception management