APIs & Use Case
Let's understand APIs with different scenarios, below are the sequence of scenarios:-
    1.
    User (GET)
    2.
    Asset (PUT)
• User(GET): You can fetch the user details with this API. UID is a unique key identifier in response this user UID helps to get spaces and makes other rest calls.
Request
Response
    Resource Path: user
    HTTP Method: GET
    Endpoint URL: https://xxx.gitbook.com/v1/user
🔰
200: OK
1
{
2
"root": {
3
"baseDomain": "aatrey882",
4
"kind": "user",
5
"title": "AashishAtrey",
6
"uid": "edvwqJPyf5bKsCuz8Kqm4m8CZ1l2"
7
}
8
}
Copied!
    Asset(PUT) Insert new assets in space.
Request
Response
    Resource Path:spaces/:spaceID/content/assets
    HTTP Method: PUT
    Endpoint URL:https://xxx.gitbook.com/v1/spaces/:spaceID/content/assets
    Path Parameters: :spaceID
To pass an attachment you need to convert file into base64 and then pass over HTTPS.
Request Body
🔰
200: OK
Returns the ID of the updated revision.
1
{"revision":"-MTMi9MgKuxSwZCV0bbH"}
Copied!
I have covered 2 cases only there but you can fork myGitHubrepository there you will find all scenarios that got integrated with ServiceNow.
Conclusion:- Overall GitBook is very cool but I feel that it lags some features
    1.
    Themes customization should be available.
    2.
    Compatible with .xlsx, .ppt, etc extensions as well.
    3.
    Assets should get included on the page as of now it's in revision mode only.
Pros:
    Custom Domain
    Easy to configure APIs
Last modified 8mo ago
Copy link