Add/update users

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://api-reference.lassomoderation.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "Lasso Moderation API MCP server": {
    "url": "https://api-reference.lassomoderation.com/mcp"
  }
}
Close
POST /user

Add or update a user

Headers

application/json

Body

  • user object Required

    Model for a user that you can send to Lasso. If the id of the user does not yet exist a new user will be made.

    Hide user attributes Show user attributes object
    • id string Required
    • name string
    • created_at string(date-time)

      ISO Date e.g. 2022-07-21T18:12:39.000Z https://en.wikipedia.org/wiki/ISO_8601

    • email_domain string

      The email domain of your user. So "user@example.com" would be "example.com"

    • email string
    • phone_number string
    • country_code string

      Two letter code according to the https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 standard

    • ip_address string

      The IP address of the user

    • profile_image_url string
    • signup_method string

      The method the user has used to sign up on your platform. This can be apple, facebook, google, email, password, or unknown.

    • metadata object
    • category_id string

      Set this if the user is only part of a specific category

    • type

      Specify what kind of user this is in your platform. By default this is a "normal" user

      Values are normal, moderator, admin, trusted, or testing. Default value is normal.

    • status string

      The status of an object

      Values are allowed, flagged, or hidden.

    • tags array[string]

      The identifiers of the tags. When tags is set, it will override all currently set tags on the user.

    • published_at string

      (optional) ISO Date e.g. 2022-07-21T18:12:39.000Z https://en.wikipedia.org/wiki/ISO_8601

      This field can be used to let Lasso know this user has not yet been published.

      • If the field is set to null the user is marked as not yet published.
      • If the field is set to a date, we use that date as the published date.
      • If the field is not specified, we assume the created at date as the published date. Note: this field can only be set when creating the user, use the publish endpoint to publish the user.
    • photo_id_urls array[string]

      Photo IDs can be used to recognize this user's face in the content.

Responses

  • 200 application/json

    OK

    Hide response attribute Show response attribute object
    • success boolean
POST /user 
curl \
 --request POST 'https://api.lassomoderation.com/api/v1/user' \
 --header "Content-Type: application/json" \
 --header "Authorization: Bearer lasso.a35afd...a6ea" \
 --data '"{\n  \"user\": {\n    \"id\": \"clczbfbhh0000sa90h45xv3cg\",\n    \"created_at\": \"2022-07-21T18:12:39.000Z\",\n    \"name\": \"John Doe\",\n    \"email_domain\": \"gmail.com\",\n    \"signup_method\": \"google\",\n    \"country_code\": \"US\",\n    \"profile_image_url\": \"https://www.example.com/profile/image.png\",\n    \"tags\": [\n      \"suspicious-user\"\n    ],\n    \"metadata\": {\n      \"tag_line\": \"I am a person of mystery...\",\n      \"connections\": 8\n    }\n  }\n}"'
Request example 
{
  "user": {
    "id": "clczbfbhh0000sa90h45xv3cg",
    "created_at": "2022-07-21T18:12:39.000Z",
    "name": "John Doe",
    "email_domain": "gmail.com",
    "signup_method": "google",
    "country_code": "US",
    "profile_image_url": "https://www.example.com/profile/image.png",
    "tags": [
      "suspicious-user"
    ],
    "metadata": {
      "tag_line": "I am a person of mystery...",
      "connections": 8
    }
  }
}
Response examples (200) 
{
  "success": true
}