Deep Researches

icon picker
API QA as a Service

Briefing:

Many companies develop APIs to dock on → , PosterXXL, etc
Nearly every API includes errors, or is badly documented
It is not easy to get into the API
Possible Solution:
Offer API Testing as a service
Test out API
Find errors
Test out Documentation
Is it easy to get into it?

API Development tools

open source and professional toolset
API Design, Development, Documentation, Testing, Mocking & Virtualization, Governance, Monitoring
API Testing
functional, security, and performance testing
Swagger Inspector provides capabilities to easily inspect API request-responses, and make sure they work as expected
Automated API Testing with
API marketplace → An API for APIs(more than 20K)
connect to thousands of public APIs
Monitoring of the performance
RapidAPI Testing Tool
Create customizable functional test flows
Monitor and manage API tests across multiple geographies
one-click API mock server

Available API testing services

Note Daniel: So an observation is that we are with that getting into the software testing market. I would assume (no Idea if true) that a lot of testing is related to security (penetration testing etc.)
Expertise on a wide range of API protocols like XML, SOAP, JSON, REST, Gdata, YAML, ATOM, RSS, and RDF etc.
End to end applications validation experience at various layers of the application.
Expertise on leading industry tools for API testing for functional, load, and security testing.
Automation of API test cases.
API specification review
Analyzing requirements
Test documentation development
Test framework development
Integration test suite with CI/CD server
Test execution & reporting
Micro Services: Web API, REST API, SOAP UI, JSON/XML, HTTP/HTTPs, Basic Auth/ OAuth, API calls,
API functional testing, data testing, interoperability testing, and load testing
API test case scripting and services mocking
API testing in CI/CD/DevOps environment and cloud environments
API testing tools/frameworks evaluation, selection, and customization
Public API testing: developer experience testing and documentation testing

Different Considerations

Looking at German market first:
There are API-companies () whose business model relies completely on API, I would assume that most stuff here is optimized as it is their core business → NO LOW HANGING FRUITS AND HARD TO STANDARDIZE → not our focus
There are companies whose core business model works through a User Interface (PosterXXL, Immoscout etc.) but who also offer APIs for specific user group. Those are the APIs that potentially can be improved with our idea. The question here is, whether the API is important enough to justify an investment (the ROI has to be good) → I would focus on those and understand what USP is appealing to them
Offering: Also maybe Offer connection to NoCode Tools/Zapier
Later I will message
Poster XXL Head of customer service: Für einen Kunden mussten wir eure API anbinden, war leider sehr schlechte Expirience, habt ihr Lust auf Feedback dazu? → richtigen Ansprechpartenr kriegen + im Call Pain Points und Prio der API lernen. Am Ende sagen, dass man vllt was in dem Bereich anbieten möchte, meldet sich dann nochmal
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.