Save a pattern
const url = 'https://api.facteur.eu/v1/inboxes/example/extractors';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"key":"example","label":"example","scope":"text","pattern":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.facteur.eu/v1/inboxes/example/extractors \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "key": "example", "label": "example", "scope": "text", "pattern": "example" }'The pattern is compiled by the ingestion engine before it is saved. One that only failed at reception would silently produce nothing, with no way to find out.
key becomes a property name under message.extract, which is why it is
constrained to something usable as one.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The inbox identifier — the same string that prefixes its receiving address.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Letters, digits and underscores, starting with a letter — it has to be usable as a property name.
Responses
Section titled “Responses”The extractor.
object
The property name this appears under in message.extract.
Example
{ "scope": "text"}INVALID_KEY, PATTERN_REQUIRED, INVALID_PATTERN (the engine says why), or INVALID_JSON.
Every failure has this shape. Branch on error.code; error.message is
written for a human and is in French today.
object
object
The stable, machine-readable reason.
A sentence for whoever is reading the failure. Not part of the contract.
Example
{ "error": { "code": "SCOPE_INSUFFICIENT" }}No usable credential. UNAUTHENTICATED when none was presented,
KEY_UNKNOWN, KEY_REVOKED or KEY_EXPIRED when a key was — kept
distinct on purpose, because “mint a new one” and “somebody took this
away from you” are different facts to whoever is reading a red pipeline.
Every failure has this shape. Branch on error.code; error.message is
written for a human and is in French today.
object
object
The stable, machine-readable reason.
A sentence for whoever is reading the failure. Not part of the contract.
Example
{ "error": { "code": "SCOPE_INSUFFICIENT" }}SCOPE_INSUFFICIENT (the message names the scope this request wanted and
the ones the key holds), KEY_CANNOT_REACH (no scope opens this route to
a key at all), FORBIDDEN, or one of the stated refusals listed under
x-api-key-refusals.
Every failure has this shape. Branch on error.code; error.message is
written for a human and is in French today.
object
object
The stable, machine-readable reason.
A sentence for whoever is reading the failure. Not part of the contract.
Example
{ "error": { "code": "SCOPE_INSUFFICIENT" }}INBOX_NOT_FOUND. An inbox in a workspace the key does not reach answers
the same way as one that does not exist — telling the two apart would let
anyone map a colleague’s workspaces one request at a time.
Every failure has this shape. Branch on error.code; error.message is
written for a human and is in French today.
object
object
The stable, machine-readable reason.
A sentence for whoever is reading the failure. Not part of the contract.
Example
{ "error": { "code": "SCOPE_INSUFFICIENT" }}KEY_ALREADY_USED — this inbox already has an extractor under that key.
Every failure has this shape. Branch on error.code; error.message is
written for a human and is in French today.
object
object
The stable, machine-readable reason.
A sentence for whoever is reading the failure. Not part of the contract.
Example
{ "error": { "code": "SCOPE_INSUFFICIENT" }}