An interface testing software that can realize offline sharing of documents on the intranet

Before this, users and friends of Apipost often asked: Why do I not support generating interface documents when I am not logged in or offline?

Now, with the release of Apipost version 6.1.1, this problem no longer exists. Since version 6.1.1, even if you are not logged in or offline; Apipost still supports the rapid generation of API documents and supports sharing with peers Friends of the local area network. Isn't it pretty~

Today, I will introduce the intranet sharing function of Apipost in detail.

01
What is intranet sharing Intranet sharing means that even when there is no Internet or the Internet is disconnected, as long as it is in the same network environment (local area network), Apipost still supports the generation of interface document links that can be accessed by small partners in the same local area network.

02
Apipost supports intranet sharing usage scenarios In version V6.1.1, we have optimized and iterated the intranet document sharing function. Even if you are not logged in (guest mode), you can quickly generate interface documents and share them with friends on the same local area network. to access. The following is a detailed comparison of usage scenarios:

If the computer is connected to the Internet, you can use the intranet sharing and normal sharing functions at the same time, but the links shared by the intranet can only be accessed through the intranet. If you are not logged in, only intranet sharing is currently supported. The normal sharing function requires the login status to be used, and the login requires an Internet connection to use.
In the case of only a local area network, we support intranet sharing, and others can view the documents you share through the local area network address.
At present, there are many tools at home and abroad that support the generation of interface documents, but for this function, Apipost is definitely a unique show, haha~

03
Apipost supports offline and offline sharing of documents

In the process of using the product, you may encounter the situation that the network cannot be connected to the Internet normally due to network fluctuations or other conditions, and some companies can only use the local area network for security reasons or data privacy considerations.

In this case, it may be inconvenient for developers to collaborate using interface debugging tools. For example, after back-end developers have developed interfaces, they may need to add content that conforms to swagger rules in the code, and then generate swagger documents before building services. Time consuming and laborious. A lot of unnecessary work is added in the middle.

Use Apipost intranet to share, one-click sharing, and others can directly access. Just don't be too cool~

Kind tips:
If the shared intranet document cannot be opened by others, you may need to check whether the firewall is turned off

04
Apipost Intranet Sharing Operation Guide When you have successfully debugged an interface and want to share it with partners in the same local area network, you only need to click to share the project/document, click to copy the intranet link, and you can share it with your partners with one click. It is easy to do in two steps. . In addition, partners who have higher requirements for data confidentiality can set the time limit and password for document access at the same time~

05
Appendix 6.1.1 Update List

Added interface documentation to support intranet sharing

Execute script after adding interface to support response.raw.responseText custom response content

Added interface debugging on-site restoration

Optimization of hot update function optimization

Optimize swagger import to support more custom formats

Optimized to limit the maximum length of user nicknames to 64 characters

Optimize interface document export markdown

Optimizing the switching project operation is too fast, causing the problem of directory data freezing

Fixed the issue that some Windows system users would experience a white screen when opening the client

Fixed some directory copy operations failing under certain circumstances

Fix parameter description library management opening and closing checkbox may fail

Fixed the problem that the menu selection state does not switch when jumping from the [Recent] menu interface record to the console

Fixed the problem that the url or parameter input "{" had a white screen after setting global variables using pre-executed scripts in interface debugging

Fix import failure of specific apifox format

Fixed the problem of double lines appearing in the lower border of the input box in the request area table

Fix the problem that the client is stuck when the websocket interface url prefix is input://

Fix parameter description extraction related bugs

Fixed the problem that the system settings certificate could not be deleted and the switch settings could not be saved

Fixed the problem that the CA certificate and client certificate uploaded by the system settings disappeared after restarting the client

Appendix 6.1.2 Update List

The number of new console display records can be set (default 10)

Fix path variable cannot enter parameter value

Fix script setting global variables not showing

Fix Monaco editor loading issue

Fix the interface save confirm close button is invalid in offline state

Fixed the problem that the interface url input ASCII code query is automatically escaped to characters

If you want to know more about product usage related functions, please visit "Visit Official Website"

Official link: Apipost-based on collaboration, not limited to API documentation, debugging, Mock