<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sisi Nene on Medium]]></title>
        <description><![CDATA[Stories by Sisi Nene on Medium]]></description>
        <link>https://medium.com/@amugogracen?source=rss-6bb78da3cb28------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5HGThNVJiWlkxAuI7Jf0XQ.webp</url>
            <title>Stories by Sisi Nene on Medium</title>
            <link>https://medium.com/@amugogracen?source=rss-6bb78da3cb28------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:44:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amugogracen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Step-by-Step Guide to Discovering APIs and Analyzing Endpoints with crAPI]]></title>
            <link>https://medium.com/@amugogracen/step-by-step-guide-to-discovering-apis-and-analyzing-endpoints-with-crapi-4335a44b18bf?source=rss-6bb78da3cb28------2</link>
            <guid isPermaLink="false">https://medium.com/p/4335a44b18bf</guid>
            <dc:creator><![CDATA[Sisi Nene]]></dc:creator>
            <pubDate>Sat, 22 Nov 2025 22:45:26 GMT</pubDate>
            <atom:updated>2025-11-22T22:45:26.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ufg88yNQJNjHLu-oVSs2Yw.jpeg" /></figure><p><strong>Hiii, I’m Sisi Nene!</strong><br> I’m a cybersecurity professional currently chasing my dream of becoming an AppSec Engineer and I’m taking you along with me. I’ll be sharing the projects I’m working on, breaking things down in a simple and relatable way, and growing openly in this space. So welcome to my world of learning, and feel free to follow along with <strong>#LearnWithSisiNene</strong>.</p><p>I genuinely can’t wait to connect with everyone who’ll be walking this journey with me. So lets quickly get to it.</p><p>Today, I’ll show you how I manually discovered multiple API endpoints using <strong>Browser Developer Tools</strong> and <strong>Postman</strong> on the <strong>crAPI (Completely Ridiculous API)</strong> vulnerable application. I interacted with its <strong>GET, POST, PUT, and DELETE</strong> endpoints to understand how the API behaves behind the scenes.</p><p>This entire process is called <strong>API Discovery</strong> or <strong>API Reconnaissance</strong>, and it’s always the first step in API penetration testing before checking for vulnerabilities like:</p><ul><li>BOLA</li><li>IDOR</li><li>Weak authentication</li><li>Business logic flaws and so on…</li></ul><p>This report covers exactly what I did, how I did it, and everything I learned along the way.</p><h3>Objective:</h3><p>To document the manual discovery and analysis of API endpoints on the crAPI vulnerable application by:</p><ul><li>Observing live API traffic through browser DevTools</li><li>Reconstructing the captured requests in Postman</li><li>Configuring authentication workflows with JWT</li><li>Understanding how key endpoints function before vulnerability testing</li></ul><h3>Environment Setup and Preparation</h3><p>First things first, I ensured the environment was properly configured before starting API discovery.</p><ul><li>My <strong>Docker</strong> was<strong> </strong>installed and running</li><li>The crAPI environment was deployed using:</li></ul><pre>sudo docker-compose -f docker-compose.yml --compatibility up -d</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I10-JmUlqk2d0kvFRyDWjQ.png" /></figure><ul><li><strong>MailHog</strong> was available for email verification:</li></ul><pre>http://localhost:8025/</pre><ul><li><strong>Postman</strong> was installed for building and testing requests</li></ul><p>I confirmed that all crAPI services were healthy via:</p><pre>sudo docker ps</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Mgp-lzI1O3cvE-aj6j2UQ.png" /></figure><p>Lastly, I opened the crAPI vulnerable application in my browser to ensure it was running correctly before proceeding to API reconnaissance:</p><pre>http://127.0.0.1:8888/</pre><h3>Login Endpoint</h3><p>After launching the app, I created a new user account and logged in. I opened <strong>Firefox DevTools → Network Tab</strong>, refreshed the page, and captured the login request:</p><pre>POST http://localhost:8888/identity/api/auth/login</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HoL-Ax-TqBllZsLkN454jQ.png" /></figure><p>This request contained:</p><ul><li>Email and password in JSON</li><li>POST method</li><li>A response body containing a <strong>JWT token</strong></li></ul><p>This token is extremely important because <strong>every authenticated endpoint depends on it</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*InPW1hGa36tojkTPiuXpcg.png" /></figure><h3>This is what I did in Postman</h3><ol><li>I created a collection called <strong>crAPI Lab</strong></li><li>Added a new request and pasted the endpoint</li><li>Added the JSON body:</li></ol><pre>{&quot;email&quot;:&quot;sisinene@gmail.com&quot;,&quot;password&quot;:&quot;TestUser@10&quot;}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*InPW1hGa36tojkTPiuXpcg.png" /></figure><ul><li>Sent the request</li><li>Received a <strong>200 OK</strong> and a JWT token</li></ul><blockquote><em>You know it’s a JWT because it has three parts separated by dots (</em><em>.): First is the </em><strong><em>header</em></strong><em>, then the </em><strong><em>payload</em></strong><em> and lastly the </em><strong><em>signature</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CmJofQqtqVKkEhrPJhhQAw.png" /></figure><p><strong>Setting Up Automatic Authorization</strong></p><p>To avoid copying the token manually in every request, I created a Postman collection variable:</p><ul><li>Variable name: <strong>accesstoken</strong></li><li>Value: the JWT token from login</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7b7Tli0lDnCBWwX_-_i7ow.png" /></figure><p>In the Authorization type, I chose <strong>Bearer Token </strong>(remember when I got the token in the Login process, below it was the Auth type and it was a <strong>Bearer Token</strong>). Then in the token, I used double curly bracket and typed the Variable name I used to save the token</p><pre>{{accesstoken}}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3p4UgpeC7ev4aXcfm61I-g.png" /></figure><p>From this point forward, Postman automatically injects the token into request headers.</p><blockquote><em>When adding new requests to the collection, always </em><strong><em>save the request first </em></strong><em>before sending it so Postman can apply the token. If not saved first, you will get: </em><strong><em>401 Unauthorized — Invalid Token </em></strong><em>message.</em></blockquote><h3>Dashboard Endpoint</h3><p>The next call I captured was the <strong>dashboard</strong> endpoint:</p><pre>GET http://localhost:8888/identity/api/v2/user/dashboard</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*858LeeEVEYyEp7e-Bbjfig.png" /></figure><p>I created a new http request in Postman and saved it under the <strong>Dashboard</strong> folder. Sending the request with the stored JWT returned Status: <strong>200 OK and User details</strong> in the response body</p><p>This endpoint helped me understand the structure of the user profile and identify values such as:</p><ul><li>userId</li><li>roles</li><li>permissions</li><li>profile metadata</li></ul><p>These information will be VERY important later when I start testing for IDOR/BOLA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iwFhNSlivFJvKvFvOIrKXQ.png" /></figure><h3>Vehicle Endpoint</h3><p>The next call I captured was the <strong>vehicle</strong> endpoint:</p><pre>GET http://localhost:8888/identity/api/v2/vehicle/vehicles</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/1*9e7FfW8Pwo4b2HNk7VbkUw.png" /></figure><p>I created a new http request in Postman and saved it under the <strong>Vehicles</strong> folder. Sending the request with the stored JWT returned Status: <strong>200 OK. </strong>There was nothing much to see on the body. It was empty because I had not added any vehicle to the current user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5QNXyyjxHuLyVZJuWxC9-g.png" /></figure><h3>Product Endpoint</h3><p>The next call I captured was the <strong>product</strong> endpoint:</p><pre>GET http://localhost:8888/workshop/api/shop/products</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*_FjYC-rfR6yUEEIOL4poAA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*SFaik6v2CKHfJUlZbQecSA.png" /></figure><p>I created a new http request in Postman and saved it under the <strong>Vehicles</strong> folder. Sending the request with the stored JWT returned Status: <strong>200 OK and Product listings</strong> in the response body. These are information related to each product with their <strong>id, name, price </strong>and <strong>product image url.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iD3FJnNvdLK7GeMQfR951w.png" /></figure><h3>Order Endpoint</h3><p>Next was the <strong>Order Endpoint </strong>which is a <strong>POST </strong>request. As usual, I copied it and saved in my collection</p><pre>POST http://localhost:8888/workshop/api/shop/orders</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*W-tVGEzeuwyUCR9-GumbIQ.png" /></figure><p>I also copied the product JSON data from the Request payload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*1CPchityFC0TIg0nNePvhQ.png" /></figure><p>Initially, I got: <strong>400 Bad Request. </strong>The API expected:</p><ul><li>product_id</li><li>quantity</li></ul><p>I copied the original JSON payload directly from Firefox DevTools and pasted it into Postman.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*NVmr02dFuUQmQ_0dwR3iiw.png" /></figure><p>After resending, I got <strong>200 OK “Order sent successfully.”</strong> response, meaning the process was successful. My credit balance also reduced to 80 from 100.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqsrkOes1pN2JoLiVIw-Dw.png" /></figure><h3>Return-order Endpoint</h3><p>After placing the order, I returned the product and also captured the process with my firefox developer tool. It was a <strong>POST </strong>request. I copied the endpoint and saved in my collection. I could also see that my <strong>order_id</strong> was<strong> 7</strong></p><pre>POST http://localhost:8888/workshop/api/shop/orders/return_order?order_id=7</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J7T4HgSJ-6D4SEkhrMHPZQ.png" /></figure><p>I sent the request and the response was status <strong>400 Bad Request </strong>and the body of the response also showed “This order is already requested for returning”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l2trQ-GyBU65ACXWMpM7Iw.png" /></figure><blockquote><strong><em>I spent some time in this endpoint trying to figure out why the process was not successful but the issues persisted, and I have no idea why. Please let me know how you did it if you get it right</em></strong></blockquote><h3>Change Email Endpoint</h3><p>In the profile page, there was a feature to change email, so I typed a new email id:</p><pre>sisinene10@gmail.com</pre><p>After changing the email, a token was sent to my email. I will show you how I accessed my email to get the token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8RpDb0q2vr5wkIf_TW-0w.png" /></figure><p>I identified and captured the change-email API request directly from Firefox Developer Tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nlluoa6swQ-7FHaVmUzELQ.png" /></figure><p>I also copied the request payload in JSON format to reproduce the request on Postman. This was to to observe the flow of verification tokens</p><pre>{&quot;old_email&quot;:sisinene@gmail.com&quot;,&quot;new_email&quot;:&quot;sisinene10@gmail.com&quot;}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MYhaQieBpIKHXf04D1OnlA.png" /></figure><p>For the change-email option, I created a new HTTP request on my collection, pasted the API endpoint, a <strong>POST</strong> request and the request payload:</p><pre>POST http://localhost:8888/identity/api/v2/user/change-email</pre><p>I received a status 200 OK after submitting the request, signifying that the procedure was successful. There was an interesting message in the response’s body. It indicated that I should use the MailHog web portal to get the token that was delivered to my email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jMoauClGNizeNwCBufOvow.png" /></figure><p>I accessed the MailHog portal through my <a href="http://localhost/">localhost</a> in port 8025</p><pre>http://127.0.0.1:8025</pre><p>I copied the token after seeing it in the updated email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4GxYqN37JlukF5cRqZIuZQ.png" /></figure><p>I successfully changed the email after inserting the new token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bakhGisKeznSH4Xo8LyvJg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i7f-0irvAb5EhqJRTZfT8Q.png" /></figure><h3>Conclusion</h3><p>So in conclusion I was able to successfully complete the first phase of API pentesting on crAPI vulnerable app and these are what I achieved:</p><ul><li>Deploying the crAPI vulnerable environment</li><li>Capturing real-time API calls using browser DevTools</li><li>Reconstructing these endpoints in Postman</li><li>Setting up a reusable authorization system using collection variables</li><li>Analyzing endpoints such as login, user dashboard, orders, products, and email verification</li><li>Understanding the response structures of each endpoint</li></ul><p>In the next phase, I will assess each endpoint for vulnerabilities such as BOLA, IDOR, authentication weaknesses, business logic flaws and so on.</p><p><strong>Please feel free to ask questions or share any comments that can help me learn from you as well.</strong></p><p>#crAPI #APISecurity #WomenInCyber #Cybersecurity #APIPentesting</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4335a44b18bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>