-
Notifications
You must be signed in to change notification settings - Fork 1
API Development and Utilization
API, or Application Programming Interface, is like a bridge that lets different pieces of software talk to each other. It's a collection of rules and tools that developers use to build software applications. Think of it as a menu in a restaurant. The menu provides a list of dishes you can order, along with a description of each dish. When you specify which dish you want, the kitchen (the system) prepares the meal and serves it. In the same way, an API tells software components how they can interact. So, when a developer wants to add a specific feature to an app, they can use an API to communicate with another service without needing to know how that service is implemented. This makes it easier to develop and integrate software, allowing different applications to work together smoothly.
To understand how APIs work, let's look at how online payments are made. For example, when you're buying something online and choose to pay with PayPal or another payment service, this process uses APIs to make everything work smoothly.
Here's what happens: When you click to pay, the website uses an API to send a message asking for your payment information. This message is sent to the payment service's server through the internet, using a special web address (called a URI) and includes details like what is being asked for and any additional necessary info.
Once the payment service gets this message, it checks everything and processes your payment. Then, it sends back a message to the website saying everything is good to go.
The website gets this response and completes your purchase. All this back-and-forth communication between the website and the payment service happens behind the scenes, thanks to the API. You, as the user, don't see any of this happening; you just see that your payment went through without a hitch.
APIs, especially web APIs, are tools that let applications share data and functionalities over the internet. Here are four common kinds of web APIs:
-
Open APIs: These are available to anyone who wants to use them, kind of like a public library. You just need to know the web address (API endpoint) and how to ask for what you want (request and response formats). They're also known as public APIs.
-
Partner APIs: These are more like private clubs. Businesses give access to these APIs to chosen partners. While the access might still happen over the web, there's a bit of a process to get in, including signing up, getting approved, and receiving special login details.
-
Internal APIs: Think of these as inside-the-company tools. They're not meant for outsiders but help different teams within the same company talk to each other's software, making work more efficient.
-
Composite APIs: These are like multitaskers. In a single request, they let you tap into several other APIs. This is handy in complex software environments, where getting a job done might mean gathering info from many sources at once.
🏠Home
- First Customer Milestone Report
- RAM
- Requirements
- Mockups
- Sequence Diagrams
- Scenarios
- Use Case Diagram
- Class Diagram
- Milestone1 Presentation Scenarios
- Meeting Notes 7 - Nov 12
- Meeting Notes 6 - Nov 5
- Optional Meeting Notes 1 ‐ Oct 21
- Meeting Notes 5 - Oct 15
- Meeting Notes 4 - Oct 8
- Meeting Notes 3 - Oct 3
- Meeting Notes 2 - Oct 1
- Meeting Notes 1 - Sep 24
- Deniz Ulaş Poyraz
- Eren Donmez
- Ersel Çanakçılı
- Oğuz Kağnıcı
- Onur Çerli
- Yekta Ercul
- Ali Alperen Sönmez
- Huseyin Turker Erdem
- Mehmet Tuluyhan Sozen
352 Material
- Final Milestone Report
- Milestone 2 Report
- RAM
- Use Case Diagram
- Sequence Diagrams
- Class Diagrams
- Requirements
- Elicitation Questions
- Mockups
- Scenarios
- Milestone 1 Report
- Our Favourite Repositories
- Linked Data and SPARQL
- Web Application Development
- API Development and Utilization
- Wikidata and Wikidata API
- Mobile Application Development
- Android Studio
- Git
- Meeting Notes 10 ‐ May 10th
- Meeting Notes 9 ‐ Apr 25th
- Meeting Notes 8 ‐ Apr 21st
- Meeting Notes 7 ‐ Apr 12th
- Meeting Notes 6 ‐ Mar 14th
- Meeting Notes 5 ‐ Mar 11th
- Meeting Notes 4 - Mar 7th
- Meeting Notes 3 - Mar 3rd
- Meeting Notes 2 - Feb 22nd
- Meeting Notes 1 - Feb 18th