API Penetration Testing
APIs are where modern breaches happen. We test your REST, GraphQL and gRPC endpoints for broken authorisation, data leakage and logic flaws, so the interfaces powering your apps and partners can't be turned against you.
Verified Solvex Specialist
Verified by SolvexDirect specialist contact for Solvex engagements
What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.
Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.
Signed authorization required. This engagement is performed only against systems you own or are contractually authorized to have tested, under an agreed scope. See the responsible testing policy.
What's covered
- OWASP API Security Top 10, including BOLA/IDOR and broken function-level authorisation
- Authentication, token scoping, and key/secret handling
- Rate-limiting, resource exhaustion and mass-assignment testing
- Excessive data exposure and improper inventory (shadow/zombie endpoints)
- GraphQL introspection, query depth and batching abuse
- Business-logic testing across chained API calls
What you receive
- Technical report with per-endpoint findings and requests/responses
- Executive summary and risk overview
- Prioritised remediation guidance with secure-design notes
- Free retest of remediated endpoints
- Attestation letter on completion
Evidence and reporting
How the work is kept honest- Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
- A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
- Signed scope firstTesting starts only after written scope and signed authorization for systems you own or are entitled to have tested.
Anyone holding a Solvex report can verify it publicly without seeing its contents.
Our boundaries
What this engagement does not do, stated before it starts.
- Only endpoints you own or are authorised to test
- No destructive load or denial-of-service testing without written consent
- No use of extracted data beyond proof of impact
- Third-party APIs excluded unless the provider authorises testing
How this engagement runs
- 01
Intake
Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.
- 02
Scope and authorization
Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.
- 03
Investigation or build
Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.
- 04
Evidence
Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.
- 05
Delivery
A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.
- 06
Verification and retest
Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.
Questions we are asked
- Do you test GraphQL and gRPC as well as REST?
- Yes. We cover REST, GraphQL and gRPC, adapting the methodology to each — for GraphQL that includes introspection, query-depth and batching abuse; for gRPC, schema and reflection analysis.
- What do you need to begin?
- API documentation or a collection (OpenAPI/Postman), test credentials or tokens for each role, and a signed scope. Good documentation makes testing faster and more thorough.
- Can you test without impacting our rate limits or data?
- Yes. We coordinate on a test environment where possible and tune request volume so testing stays safe and non-disruptive.
Related services
Offensive / Testing
Web Application Penetration Testing
We attack your web application the way a skilled adversary would — safely, under a signed scope — and hand you a clear map of every exploitable weakness. You get proof, business impact and a fix-it plan, not a raw scanner dump.
Offensive / Testing
Secure Source Code Review
Some flaws only reveal themselves in the code. Our experts read your source — by hand, guided by tooling — to find vulnerabilities, insecure patterns and design weaknesses that black-box testing can miss.
Web3 & Emerging
Web3 Application Penetration Testing
A dApp is more than its contracts — it's front-ends, wallets, APIs and integrations, each a potential weak point. We test the whole Web3 application stack so users interacting with your protocol stay safe end to end.