The following endpoints accept running text as the data payload, and directly return a json response. Eg:
$ curl --data "Voi voi olla." kielipankki.rahtiapp.fi/text/fi/postag | jq
{
"postagged": [
[
[
"Voi",
"voi",
"[POS=PARTICLE]|[SUBCAT=INTERJECTION]"
],
[
"voi",
"voida",
"[POS=VERB]|[VOICE=ACT]|[MOOD=INDV]|[TENSE=PRESENT]|[PERS=SG3]"
],
[
"olla",
"olla",
"[POS=VERB]|[VOICE=ACT]|[INF=A]|[CASE=LAT]"
],
[
".",
".",
"[POS=PUNCTUATION]"
]
]
]
}
The following endpoints, intended to support slightly larger jobs that may time out, support a submit-and-query scheme. Eg:
$ curl --data '@text_to_process.txt' kielipankki.rahtiapp.fi/text/fi/nertag/submit
{"jobid":"4afa7d86-3416-4993-8110-ab9a7e2de39e"}
$ curl --data '4afa7d86-3416-4993-8110-ab9a7e2de39e' kielipankki.rahtiapp.fi/text/fi/nertag/query_job
...verbose output...
Endpoints for automatic speech recognition.
Submit a form with a file
key, eg. curl -F 'file=@audio.mp3' http://kielipankki.rahtiapp.fi/audio/asr/fi/submit_file
. The response is a json object containing a jobid
key, which is used later for polling for results with /audio/asr/fi/query_job
.
Example output:
{"file":"puhetta.mp3","jobid":"357f3518-afaa-45e9-bda7-b52a60b73000"}
Additional fields may appear, the jobid
field is the important one.
Submit a wav file as the data payload, eg. curl --data-binary @audio.wav https://kielipankki.rahtiapp.fi/audio/asr/fi/submit
. The response is a json object containing a jobid
key, which is used later for polling for results with /audio/asr/fi/query_job
.
Example output:
{"jobid":"337adadb-37ff-4492-9480-d2ffb1126932"}
Submit a jobid as the data payload. The response may be a partial result, a complete result, a pending result, or an error state.
If the submitted job id is unknown to the service, meaning that no such job has been submitted, or has been submitted so long ago that the cache has forgoten about it, the service returns
{"error": "job id not available"}
This is also the response if the job has multiple segments, and one or more of those segments has an unknown job id.
In this case the job is known, but there is no result to report yet, partial or otherwise.
{'status': 'pending'}
This is a specialised endpoint that conforms to a particular front-end.
Submit a jobid as the data payload. The response may be a partial result, a complete result, a pending result, or an error state.
Endpoints for aligning a known transcript with an audio to obtain timestamps.
Submit a form with audio
and transcript
keys.