API Testing and Automation with real time Project APIs

Obtain API access credentials, log in to create a bearer authorization token, and use that token to call a get endpoint that returns company data.

Generate a token using a post request with a valid body, then use bearer authentication to access real-time apis, noting token expiration and driver data.

Learn to generate an API request using a token. Create a get driver endpoint in your collection, configure the URL, method, and token authorization, then send to retrieve all drivers.

Learn how an application programming interface enables automated access to weather information with crud operations, authentication, and access control, turning weather data into a monetizable service.

Explore why we need APIs, including authentication, access control, and monetization through usage caps. See how APIs improve performance and reduce dependencies by delivering data you need across languages.

Explore what an API is through real-world examples from weather, social media, and cloud providers, and learn how hospitals fetch patient data using cloud APIs.

Explore the core api components, including url, path, methods, parameters, authorizations, tokens, headers, body, and status codes, and learn to interpret responses like 200, 400, 500 for real-time project APIs.

Explore api components such as url path, methods, parameters, authorizations, headers, and body, and understand response codes like 200, 400, and 500 to hit and interpret api responses.

Learn how API parameters filter results and configure requests, including when parameters are optional or mandatory. Use Postman to specify key and value and retrieve data accordingly.

Learn how API authorization controls access using tokens, API keys, and common authentication methods, and implement bearer token authentication in Postman.

Master API methods that drive endpoint operations: read, create, update, partial update, and delete, and learn how to choose the right method, supply authentication, and use Postman with documentation.

Understand the api body or payload as data to create a new resource, and consult documentation or swagger, e.g., post driver api, to receive a 200 response.

Explore API responses and common status codes, including 200 ok, 201 created, 202 accepted, 400s and 500s, and learn how to test them with Postman.

Learn to read api documentation, test and automate api checks, and perform data validation across api and etl processes, including data types, formatting, constraints, null checks, and dependencies.

Open postman, create or sign in to an account (log in with Google), and start testing APIs by organizing collections in a workspace with authentication, test scripts, and environment variables.

Learn to create your first Postman request within a collection, configure URL, methods, parameters, headers, and authorization, and run pre-request scripts and tests to verify a 200 status code.

Review Postman logs and the console to see the exact request, url, header, body, and response, enabling quick debugging of API errors.

Explore how get endpoints fetch information across driver, policy, and vehicle APIs, using a URL, bearer token, and filters, like a SQL select statement.

Learn to use the driver get endpoint in Postman with bearer token authentication, then filter results by last name or by driver ID to fetch all or a single driver.

Explore policy get APIs through a get operation using an authorization token, fetch all policies or a specific one by policy ID or number, and use query parameters.

Learn how to use get endpoints to fetch policies, vehicles, driver addresses, policy coverage, and payment details from a real-time auto insurance API, with URL parameters and single-item retrieval.

Learn how post APIs create new resources via a URL and payload, sometimes to fetch data, and require parameters and authorization tokens, with live examples and API documentation.

Create a new driver via the driver post api with required fields and a unique phone; the post returns 201 and can be verified by get by id.

Create new vehicles with the vehicle post API by sending a post request with a unique VIN. Verify results using the get vehicle endpoint and the assigned ID.

Create a new policy with the policy post endpoint and verify it with the get endpoint, ensuring a unique policy number and data matching policy id, amount, and monthly.

Post a new driver address using the post endpoint with city, state, zip code, and driver id. Then verify creation via the get driver address endpoint.

This lecture demonstrates using put to update an entire record and patch to update one or more fields, requiring the record ID and request body, with verification via get endpoint.

Learn how to use the driver patch endpoint to update a driver's first name and verify the change with the get endpoint, demonstrating patch and get workflows.

Explore put and patch endpoints for vehicle resources, updating mileage and verifying changes with get requests, and learn how to use these methods for basic API operations.

Update driver address through put and patch endpoints in real time project APIs, verify changes with get requests, and understand put requires full records while patch updates only targeted fields.

Explore policy coverage management by using put and patch endpoints to update entire records or single fields, validating changes with get endpoint retrieval.

Delete endpoints remove a resource by object ID, returning 200 on success and 404 when not found, demonstrated on driver, policy, and vehicle objects.

Learn to create environments and use variables in Postman to test development, QA, and production APIs across stages and improve overall quality.

