[BUG] API Error: status_code: 401, body: unauthorized

[yoyohoho0221]

Hi there, first of all thanks for checking this issue, I have recently tried to deploy zep community locally, however I have the API Error raised. I have generated the API secret and API key with JWT.

Could anyone help me resolve it? Thanks a lot!

The error is:
Exception has occurred: ApiError
status_code: 401, body: unauthorized
StopIteration: 0

During handling of the above exception, another exception occurred:

json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

File "C:\Users\yaoyao14\Downloads\zep.py", line 29, in
client.memory.add(
zep_python.core.api_error.ApiError: status_code: 401, body: unauthorized

The log of zep shows:
zep-1 | 2025-01-26T03:03:32.767ZINFOHTTP Request Served{"proto": "HTTP/1.1", "method": "POST", "path": "/api/v2/sessions/1db9280c30ca4e938516f21b619a6988/memory", "request_id": "", "duration": "119.237µs", "status": 401, "response_size": 13}

My testing code is very simple.

client = Zep(
api_key=API_KEY,
base_url=BASE_URL,
)

sessionId = uuid.uuid4().hex
client.memory.add(
session_id=sessionId,
messages=[
Message(
content="content",
role_type="norole",
)
],
)

The code to generate secret and API key:
import secrets
import jwt
sec=secrets.token_urlsafe(64)
print(sec)
playload={}
token = jwt.encode(playload, sec, algorithm='HS256')
print(token)

Environment (please complete the following information):

• Zep version: latest
• Zep SDK and version: zep-python latest
• Deployment using docker compose following the online guide.

[jvsteiner]

I managed to get it running - I just manually set the api key in the zep.yaml file, under api_secret:

I am not using https - just running it locally, and I immediately run into other issues for which there is zero documentation or mentions. I don't think this project is currently intended to work - probably its a much earlier version which the team building the cloud service do not have time or resources to maintain - which I totally understand. Unless community folks actively start developing this version, it's probably going to be a while before the Zep team has enough bandwidth to do much here