Connect Amberscript to Simpleen Translation

Both apps 23Amberscript 10Simpleen Translation 13

• Trigger
  Job Finished

  Triggers when a job has finished on our platform.

• Action
  Add glossary

  Create a new glossary of terms that can be referenced by glossaryId on job upload for improved transcription accuracy. POST https://api.amberscript.com/api/glossaries?apiKey={apiKey}.

• Action
  Create New Job

  This action creates a new job on the Amberscript platform.

• Action
  Delete glossary

  Delete an existing glossary. DELETE https://api.amberscript.com/api/glossaries/{glossaryId}?apiKey={apiKey}.

• Action
  Delete job

  Delete a transcription job. DELETE https://api.amberscript.com/api/jobs?jobId={jobId}&apiKey={apiKey}. Returns {"message":"Job deleted"}.

• Action
  Get job

  Retrieve the status/details of a transcription job. GET https://api.amberscript.com/api/jobs/status?jobId={jobId}&apiKey={apiKey}. Returns jobStatus with status OPEN/BUSY/ERROR/DONE, transcriptionType, jobType, language, nrAudioSeconds, etc.

• Action
  Get job transcript

  Download a finished job's transcript/subtitles in a chosen export format. GET https://api.amberscript.com/api/jobs/export-{format}?jobId={jobId}&apiKey={apiKey} where format is one of srt, vtt, txt, json (srt/vtt take optional maxCharsPerRow/maxNumberOfRows/maxScreenTimePerRowSeconds; txt takes optional includeTimestamps/includeSpeakers/highlightsOnly/maxCharsPerRow). SRT/VTT/JSON return the content directly (JSON export returns structured word-level data); TXT and STL(deprecated) return a downloadUrl JSON wrapper for some formats. Implementer should expose a format field and branch the endpoint/response handling accordingly.

• Action
  List glossaries

  List all glossaries defined on the account (used to supply glossaryId when uploading a job). GET https://api.amberscript.com/api/glossaries?apiKey={apiKey} per Amberscript docs Glossary section.

• Action
  List jobs

  List all transcription jobs for the account. GET https://api.amberscript.com/api/jobs?apiKey={apiKey}. Returns an array of jobStatus objects.

• Action
  Update glossary

  Update an existing glossary's terms. PUT/PATCH https://api.amberscript.com/api/glossaries/{glossaryId}?apiKey={apiKey}.

• Action
  Add glossary

  Create a new glossary of word entries/ignored terms for translation. POST /glossaries.

• Action
  Add segment

  Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.

• Action
  Create Translation

  Translates content to selected target language

• Action
  Get file

  Get a specific localization file by id, including its segments and languages. GET /files/{id}.

• Action
  Get glossary

  Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.

• Action
  Get segment

  Get a specific translation segment by id. GET /segments/{id}.

• Action
  List files

  List the localization files known to the account. GET /files.

• Action
  List glossaries

  List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.

• Action
  List languages

  List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.

• Action
  List segments

  List translatable segments (source/translated entry pairs) across the user's files. GET /segments.

• Action
  Run translator

  Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.

• Action
  Update glossary

  Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.

• Action
  Update segment

  Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.