Skip to main content
WeCareRemote uses JSON Web Tokens (JWTs) to authenticate API requests. A JWT is a compact, self-contained token that encodes your user identity and permissions. Every time you call a protected endpoint — such as the AI assistant API — you include this token in your request header so WeCareRemote can verify who you are without requiring you to log in again. A JWT has three parts joined by dots: header.payload.signature. The header describes the signing algorithm, the payload contains your identity and permissions, and the signature proves the token was issued by WeCareRemote and has not been altered. You do not need to construct tokens yourself — WeCareRemote issues them for you at login.

​
Obtaining a token

Your JWT token is issued automatically when you log in through the WeCareRemote platform.
1

Log in to WeCareRemote

Sign in at wcr.is/home using your email and password.
2

Receive your token

On successful login, WeCareRemote issues a JWT token. The token encodes your user identity, role, and permissions.
3

Copy your token

Retrieve your token from the login response to use in API requests. You can also request it directly from the token endpoint shown below.

​
Using your token in API requests

To fetch your JWT token directly, call the token endpoint: 
GET /api/v1/wordpress_auth/jwt_token
Host: getme.global
The response returns your token: 
{
  "success": true,
  "jwt_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}
Pass the token in the Authorization header on every API request: 
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
The AI assistant API also uses Bearer token authentication. Use the same JWT token in the Authorization header when calling the AI assistant endpoints.

​
Verifying your token

You can verify that your token is valid at any time by calling the verification endpoint. Endpoint: POST https://getme.global/api/v1/wordpress_auth/verify_jwt_token Request body: 
{
  "token": "<your-jwt>"
}
Successful response: A valid token returns your full user profile: 
{
  "success": true,
  "user": {
    "id": 42,
    "username": "jane.doe",
    "name": "Jane Doe",
    "email": "jane@example.org",
    "permissions": ["org_admin"],
    "organization": {
      "name": "Helping Hands NGO"
    }
  }
}
The permissions array contains your assigned role — either ["blog"] for refugee users or ["org_admin"] for NGO administrators. See user roles for details on what each role can access.

​
Token expiry and errors

JWT tokens expire after a set period. If your token has expired, API requests will return a 401 Unauthorized error. Log in again at wcr.is/home to receive a new token.
Common authentication errors:
StatusMeaning
401 UnauthorizedYour token is missing, malformed, or expired. Re-authenticate to get a fresh token.
403 ForbiddenYour token is valid but your role does not have permission to access the requested resource.