API-rest
The Gosocket API is a set of functions and procedures that allow external applications to interact with Gosocket's products.
According to the method of authentication used, the API URL is managed:
API with Basic Auth authentication:
- In Sandbox environment: https://developers-sbx.gosocket.net/api/v1/
- In Production environment: https://developers.gosocket.net/api/v1/
API with oAuth 2.0 authentication:
- In Sandbox environment: https://developers-sbx.gosocket.net/api/v2/
- In Production environment: https://developers.gosocket.net/api/v2/
Introduction
The Gosocket REST API is a set of functions and procedures that allow external applications to securely interact with Gosocket's products. It uses HTTP/HTTPS security transfer protocols that protect the integrity and confidentiality of user data between its issuing point and Gosocket, ensuring security and reliability in the point-to-point transmission of documents under a REST API architecture.
Definition, Benefits, and Functions.
Definition
The Gosocket API allows the exchange of DTES according to the Local Schema. In the communication process, the client initiates a request, for this the server and the web client communicate in an information exchange format that can be Json or another language like XML. This development based on REST API allows us to deliver an Online service that offers a DTE Management web and validation of the corresponding electronic tax entity.
Benefits
- Client/server separation: As they are independent systems, they can be managed as autonomous projects, autonomous teams.
- Reliability, scalability, flexibility: Using components with Microsoft Azure helps applications perform optimally when demand changes, in addition to the availability and security provided by Microsoft.
- User experience: A website based on API can perform better than a traditional one. When a request is made to the server, what is obtained in response is plain data, which requires shorter transfer times than if that same data were received mixed with the HTML/CSS of the presentation. With this whole process, we can achieve web applications that resemble desktop applications, making Requests and returns more user-friendly.
Functional scopes
According to the operation model, it has the following functional scopes based on the schemes defined by the local tax entity: • Integration model by consumption methods. • Generation and signing of the tax XML. • Load the digital certificate for the signing of the tax document. • Dispatch/send the XML to the tax entity and obtain the acceptance or rejection of the document by the tax entity.