Find recipe authors
const url = 'http://127.0.0.1:8080/api/v1/recipe-authors?q=example&limit=20';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'http://127.0.0.1:8080/api/v1/recipe-authors?q=example&limit=20' \ --header 'Authorization: Bearer <token>'Resolve a complete author name from active recipes in the selected library. Returns only the best available tier: Unicode case-folded NFC and whitespace equality, then Latin accent variants, then one edit or adjacent transposition for 5 to 64 rune names with at least four letters. Punctuation is literal in exact matching. Non-Latin marks are preserved; scripts are not transliterated. Names are ordered by their original Unicode spelling. Exact and accent matches have no candidate cap; typo comparisons evaluate at most 128 indexed candidate names. Choose a returned name before applying the exact author: recipe filter, and ask for a choice when suggestions are ambiguous.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Complete author name to resolve; only recipe author fields are searched
Complete author name to resolve; only recipe author fields are searched
Maximum number of author names to return
Maximum number of author names to return
Responses
Section titled “Responses”OK
object
Typo candidate retrieval exceeded 128 names; additional suggestions may exist
Matching names in the selected tier exceed the requested limit
object
Best available tier: exact normalized name, Latin accent variant, or one edit or adjacent transposition
Original author name to quote in an author: qualifier
Active recipes with this exact credited spelling in the selected library
Example
{ "items": [ { "match": "exact" } ]}No valid session or API token (authentication-required), or the credential sent is invalid (invalid-credentials).
object
Examplegenerated
{ "code": "example", "detail": "example", "status": 1, "title": "example", "type": "example"}Forbidden
object
Stable application error code; clients may also use the problem type suffix.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
Structured context for the stable error code.
object
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
object
object
Example
{ "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}Unprocessable Entity
object
Stable application error code; clients may also use the problem type suffix.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
Structured context for the stable error code.
object
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
object
object
Example
{ "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}Internal Server Error
object
Stable application error code; clients may also use the problem type suffix.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
Structured context for the stable error code.
object
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
object
object
Example
{ "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}