Given you have jmeter
in tags here is a JMeter-related solution.
Load testing is the process ensuring that the application can handle the anticipated load hence the process of load testing a web application is simulating real users using real browsers accessing the web application.
So you don't need to know about the APIs or backend technologies, you need to perform some form of black-box testing and all you need to do is to replicate the network footprint of the real users which are using real browsers.
Browsers don't do any magic, they just send HTTP Requests, receive responses and render the responses so you could see it. JMeter can send the same HTTP Requests using HTTP Request sampler (and some configuration elements so JMeter would behave like a real browser)
Assuming all above you need to do the following:
- Record your application usage scenario(s) using JMeter's HTTP(S) Test Script Recorder and your browser
- Perform correlation of dynamic parameters and parameterization of i.e. user credentials so each JMeter thread (virtual user) would use its own login/password combination
- Dry-run your test with 1-2 users/iterations to ensure that it's doing what it's supposed to be doing by looking into requests and responses details in the View Results Tree listener
- Run your test with the anticipated number of virtual users
- Analyze the results using HTML Reporting Dashboard, identify bottlenecks if any, raise issues, etc.