Study guide
11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs
Praxis Computer Science 5652
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Praxis 5652 Exam Overview and ETS Pseudocode
1.1 Praxis 5652 Test Facts, Scoring, and Registration 1.2 Official ETS Pseudocode Notation and Tracing Strategy
2 Chapter 2: Impacts of Computing: Innovation, Access, and Effects
2.1 Computing for Creativity, Problem Solving, Communication, and Innovation 2.2 Equal Access, the Digital Divide, and Accessibility 2.3 Beneficial and Harmful Effects of Computing Innovations
3 Chapter 3: Impacts of Computing: Intellectual Property, Ethics, Privacy, and Security
3.1 Intellectual Property: Copyright, Open Source, and Creative Commons 3.2 Ethical and Unethical Computing Practices and Their Implications 3.3 Privacy, Security, Data Collection, and Local vs. Cloud Storage
4 Chapter 4: Algorithms and Computational Thinking: Abstraction, Decomposition, Number Bases, and Representation
4.1 Abstraction and Abstraction Hierarchies 4.2 Decomposition, Pattern Recognition, and Developing Algorithms 4.3 Number Bases: Binary, Octal, Decimal, and Hexadecimal 4.4 Algorithm Formats: Natural Language, Flowcharts, Pseudocode, and Tracing
5 Chapter 5: Algorithms: Efficiency, Limits of Computing, and Randomization
5.1 Algorithm Efficiency: Linear, Quadratic, Exponential, and Logarithmic Growth 5.2 Limits of Computing: Unsolvable Problems, Intractability, and Heuristics 5.3 Randomization, Random vs. Pseudorandom Numbers, and Scaling to a Range
6 Chapter 6: Algorithms: Searching, Sorting, and Recursion
6.1 Searching Algorithms: Linear Search and Binary Search 6.2 Sorting Algorithms: Tracing, Comparisons, Correctness, and Efficiency 6.3 Recursion: Base Cases, Tracing, Errors, and Iterative Equivalents
7 Chapter 7: Programming: Variables, Data Types, Strings, and Expressions
7.1 Variables, Data Types, and Type Conversion 7.2 Strings and String Operations 7.3 Operators, Precedence, Expressions, and Formulas 7.4 Boolean Expressions, Truth Tables, and Boolean Algebra
8 Chapter 8: Programming: Selection, Iteration, and Writing Code
8.1 Sequence and Selection: if, else, Chained and Nested Conditions 8.2 Iteration: for, while, do … while, and repeat … until Loops 8.3 Reading, Completing, and Modifying Code
9 Chapter 9: Programming: Procedures, Arrays, and Data Structures
9.1 Procedures, Parameters, Return Values, Nested Calls, and Scope 9.2 Arrays, Lists, and Two-Dimensional Arrays 9.3 Stacks, Queues, and Dictionaries (Maps)
10 Chapter 10: Programming: Correctness, Errors, Testing, and Code Quality
10.1 Program Correctness: Preconditions, Postconditions, Invariants, and Testing vs. Proof 10.2 Error Types and Debugging Techniques 10.3 Choosing Useful Test Cases: Boundaries, Partitions, Coverage, and Regression 10.4 Extensibility, Modifiability, and Reusability: Constants and Parameterization 10.5 Documentation, Code Reviews, Peer Feedback, and End-User Feedback
11 Chapter 11: Programming: Events, Usability, Input Validation, and APIs
11.1 Event-Driven Programming, Asynchronous Events, and Concurrency 11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification 11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs
12 Chapter 12: Programming: Languages, Tools, Paradigms, and Object-Oriented Design
12.1 Low- and High-Level Languages, Compilers and Interpreters, and IDEs 12.2 Programming Paradigms: Procedural, Object-Oriented, and Others 12.3 Classes, Objects, Instance Variables, Methods, and Encapsulation 12.4 Inheritance, Polymorphism, and Overloading vs. Overriding
13 Chapter 13: Data: Bits, Encoding, Compression, and Encryption
13.1 Bits and Bytes: Why Binary, Storage Calculations, and Signed Integers 13.2 Encoding Text, Images, and Sound 13.3 Lossless and Lossy Compression: Run-Length Encoding, Huffman Coding, and Media Formats 13.4 Encoding vs. Encryption, Symmetric and Public-Key Encryption, and Their Trade-offs
14 Chapter 14: Data: Analysis Tools, Simulation, Storage, and Collection
14.1 Analyzing Data with Spreadsheets: Cleaning, Transforming, and Visualizing 14.2 Simulation and Modeling 14.3 Files, Databases, and Storage Requirements: Scale, Redundancy, and Backup 14.4 Collecting, Aggregating, and Generating Data: Public Data Sets, Surveys, Sensors, and Crowdsourcing
15 Chapter 15: Computing Systems: Hardware, Operating Systems, and Computing Environments
15.1 Hardware Components and the Fetch–Decode–Execute Cycle 15.2 Operating Systems, Software Components, and Resource Issues 15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems 15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored
16 Chapter 16: Networks, the Internet, the Web, and Cybersecurity
16.1 Network Types and Wired and Wireless Communication 16.2 Network Hardware and Layered Network Models (OSI and TCP/IP) 16.3 Network Performance: Bandwidth, Latency, Load, and Estimating Needs 16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability 16.5 The Web: HTTP, HTML and Markup Languages, Browsers, Servers, and Clients 16.6 Cybersecurity: The Five Pillars, Strong Passwords, Security Strategies, and Trade-offs
11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs
Key Takeaways Explain This Topic AI
A library is a collection of prewritten, reusable code; an API (application programming interface) is the documented set of procedures, parameters, and return values through which a program uses a library or service.
To use an API correctly, match each argument to the parameter in the stated order and type, and store or use the returned value; calling sqrt ( x ) on a line by itself computes a result and then discards it.
Reasons to use a library include saving time and relying on tested, efficient, secure, standard code.
Reasons not to use a library include license terms or cost, dependency and security risks, unneeded size, platform limits, and learning goals that require students to write the algorithm themselves.
Math functions, random number generation, graphics, date and time handling, maps, weather data, payments, and speech recognition are all commonly provided through APIs.
Last updated: September 2026
What this competency asks
ETS asks you to know how to use libraries and APIs :
Identify correct call(s) and use of return values given an API definition .
Identify reasons to use or not use libraries in place of writing original code.
Identify applications (for example, math libraries and random number generation) that use APIs.
Libraries and APIs
A library is a collection of prewritten code, such as procedures and classes, that programs can reuse. An API (application programming interface) is the contract for using that code: the names of the procedures, their parameters and types, what they return, and what they do. An API is an abstraction (Section 4.1). You need to know what a procedure does, not how .
APIs also connect programs to services over the Internet. A web API lets a program send a request, for example for a weather forecast for a ZIP code, and receive a structured response, often in JSON format. Web APIs commonly require an API key and limit how many requests you can make.
Reading an API definition
Questions supply a table like this one. Use exactly what it says.
- Procedure Description
- double pow ( double base, double exponent ) Returns base raised to the power exponent
- double sqrt ( double x ) Returns the square root of x; precondition: x ≥ 0
- int abs ( int x ) Returns the absolute value of x
- int randomInt ( int low, int high ) Returns a random integer from low to high, inclusive
Checks for every call:
Name and number of arguments: pow needs two arguments.
Order: pow ( 2, 10 ) is 2¹⁰ = 1024, but pow ( 10, 2 ) is 100.
Types: pass the types listed. The return type tells you what kind of variable can hold the result.
Preconditions: sqrt requires x ≥ 0. Check or validate before calling.
Use the return value: store it, print it, or use it in an expression.
- Correct and incorrect use // Distance between points (x1, y1) and (x2, y2)
- double d ← sqrt ( pow ( x2 - x1, 2 ) + pow ( y2 - y1, 2 ) )
- // Roll a die
- int roll ← randomInt ( 1, 6 )
- // BUG: the return value is discarded; x is unchanged
- sqrt ( x )
- print x
- // FIX
- double root ← sqrt ( x )
- print root
A frequent distractor calls a value-returning procedure as if it changed its argument . abs ( n ) does not change n ; n ← abs ( n ) does.
Class-based APIs work the same way. ETS's sample string question gives a table for a String class ( substring , toUpperCase , length ) and asks which sequence of calls produces a given output. Method calls use dot notation: value.toUpperCase ( ) .
Why use a library?
- Benefit Explanation
- Saves time No need to write and debug common functionality
- Reliability Widely used libraries have been tested by many programmers
- Efficiency Library code is often carefully optimized
Security Getting cryptography, password hashing, and input parsing right is hard; vetted libraries avoid subtle flaws
Standardization Other programmers recognize and understand common libraries
Access to services APIs connect to maps, payments, weather, and machine learning that you could not build yourself
Why not use a library?
Reason Example
License or cost A library's copyleft license conflicts with a closed-source product, or its price is too high (Section 3.1)
Dependency risk The library is abandoned, changes its API in a breaking way, or has a security vulnerability that affects every program using it
- Size and performance A huge library is used for one small function; a tiny embedded device cannot hold it
- Poor fit It does not quite meet the requirements, and working around it costs more than writing custom code
Privacy or availability A web API sends user data to a third party, or fails when the service is down or rate-limited
Learning goals In a CS class, students write their own sort or search to understand the algorithm, even though a library version exists
For a teacher, the last row matters. "Why not just call sort ?" is a fair question in industry, but in a classroom the goal may be learning the algorithm itself.
Applications that use APIs
- Area Typical API use
- Math Square roots, powers, trigonometry, rounding
- Random number generation Dice, shuffles, simulations (Section 5.3)
- Graphics and games Drawing shapes, handling sprites and sound
- Date and time Time zones, calendars, measuring elapsed time
- Files and networking Reading files, sending web requests
- Maps and location Geocoding addresses, directions
- Data and science Statistics, charts, machine-learning models
- Communication Sending email or text messages; signing in with an existing account
- Payments Card processing through a payment provider's API
- Accessibility and AI Speech-to-text, text-to-speech, translation
- Documentation makes an API usable
A good API comes with documentation that states each procedure's purpose, parameters, return value, preconditions, errors, and an example (Section 10.5). When you write your own procedures for others to call, you are designing an API, so give it the same care.