Resolve an integration entity
GET
/api/v1/lookup/{app}/{entity_id}
const url = 'https://example.com/api/v1/lookup/snipeit/example';const options = {method: 'GET', headers: {'X-Label-Hub-Key': '<X-Label-Hub-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/lookup/snipeit/example \ --header 'X-Label-Hub-Key: <X-Label-Hub-Key>'Looks up an entity from the given integration app by its identifier. app must be one of snipeit, grocy, or spoolman — an unsupported value returns 422. Returns 404 ProblemDetail when the entity does not exist in the integration’s backend. The url field is the deep-link to the entity in the integration’s own web UI, suitable for embedding in a QR code or label.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”app
required
App
string
entity_id
required
Entity Id
string
Responses
Section titled “Responses”Successful Response
Media typeapplication/json
LookupResult
REST view of a resolved integration entity.
object
app
required
App
Integration app that resolved this entity
string
extra
Extra
Integration-specific extras not covered by the core fields. Contents vary by app — see each integration’s plugin docs.
object
key
additional properties
any
id
required
Id
The entity identifier as supplied by the caller
string
Example
{ "app": "snipeit"}Validation Error
Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationErrorobject
ctx
Context
object
input
Input
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
Example generated
{ "detail": [ { "ctx": {}, "input": "example", "loc": [ "example" ], "msg": "example", "type": "example" } ]}