Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #3192] [FEAT]: Add additional EMBED API endpoints [WIP] #2054

New Issue
Closed
opened 2026-02-22 18:27:56 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:27:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @jamieede on GitHub (Feb 13, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3192

Originally assigned to: @shatfield4 on GitHub.

Add API endpoints for creating & editing embed configurations

Overview

Currently, embed configurations can only be created through the web interface.

This feature request adds new REST API endpoints /v1/embed/new and `/v1/embed/{id} to allow programmatic creation and editing of embed configurations using API key authentication.

Why?

  • Enables automation of embed creation
  • Enables automation of embed editing
  • Allows integration with external systems and scripts
  • Provides a programmatic alternative to the UI-based workflow

Current Solution

Users must manually create and edit embeds through the web interface at /settings/embed-config

The endpoints will use the existing API key authentication system and follow the same patterns as other API endpoints in the system.

Originally created by @jamieede on GitHub (Feb 13, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3192 Originally assigned to: @shatfield4 on GitHub. # Add API endpoints for creating & editing embed configurations ## Overview Currently, embed configurations can only be created through the web interface. This feature request adds new REST API endpoints `/v1/embed/new` and `/v1/embed/{id} to allow programmatic creation and editing of embed configurations using API key authentication. ## Why? - Enables automation of embed creation - Enables automation of embed editing - Allows integration with external systems and scripts - Provides a programmatic alternative to the UI-based workflow ## Current Solution Users must manually create and edit embeds through the web interface at `/settings/embed-config` The endpoints will use the existing API key authentication system and follow the same patterns as other API endpoints in the system.
yindo added the enhancementfeature request labels 2026-02-22 18:27:56 -05:00
yindo closed this issue 2026-02-22 18:27:56 -05:00
yindo commented 2026-02-22 18:27:56 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 13, 2025):

To clarify, do you mean to add an API that does embedding and returns the vectors and such for a given text or file. If you mean using the API to automate the management of documents in a workspace that does already exist in the /v1/workspace/:slug/update-embeddings endpoint

@timothycarambat commented on GitHub (Feb 13, 2025): To clarify, do you mean to add an API that does embedding and returns the vectors and such for a given text or file. If you mean using the API to automate the management of documents in a workspace that does already exist in the `/v1/workspace/:slug/update-embeddings` endpoint
yindo commented 2026-02-22 18:27:56 -05:00
Author
Owner
Copy Link
Copy Source

@jamieede commented on GitHub (Feb 13, 2025):

@timothycarambat I am talking about the endpoints for the JS embeds.

The web application has UI API endpoints for:

  • /api/embeds/new POST
  • /api/embed/{embed_id} DELETE
  • /api/embed/update/{embed_id} POST

However these are not exposed on the main API over at /api/v1

I am looking to have parity in the endpoints from the UI in the main api.

Your thoughts on this would be appreciated. I did begin work to get those incorporated, however, I believe I will struggle with getting it exactly as needed in terms of response and requirements your team expects.

@jamieede commented on GitHub (Feb 13, 2025): @timothycarambat I am talking about the endpoints for the JS embeds. The web application has UI API endpoints for: - /api/embeds/new POST - /api/embed/{embed_id} DELETE - /api/embed/update/{embed_id} POST However these are **not** exposed on the main API over at **/api/v1** I am looking to have parity in the endpoints from the UI in the main api. Your thoughts on this would be appreciated. I did begin work to get those incorporated, however, I believe I will struggle with getting it exactly as needed in terms of response and requirements your team expects.
yindo changed title from [FEAT]: Add additional EMBED API endpoints [WIP] to [GH-ISSUE #3192] [FEAT]: Add additional EMBED API endpoints [WIP] 2026-06-05 14:44:15 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2054
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?