Generic documentation

Introduction

What is?

Helper is an application that is used for helping people find any services around them in a very quick time.

<aside> 📱 Usage:

</aside>

How it works?

Project structure

<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/0d31710f-bada-4d1d-b505-aaf6043da188/web-size_1073465.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/0d31710f-bada-4d1d-b505-aaf6043da188/web-size_1073465.png" width="40px" /> Backend Server side structure made of by using SpringBoot KT

</aside>

<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/8ace4e49-9641-431a-9cf1-6d7680f2da66/webpage_14380808.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/8ace4e49-9641-431a-9cf1-6d7680f2da66/webpage_14380808.png" width="40px" /> Frontend Front-end mobile made of by using Kotlin Multiplatform (ComposeUI framework)

</aside>

<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/afbc9989-d0f7-4418-9c04-dd52590dff40/interface_14549281.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/afbc9989-d0f7-4418-9c04-dd52590dff40/interface_14549281.png" width="40px" /> Database User Data - Posts Data on PostgresSQL Secondary features on MongoDB

</aside>

<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/4bff24a9-4f8d-4b3a-ac30-7b6b9d9d8ade/devops.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/97b6bdcb-5e88-4b2d-bc5b-aba94d4f08be/4bff24a9-4f8d-4b3a-ac30-7b6b9d9d8ade/devops.png" width="40px" /> DevOps integration CI/CD Ratchet Strategy

</aside>

System design

Opera_senza_titolo.png

Conventions

The base URL to send all API requests is https://api.devmate.app HTTPS is required for all API requests.

The Devmate API follows RESTful conventions when possible, with most operations performed via GETPOSTPATCH, and DELETE requests on page and database resources. Request and response bodies are encoded as JSON.

JSON CONVENTIONS

Pagination

Endpoints that return lists of objects support cursor-based pagination requests. By default, Devmate returns ten items per API call. If the number of items in a response from a support endpoint exceeds the default, then an integration can use pagination to request a specific set of the results and/or to limit the number of returned items.

SUPPORTED ENDPOINTS

HTTP method Endpoint
GET List all users
GET Retrieve a post
GET Retrieve a comment
POST Query a database
POST Insert a post

RESPONSES

Field Type Description
has_more boolean Whether the response includes the end of the list. false if there are no more results. Otherwise, true.
object "list" The constant string "list".
results array of objects The list, or partial list, of endpoint-specific results.

Status Codes

HTTP response codes are used to indicate general classes of success and error.

Success Code

HTTP Status Quote Description response
200 Successfully processed request.
Successfully logged in. Data of login access
Successfully registered. Data of registration user
Successfully inserted post.

Error Codes

Error responses contain more detail about the error in the response body, in the "code" and "message"properties.

HTTP Status Quote code message
400 invalid_json The request body could not be decoded as JSON
invalid_request_url This request URL is not valid.
invalid_request This request is not supported.
401 unauthorized The bearer token is not valid.

Versioning

Our API versions are named for the date the version is released.

You set the version by including a Devmate-Version header. Setting the Devmate-Version header in required.

curl <https://api.devmate.app/v1/users/01da9b00-e400-4959-91ce-af55307647e5> \\
  -H "Authorization: Bearer secret_t1CdN9S8yicG5eWLUOfhcWaOscVnFXns"
  -H "Notion-Version: 2025-05-15"

Objects

Users

Where user objects appear in the API

User objects appear in the API in nearly all objects returned by the API, including:

User objects will always contain object and id keys, as described below. The remaining properties may appear if the user is being rendered in a rich text or page property context, and the bot has the correct capabilities to access those properties. For more about capabilities, see the Capabilities guide and the Authorization guide.

All users

These fields are shared by all users, including people and bots. Fields marked with * are always present.

Property Updatable Type Description Example value
object* Display-only "user" Always "user" "user"
id* Display-only string(UUID) Unique identifier for this user. "e79a0b74-3aba-4149-9f74-0bb5791a6ee6"
type Display-only string(optional, enum) Type of the user. Possible values are "person" and "bot". "person"
name Display-only string(optional) User's name, as displayed in Notion. "Avocado Lovelace"
avatar_url Display-only string(optional) Chosen avatar image. "<https://secure.notion-static.com/e6a352a8-8381-44d0-a1dc-9ed80e62b53d.jpg>"

File

File objects contain data about a file that is uploaded to Notion, or data about an external file that is linked to in Notion.

{
  "type": "file",
  "file": {
    "url": "<https://s3.us-west-2.amazonaws.com/secure.notion-static.com/7b8b0713-dbd4-4962-b38b-955b6c49a573/My_test_image.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAT73L2G45EIPT3X45%2F20221024%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20221024T205211Z&X-Amz-Expires=3600&X-Amz-Signature=208aa971577ff05e75e68354e8a9488697288ff3fb3879c2d599433a7625bf90&X-Amz-SignedHeaders=host&x-id=GetObject>",
    "expiry_time": "2022-10-24T22:49:22.765Z"
  }
}

Page, embed, image, video, file, pdf, and bookmark block types all contain file objects. Icon and cover page object values also contain file objects.

Each file object includes the following fields:

| --- | --- | --- | --- |

Endpoints

Endpoints (1)

Contact us

Email

[email protected] - professional email

Github

https://github.com/Giacomop19 - projects

Linkedin

https://www.linkedin.com/in/giacomo-pumapillo/ - resume