README.md

💥 A-P-I-V-E-R-S-E : 𝐂𝐨𝐥𝐥𝐞𝐜𝐭𝐢𝐨𝐧 𝐨𝐟 𝐀𝐏𝐈𝐬 !! 🤝

APIVerse is a collection of APIs that are useful for developers. It simplifies the process of both adding new APIs and learning how to harness the power of existing ones. Whether you're a developer looking to expand your toolbox or a newcomer eager to dive into the API ecosystem, APIVerse empowers you to seamlessly learn about API!😃

🌟 Stars	🍴 Forks	🐛 Issues	🔔 Open PRs	🔕 Close PRs

 Tech Stacks!

New API v/s Existing API

📌New API is the one where all the endpoints are defined by you and there is no integration of any API that's already existing.

📌Existing API means that there is an API that is already existing, you are just fetching data and displaying it from external source.

🚀When you can expect your PR will get accepted?

✅ You should add either 1 new API or 1 existing APIafter testing the code properly. The file structure should be followed. README.md file should be present inside your folder.
✅If you are contributing towards enhancement of any API, you need to make sure that you are enhancing atleast 2 APIs.
✅If you are contributing towards any documentation related bug, you should solve atleast 5 documentation bugs to get your PR merged.

Note : For existing API, You should submit the corresponding html and css files also so that we can better visualise how this API can be used within projects. Only submitting JS files won't work.

Here you go🚀, Looking towards great contributions from your side!🔥

Happy Coding!❤️

✨ How to contribute?

• Go through project README.md and CONTRIBUTING GUIDELINES to know about project and related guidelines.
• Go through project to know what you can contribute towards it.

• CREATING ISSUE!

  • Under issues section, you can select proper template, and fill all the necessary details. YOU ARE NOT SUPPOSED TO ALTER THE PROJECT TITLE. ISSUE TITLE SHOULD BE MENTIONED AFTER [].

    You can go through the issues mentioned here before creating any issue to know how the issue is supposed to be created : Issue 1 , Issue 2 , Issue 3, Issue 4

  • You have to wait till the issue is assigned to you. After the issue is assigned, you can start working on the issue.

• ADDING YOUR CODE!

  • You need to fork the repository to work on the project.
  • After forking into your account, you need to clone it using git clone "repo_link"
  • After cloning the repository, you need to create a new branch git checkout -b <BRANCH_NAME>
  • Add the code that you want to contribute from your side under newly created branch.
  • Make sure you follow proper file structure. If you are creating a new api, then you should add your folder(NAMEOFAPI) into the New_APIs folder. If you are adding any existing api, make sure proper file structure is followed and you have added README.md files for the APIs you are adding.

• BRINGING YOUR CODE ON GITHUB!

  • git add . to stage your changes.
  • Use git commit -m "message" to commit the changes. Make sure you are on the branch you have created.
  • Push your changes into github using git push origin <BRANCH_NAME>.
  • Once you are done pushing, create a PR and you are done!😎💗🎯

Our Contributors ❤️

Thank you for contributing to our repository.😃

Show some ❤️ by starring this awesome repository!