Unlike SOAP-based web services, there is no "official" standard for RESTful web APIs. This is because REST is an architectural style, while SOAP is a protocol. Even though REST is not a standard per se, most RESTful implementations make use of standards such as HTTP, URI, JSON, and XML.
How to connect and use
Register with VerifyID and we will give you the intergration documentation with example intergration code, we will also help you intergrate with the help of one of our expert system administrators. Once intergrated your system will communicate with ours and ID Verifications will be seamlessly passed between our respective servers over a secure 256bit encryted https layer of secure communication. Once registered you will also be able to use our awesome reporting system to check the transaction you have done and also get all the information you will need to intergrate our API into any system you may have.
- South African Drivers License Decoder and ID Number Verification
- South African ID Number Verification
- South African ID Number Profile and Deceased Status plus Verification (2 week database)
- Real time Home Affairs ID Verification with deceased Status
- Tracing reports (Last Know Addreses and Telephones plus ID Verifications)
- Contact Enquiries (Last Know Names, Surname and ID Number from provided Cell/Telephone Number)
- Marital Status Verification (Marital status of a person and the spouse they are married to)
- Bank Account Verification (Bank Account Verification)
- CIPC - Companies and Intellectual Property Commission
About REST (REpresentational State Transfer)
We designed the VerifyID API in a very RESTful way, so that your consumption of it is simple and straightforward. From Wikipedia
REST's proponents argue that the Web's scalability and growth are a direct result of a few key design principles:
- Application state and functionality are divided into resources
- Every resource is uniquely addressable using a universal syntax for use in hypermedia links
- All resources share a uniform interface for the transfer of state between client and resource, consisting of
- A constrained set of well-defined operations
- A constrained set of content types, optionally supporting code on demand
- A protocol which is:
REST's client/server separation of concerns simplifies component implementation, reduces the complexity of connector semantics, improves the effectiveness of performance tuning, and increases the scalability of pure server components. Layered system constraints allow intermediaries-proxies, gateways, and firewalls-to be introduced at various points in the communication without changing the interfaces between components, thus allowing them to assist in communication translation or improve performance via large-scale, shared caching.
REST enables intermediate processing by constraining messages to be self-descriptive: interaction is stateless between requests, standard methods and media types are used to indicate semantics and exchange information, and responses explicitly indicate cacheability.
If you're looking for more information about RESTful web services, the O'Reilly RESTful Web Services book.