Docs Menu
- Introduction to Syncloop
- Quick Start Syncloop
-
API Developer Guide
-
middleware
-
pub
- adapter
- authorization
- client
- collection
- date
- docList
- file
- graphQL
- io
- json
- jwt
- math
- platform
- security
- server
- service
- specs
- sql
- string
- bytesToHexString
- bytesToString
- compare
- compareStrings
- concat
- decodeBase64
- decodeHTML
- encodeBase64
- encodeHTML
- equals
- equalsIgnoreCase
- escapeSQL
- fromXML
- htmlDecode
- htmlEncode
- indexOf
- isAlphanumeric
- isBlank
- isDate
- isEmpty
- isNumber
- length
- lookupDict
- maskString
- messageDigest
- messageFormat
- NullOrWhiteSpc
- objectToString
- padLeft
- replace
- rightPad
- stringConcat
- stringIndexOf
- stringToBytes
- subString
- TextArrayToTextString
- TextListCollector
- tokenize
- toLower
- toString
- toUpper
- trim
- urlDecode
- tenant
- util
- xml
-
pub
-
middleware
- User Guide
- FAQs
- Java Docs
- Blogs
FAQs / Basic API Information
Basic API Information
An API (Application Programming Interface) is a middleware software that enables two applications to communicate with each other. It contains several subroutine definitions, logs, and tools for creating efficient application software.
A Web service uses only three styles of use: SOAP, REST, and XML-RPC for communication whereas API may be exposed in multiple ways.
APIs have a certain limit that is set up by the provider.
1. HTTP for client-server communication
2. Stateless communication
3. XML/JSON as a formatting language
4. Simple URI as the address for the services
2. Stateless communication
3. XML/JSON as a formatting language
4. Simple URI as the address for the services
Web API can be consumed by any client which supports HTTP. These Web APIs do not require any sort of configuration as they are easily used by the client for their applications.
API testing is a kind of software testing that determines if the developed APIs meet expectations regarding the functionality, reliability, performance, and security of the application. ekaAPI testing can also be carried out by Postman API Testing Software.
1. Missing or duplicate functionality
2. Fails to handle error conditions gracefully
3. Stress
4. Reliability
5. Security
6. Unused flags
7. Not implemented errors
8. Inconsistent error handling
9. Performance
10. Multi-threading issues
11. Improper errors
2. Fails to handle error conditions gracefully
3. Stress
4. Reliability
5. Security
6. Unused flags
7. Not implemented errors
8. Inconsistent error handling
9. Performance
10. Multi-threading issues
11. Improper errors
REST (Representational State Transfer) is an architectural style for developing web services. It revolves around resources where every component is a resource that can be accessed through a shared interface using standard HTTP methods.
SOAP (Simple Object Access Protocol) – an XML-based method to expose web services.Web services developed in the REST style are referred to as RESTful web services. These web services use HTTP methods to implement the concept of REST architecture. A RESTful web service usually defines a URI, Uniform Resource Identifier a service, and provides resource representation like JSON and a set of HTTP methods.
REST architecture treats any content as a resource, which can be text files, HTML pages, images, videos, or dynamic business information.
REST uses different representations to define a resource like text, JSON, and XML. XML and JSON are the most popular representations of resources.
RESTful web services use the HTTP protocol as a medium of communication between the client and the server.