Connections API

These endpoints are responsible for creating bidirectional edges to connect users, and to fetch all relevant connections for any single user.

POST /interactions

this endpoint is used to create an interaction between two users, resulting in two rows that are bi-directional edges

Request

{
    "eventType": "CONNECTION",
    "eventParam": "SixVansSort"
}

Response

the response is intended for debugging purposes, as it does not hold meaningful information that isn't communicated in the response status

example response

{
    "message": "Connection created with firstname",
    "name": "firstname lastname"
}

GET /interactions/journal

this endpoint is used to fetch all connections for a single user. A connection "journal".

Request

Query Parameters (optional)

You may optionally filter connections by event and/or year using query string parameters.

Example request

GET /interactions/journal

GET /interactions/journal?eventId=blueprint&year=2025

Response

All connections will include the fields in the following response. Note that by default, all connections will be sorted from most to least recent in the response

Example response

{
    "message": "all connections for kevin.xiao27@gmail.com",
    "data": [
        {
            "compositeID": "PROFILE#SillyPandasDeny", // this profileID belongs to the user making the request
            "fname": "firstname",
            "pronouns": "",
            "year": "Not Applicable",
            "createdAt": 1754717442711,
            "connectionID": "SixVansSort",
            "major": "Awesome",
            "lname": "lastname",
            "type": "CONNECTION#SixVansSort" // this profileID belongs to a connection
        }
    ]
}

GET /interactions/journal/{id}

this endpoint is used to check if the authenticated user is connected with a profile of a specific ID

Request

Response The response will return a boolean field, connection. This will indicate if two users are connected. There are some specific behaviours which may also have an additional message field which is typically used for debugging.

Some behaviour to note is that this endpoint will return false if a user checks their own profile, they aren't a member, or the profile requested doesn't exist. Some of this is based on vacuous logic (i.e. if a user isn't a member, by definition they can't be connected), but may need explicit handling in the frontend.

Example Response

{
    "message": "No profile associated with kevin@ubcbiztech.com",
    "connected": false
}

Errors

• 400 means that the user has attempted to check if they have a connection with themselves

GET /interactions/quests 🚧

POST /interactions/search

this endpoint is used to semantically search a user’s connections based on a free-text query.

This endpoint allows an authenticated user to search through their existing connections using natural language. It is typically backed by semantic or embedding-based search, rather than exact keyword matching.

Request

Example request

curl -X POST "https://api-dev.ubcbiztech.com/interactions/search" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <JWT_TOKEN>" \
  -d '{
    "query": "I want to meet Lumeno AI interns"
  }'