It's a collection of multiple types of lists used during security assessments, collected in one place. List types include usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells, and many more.

api-endpoints.txt · This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.

It's a collection of multiple types of lists used during security assessments, collected in one place. List types include usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells, and many more.

It's a collection of multiple types of lists used during security assessments, collected in one place. List types include usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells, and many more.

March 4, 2025 - GitLab Community Edition

endpoints.txt · 24.6 MB · object_names.txt · 4.52 MB · Most likely ports where domains host their API · Possible URL path locations of the API · Custom HTTP request headers seen in other APIs · Path parameters identify a specific resource of the endpoint ·

February 25, 2026 - # Tools https://github.com/Fuzzapi/fuzzapi https://github.com/Fuzzapi/API-fuzzer https://github.com/flipkart-incubator/Astra https://github.com/BBVA/apicheck/ https://github.com/ngalongc/openapi_security_scanner https://github.com/assetnote/kiterunner https://github.com/s0md3v/dump/tree/master/json2paths https://github.com/API-Security/APIKit # API keys guesser https://api-guesser.netlify.app/ # Wordlists https://github.com/chrislockard/api_wordlist https://github.com/danielmiessler/SecLists/blob/master/Discovery/Web-Content/common-api-endpoints-mazen160.txt https://github.com/danielmiessler/S

AIrticle is an innovative web application designed to harness the capabilities of GPT-4 for generating high-quality newsletters based on user-defined topics or prompts. - AIrticle/AIrticle RESTful API Endpoints.txt at main · Feel-The-AGI/AIrticle

with open("something.txt") as f: data = {'file': f.read()}

The txt APIs provide more human readable and script friendly API endpoints for common information requests.

March 1, 2026 - For AI agents: visit https://techdocs.akamai.com/api-definitions/llms.txt for an index of all pages formatted in Markdown and endpoints in OpenAPI. Append .md to any documentation page URL to get its markdown version. Jump to Content · GuideRecipesAPIRelease notesTerraformControl Center ·

December 30, 2023 - Around the third user-agent update, ... this relatively small, mundane task. ... Fetch data from a remote API endpoint that defines known user-agent strings that should be disallowed...

Added bonus of moving ispsystem_billmanager_api.txt from CRLF to LF line endings.

Uitzendinggemist NPO NED1, NED2, NED3. Contribute to Opvolger/plugin.video.uzg development by creating an account on GitHub.

April 15, 2025 - grep -irl "fetch(" js_files/ > fetch_based.txt grep -irl "axios" js_files/ > axios_based.txt grep -irl "token" js_files/ > tokens.txt grep -irl "apiKey" js_files/ > apikeys.txt · Here’s what the average recon guy misses: they look for endpoints, but not how they’re used.

Projeto de calendário utilizando Flask + SQLite para composição de nota na disciplina de modelagem e projeto de sistemas - flask-web-Calendar/API endpoints.txt at main · tmmarquess/flask-web-Calendar

November 14, 2023 - If you are using crAPI and you try to login, the first endpoint that you can see is identity/api/auth/login, this endpoint was called with POST method and we send user/pass as part of the request to the endpoint. If you clicked on every single option, you got different endpoint. It’s must to check the great great resource call robots.txt, sometimes we can found information useful, in this file we can see resource disabled for search engine does not able to track them.

May 17, 2023 - To get a more thorough understanding of the endpoints we are getting back, we can run Feroxbuster one last time using the PUT and DELETE methods (we can include as many methods as we want in the -m tag): feroxbuster -u http://192.168.1.26:8000/api/ -w /usr/share/seclists/Discovery/Web-Content/raft-medium-directories.txt -H 'Authorization: Token eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VybmFtZSI6IlNhbW15IiwiZXhwIjoxNjgzNTgwODE2LCJzdWIiOiJhY2Nlc3MifQ.QCYFvWCrs74U_6bs8SYx6hR5QhjKHkKOwdJh9x8tlIo' -m PUT DELETE

There have been multiple instances where I found “hidden” API endpoints during assessments that weren’t originally provided by the customer. With brute forcing tools like Feroxbuster and FFUF a big part of your success depends on the quality of your wordlists. In this case I always run a common wordlist like “directory-list-2.3-small.txt” or “common.txt” just in case the API endpoints contain commonly found words that aren’t that common with APIs.