Owners, editors and members #
A person signs in at https://app.memelemur.com/jungle-gym and is known by their email. Emails are compared without regard to capitals. A person is in a team with one of three roles: member, editor or owner.
| Member | Editor | Owner | |
|---|---|---|---|
| Make memes, upload templates, use the library, vote, view usage and credits | Yes | Yes | Yes |
| Change settings (tone, off-limits topics, watermark and the rest) | No | Yes | Yes |
| Create, edit and delete spaces | No | Yes | Yes |
| Delete a template | No | Yes | Yes |
| Create, list and revoke regular API keys | No | Yes | Yes |
| Create, list and revoke admin API keys | No | No | Yes |
| The team's own model key (store, delete) | No | No | Yes |
| Invite, remove, or change the role of people | No | No | Yes |
Every role can read the settings, the spaces and whether a model key is stored. Only an owner can list the people and the invitations.
An editor works with regular API keys only. The list of keys an editor gets leaves the admin keys out, and an editor cannot make or revoke one.
A call a person's role does not allow returns 403, and the message says which role the route needs: this route needs the editor role or this route needs the owner role.
Roles are for people who sign in. A call made with an API key is allowed or refused by the kind of the key, which API keys covers.
The invitation and member routes need an owner or an admin API key, which is the key their examples send. With a regular key they return 403 with this route needs an admin API key.
A team with people in it always has an owner. The only owner cannot be removed or given another role while the team has other people.
A person becomes a member through an invitation to their email address. The operator, who is whoever runs Meme Lemur for you, can also add someone. Nothing else lets a person in: an address at your company's domain that nobody invited has no access.
Invite someone #
POST /v1/invitations
The person gets an email from Meme Lemur that says who invited them and to which team, with a button to accept. They sign in with the invited address, and that makes them a member.
| Field | Type | What it does |
|---|---|---|
email |
an email address | Who to invite. Required. |
role |
owner, editor or member |
The role they get. The default is member. |
curl https://api.memelemur.com/v1/invitations \
-H "Authorization: Bearer $MEMELEMUR_ADMIN_KEY" \
-H "Content-Type: application/json" \
-d '{"email": "sam@acme.com", "role": "member"}'The response is 201:
{
"invitation": {
"id": "inv_wkg4i1tm2a8np6v3",
"email": "sam@acme.com",
"role": "member",
"invitedBy": null,
"createdAt": "2026-10-02T00:58:17.721Z",
"expiresAt": "2026-10-09T00:58:17.721Z",
"expired": false,
"emailedAt": "2026-10-02T00:58:18.102Z",
"link": "https://app.memelemur.com/jungle-gym?team=tnt_hc0n3r4w54a35prf&invitation=inv_wkg4i1tm2a8np6v3"
},
"email": { "sent": true }
}| Field | What it is |
|---|---|
invitedBy |
The email of the owner who invited, and null when an API key did. The email says this person invited them, and a reply to it goes to this person. |
emailedAt |
When the last email for the invitation was sent. Null when none was. |
link |
Where the button in the email goes. |
email.sent |
Whether this call sent the email. |
email.reason |
Why it did not, when sent is false. |
The invitation is made whether or not the email goes out. When email.sent is false, pass link on to the person yourself.
An invitation lasts 7 days and works once. Inviting the same email again replaces the earlier invitation.
It returns 409 when the email is already a member. Change a member's role with the members route.
What the link lets a person do #
The link has the ids of your team and of the invitation in it, and nothing secret. Opening it asks the person to sign in, which proves their address with a code sent to it. Only the invited address becomes a member.
Someone else who gets the link, say because the email was forwarded, can sign in with their own address and is then told the invitation was sent to a different one. They do not join, and they do not learn which address or which team it was for. The invitation stays open for the person it was sent to.
After the invited person has joined, or the invitation has expired or been revoked, the link lets nobody in.
Limits on the emails #
The limits count the invitation emails sent in the last 24 hours.
| Limit | Emails |
|---|---|
| To one address, from every team together | 3 |
| By one person who invites | 20 |
| By one team | 50 |
Past a limit the invitation is still made, email.sent is false and email.reason says which limit it was.
List the invitations #
GET /v1/invitations
Returns the invitations nobody has taken up yet, newest first, expired ones included. An expired one makes nobody a member until you send it again.
curl https://api.memelemur.com/v1/invitations \
-H "Authorization: Bearer $MEMELEMUR_ADMIN_KEY"{
"invitations": [
{
"id": "inv_wkg4i1tm2a8np6v3",
"email": "sam@acme.com",
"role": "member",
"invitedBy": null,
"createdAt": "2026-10-02T00:58:17.721Z",
"expiresAt": "2026-10-09T00:58:17.721Z",
"expired": false,
"emailedAt": "2026-10-02T00:58:18.102Z",
"link": "https://app.memelemur.com/jungle-gym?team=tnt_hc0n3r4w54a35prf&invitation=inv_wkg4i1tm2a8np6v3"
}
]
}Send an invitation again #
POST /v1/invitations/:id/resend
Sends the email again and gives the invitation another 7 days, whether or not it had expired. The link stays the same.
curl -X POST https://api.memelemur.com/v1/invitations/inv_wkg4i1tm2a8np6v3/resend \
-H "Authorization: Bearer $MEMELEMUR_ADMIN_KEY"The response is the same as for inviting:
{
"invitation": {
"id": "inv_wkg4i1tm2a8np6v3",
"email": "sam@acme.com",
"role": "member",
"invitedBy": null,
"createdAt": "2026-10-02T00:58:17.721Z",
"expiresAt": "2026-10-11T09:14:02.337Z",
"expired": false,
"emailedAt": "2026-10-04T09:14:02.611Z",
"link": "https://app.memelemur.com/jungle-gym?team=tnt_hc0n3r4w54a35prf&invitation=inv_wkg4i1tm2a8np6v3"
},
"email": { "sent": true }
}It returns 404 when your team has no invitation with that id. One address gets 3 invitation emails a day at most. A call past that returns 200 with "sent": false, and still gives the invitation another 7 days.
Revoke an invitation #
DELETE /v1/invitations/:id
Returns 204 with no body, and 404 when your team has no invitation with that id. The link in an email already sent stops working.
curl -X DELETE https://api.memelemur.com/v1/invitations/inv_wkg4i1tm2a8np6v3 \
-H "Authorization: Bearer $MEMELEMUR_ADMIN_KEY"List the members #
GET /v1/members
Returns the team's members in order of email.
curl https://api.memelemur.com/v1/members \
-H "Authorization: Bearer $MEMELEMUR_ADMIN_KEY"{
"members": [
{ "email": "dana@acme.com", "role": "owner", "joinedThrough": "invitation", "addedBy": null, "createdAt": "2026-10-02T01:13:55.284Z" },
{ "email": "sam@acme.com", "role": "member", "joinedThrough": "invitation", "addedBy": "dana@acme.com", "createdAt": "2026-10-03T09:20:11.530Z" }
]
}| Field | What it is |
|---|---|
joinedThrough |
How the person became a member: invitation or operator. A person who joined before October 2026 can have domain, from when a team could take in a whole email domain. |
addedBy |
The email of who invited or added them. Null when a key was used. |
Change a member's role #
PATCH /v1/members/:email
| Field | Type | What it does |
|---|---|---|
role |
owner, editor or member |
The member's new role. Required. |
curl -X PATCH https://api.memelemur.com/v1/members/dana@acme.com \
-H "Authorization: Bearer $MEMELEMUR_ADMIN_KEY" \
-H "Content-Type: application/json" \
-d '{"role": "owner"}'{
"member": { "email": "dana@acme.com", "role": "owner", "joinedThrough": "invitation", "addedBy": null, "createdAt": "2026-10-02T01:13:55.284Z" }
}Errors #
| Status | When |
|---|---|
| 400 | role is not owner, editor or member, or the path is not an email address. |
| 403 | The call was made by a signed-in member or editor, or with a regular API key. An owner or an admin key can change a role. |
| 404 | The team has no member with that email. |
| 409 | The change would leave a team that has members with no owner. Make another member an owner first. |
Remove a member #
DELETE /v1/members/:email
Returns 204 with no body. The person can no longer use the team from their next request.
curl -X DELETE https://api.memelemur.com/v1/members/sam@acme.com \
-H "Authorization: Bearer $MEMELEMUR_ADMIN_KEY"It returns 404 when the team has no member with that email, and 409 when the person is the only owner and the team has other members. A person you removed stays out until you invite them again.
Who is signed in #
GET /v1/me
This route is for the pages on https://app.memelemur.com. It tells a signed-in person who they are and which teams they may use, and it is where an invitation takes effect.
curl https://api.memelemur.com/v1/me \
-H "Authorization: Bearer $MEMELEMUR_KEY"A call with an API key returns 401, because a key is not a person:
{ "error": "nobody is signed in" }A signed-in person gets:
{
"email": "dana@acme.com",
"operator": false,
"teams": [{ "id": "tnt_hc0n3r4w54a35prf", "name": "acme", "role": "owner" }]
}How a signed-in request is made #
The pages on https://app.memelemur.com call the same /v1 routes these docs describe. A signed-in request sends no Authorization header. It sends Memelemur-Team: <team id> to say which team it is for, even when the person has one team, and it has to come from a page on https://app.memelemur.com. A request a page on another site makes for a signed-in person returns 403.
People are signed in only on https://app.memelemur.com. On https://api.memelemur.com every call needs an API key.