Set up and reuse environment variables in Postman to streamline API testing by creating a dev auto insurance environment, defining a URL variable, and applying it across requests.

Define postman variables to automate tests and avoid manual entry. Use a base URL variable with double curly braces across endpoints and body.

Discover how to automate token management by using tests to store access tokens in variables, create token two, and auto-refresh tokens when expired for API requests.

Explore API documentation and learn to read how each field behaves, including limits and constraints, and understand formats like user stories, PDFs, or spreadsheets for testing and automation.

Explore the driver API documentation and learn how to read fields, data types, required flags, formats, and uniqueness. Apply testing strategies with validation, alphanumeric constraints, and sample test cases.

Explore vehicle API documentation and learn to test each field against data types, required and unique constraints, and business rules. Develop test scenarios for year, VIN, and state.

Explore policy api documentation, examine field types, constraints, and test cases, including unique policy numbers, alphanumeric limits, not-null constraints, and the monthly premium calculation from total.

Explore the driver address API documentation, test field validation (zip formats, required vs optional fields), and verify data flow with post and get endpoints while documenting results.

Explore policy coverage API documentation and inspect fields like name, data type, auto, visible, required, and optional lists; test valid and invalid codes and coverage names via post requests.

Explore driver API testing by validating the first name field against requirements (alphanumeric only, no special characters, max 20 characters) using the driver post endpoint with authentication.

Learn to validate the driver first name using Postman, verify 201 for valid input and 400 for missing or invalid data, and document test cases with prepared data.

Test the driver endpoint's first name validation, documenting key scenarios and exploring out of the box cases to uncover defects and improve application quality.

Explore testing the driver post endpoint by probing the first name field for corner cases, asking questions about uniqueness, spacing, error messages, and length limits to improve application quality.

Post driver last name to the driver endpoint, ensure the last name is a required field with max 20 characters, and validate 201 for valid inputs and 400 for errors.

Test driver last name validation in an api using Postman, verify success with valid input, and document results and status codes for blank, missing, and invalid characters.

Validate driver email addresses by enforcing required fields and a specific format with an add sign, domain, and dot extension; cover positive and negative test cases to improve application quality.

Practice email validation testing in Postman against the driver endpoint, exploring valid and invalid emails, missing fields, and negative scenarios, and document results for team review.

Learn to test the vehicle post endpoint by selecting fields like registration state and VIN, validate year ranges, create test data and cases, run tests in Postman, and document results.

Document and evaluate vehicle year validation tests, create test data and scenarios, capture actual vs expected results, and explore unique error messages for incorrect or blank years in API testing.

Test the vehicle post endpoint by crafting test data and test case outlines to validate the year field between 1840 and 2023, including happy path and error scenarios.

Explore vehicle vin validation for a post endpoint, confirming alphanumeric input up to 20 characters, testing cases, and expected 201 or 400 responses.

Explore how to test vehicle VIN validation in real-time APIs by examining case sensitivity, spacing, and validity rules, and how to validate behind the scenes with government-assigned VINs.

Examines vehicle post endpoint validation for registered state, accepting full names and CA abbreviation, with positive and negative test cases, and documenting results and potential defects.

Explore testing the policy post endpoint by validating policy number, payment option, and calculated monthly premium via get and post requests, with positive and negative scenarios and test cases.

Explore policy post endpoint validation in Postman by testing policy number, total amount, and monthly fields, verifying monthly premium calculations, date formats, and payment option constraints, and logging defects.

Document each test case in a format, including test case number, outline, api url, method, headers, authorization, test data, steps, and expected vs actual results, plus defect template and IDs.

document a defect with full details, including ID, description, reproduction steps, and the expected and actual results. record reproducibility and assign ownership, including API URL and API method.

Learn how to generate unique data in Postman using random functions to create unique phone numbers and social security numbers for API testing of new driver endpoints.

Test date of birth and Social Security number fields in driver API by creating test cases and data, then document results. Build confidence in API testing by reading requirements.

Explore Postman validation functions for test cases, including headers, JSON values, cookies, response times, one-off validations, and conditional logic, with logging and custom code as needed.

Develop hands-on expertise in testing auto insurance APIs by examining driver, policy, vehicle, and address endpoints, documenting test cases, and validating data fields and formats.